Null ref spam on fresh install of EditorXR

Running Windows 10 w/ an i7-6700K @4GHz & a GTX1080. Just installed Unity 2017.2.0p1, installed the Unity package for EditorXR in a brand new project, installed Oculus Utilities (using Rift w/ Touch), and turned on VR Support in Player Settings. I downloaded everything from the links provided here:

https://blogs.unity3d.com/2017/11/30/learn-how-googles-poly-works-with-unity-editorxr/

I followed the setup instructions in the V4 guide. When I turn on EditorXR, everything seems to be fine. Head tracking works with no trouble, but as soon as I pick up my controllers I am bombarded by null ref spam.

1st error:

This one fires only once -

NullReferenceException: Object reference not set to an instance of an object
UnityEditor.Experimental.EditorVR.Workspaces.FilterUI.set_filterList (System.Collections.Generic.List`1 value) (at Assets/EditorVR/Workspaces/Common/Scripts/FilterUI.cs:108)

2nd error:

This one throws hundreds of times per second, causing lag in headset -

NullReferenceException: Object reference not set to an instance of an object
UnityEditor.Experimental.EditorVR.Workspaces.HierarchyListViewController.UpdateItems () (at Assets/EditorVR/Workspaces/HierarchyWorkspace/Scripts/HierarchyListViewController.cs:127)
ListView.ListViewControllerBase.UpdateView () (at Assets/EditorVR/Scripts/ListView/ListViewControllerBase.cs:108)

These null refs prevent most touch controller UI from displaying, so my menus appear to be mostly empty.


How are there null refs in a fresh install of both the engine and the package in a brand new project? Was this package tested before export? It looks like someone must have committed a mistake just before exporting it. Has anyone dealt with/resolved this? What am I missing?

 

Think I figured it out. I figured the Text Mesh Pro install was optional. I was wrong. On reboot, EditorXR threw a warning that said it's required. I installed it, and all is well now.