Constant Debug Log Errors while using Mock HMD in Editor

[dlackey_bh]

I’m trying to integrate the Mock HMD for use in our development process. In play mode, every frame, there is this log error:

Attempting to determine the size of an unknown feature type Id [-1].
UnityEditor.EditorGUIUtility:RenderPlayModeViewCamerasInternal_Injected(RenderTexture, Int32, Vector2&, Boolean, Boolean)
UnityEditor.EditorGUIUtility:RenderPlayModeViewCamerasInternal(RenderTexture, Int32, Vector2, Boolean, Boolean)
UnityEditor.PlayModeView:RenderView(Vector2, Boolean)
UnityEditor.GameView:OnGUI()
System.Reflection.MonoMethod:InternalInvoke(Object, Object[ ], Exception&)
System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[ ], CultureInfo)
System.Reflection.MethodBase:Invoke(Object, Object[ ])
UnityEditor.HostView:Invoke(String, Object)
UnityEditor.HostView:Invoke(String)
UnityEditor.HostView:InvokeOnGUI(Rect, Rect)
UnityEditor.DockArea:smile:rawView(Rect, Rect)
UnityEditor.DockArea:OldOnGUI()
UnityEngine.UIElements.IMGUIContainer:smile:oOnGUI(Event, Matrix4x4, Rect, Boolean, Rect, Action, Boolean)
UnityEngine.UIElements.IMGUIContainer:HandleIMGUIEvent(Event, Matrix4x4, Rect, Action, Boolean)
UnityEngine.UIElements.IMGUIContainer:smile:oIMGUIRepaint()
UnityEngine.UIElements.UIR.RenderChainCommand:ExecuteNonDrawMesh(DrawParams, Boolean, Single, Exception&)
UnityEngine.UIElements.UIR.UIRenderDevice:EvaluateChain(RenderChainCommand, Rect, Matrix4x4, PanelClearFlags, Texture, Texture, Texture, Single, NativeArray1, NativeArray1, Exception&)
UnityEngine.UIElements.UIR.UIRenderDevice:smile:rawChain(RenderChainCommand, Rect, Matrix4x4, PanelClearFlags, Texture, Texture, Texture, Single, NativeArray1, NativeArray1, Exception&)
UnityEngine.UIElements.UIR.RenderChain:Render(Rect, Matrix4x4, PanelClearFlags)
UnityEngine.UIElements.UIRRepaintUpdater:smile:rawChain(Rect, Matrix4x4)
UnityEngine.UIElements.UIRRepaintUpdater:Update()
UnityEngine.UIElements.VisualTreeUpdater:UpdateVisualTreePhase(VisualTreeUpdatePhase)
UnityEngine.UIElements.Panel:UpdateForRepaint()
UnityEngine.UIElements.Panel:Repaint(Event)
UnityEngine.UIElements.UIElementsUtility:smile:oDispatch(BaseVisualElementPanel)
UnityEngine.UIElements.UIElementsUtility:ProcessEvent(Int32, IntPtr)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

[C:\buildslave\unity\build\Modules/XR/Subsystems/Input/Public/XRInputUtilities.cpp line 183]
(Filename: C:\buildslave\unity\build\Modules/XR/Subsystems/Input/Public/XRInputUtilities.cpp Line: 183)

Obviously, the Game window is trying to draw something that seems not to be there. Have not yet tried a build (I’m about to leave for the day). I did have a separate project with nothing in it, so I tried the Mock HMD plugin there and did not see the error. Not sure what the difference is. I’m unable to produce a small project that reproduces the error, and I am not at liberty to distribute our production project. Not even really sure it would help since it looks to be happening in Unity-land code and not user-land.

Any help or guidance would be appreciated.

[Shaunyowns]

Hey @dlackey_bh , there could be several factors causing the issue, and unfortunately it’s hard for us to investigate without a reproducible project. At the very least, can you file a bug with the log file attached so the team can take a look? Thanks!

[dlackey_bh]

Thank you for the reply. I’m working with IT at the moment to try and get Unity’s bug reporter unblocked from the web filter. Will submit a bug asap.

[dlackey_bh]

Bug submitted. Case 1289987. Hopefully someone can make sense of it.

[Real-LifeAssets]

It is actually pretty easy to reproduce, just create empty project, enable XR plugin management and XR interaction toolkit, install Mock HMD loader, add room-scale XR rig to the scene and here it is! Reproduced in Unity 2020.1.13f1

[xshadowmintx]

Seems like you can fix this by rolling back to the preview.1 - 1.1.3-preview.1 package or before.

Definitely a paper-cut, but that’s what you get for using preview packages I guess.

[dlackey_bh]

Haven’t logged into the forums for a while, so I’m just now seeing the replies. We’re actually using 2019.4.12f1 for our product (not moving up to 2020 for a while), and that’s where I am seeing the issue.