Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
0.9.4-preview
Issue ID
1246259
Regression
No
Crash on XRInputSubsystem::TrySetTrackingOriginMode when starting XRGeneralSettings.Manager.InitializeLoader() Coroutine
How to reproduce:
1. Open attached project "Case_1236259" and load scene "SampleScene"
2. Enter Play Mode
Reproducible with: 0.0.6-preview, 0.9.4-preview (2019.3.16f1, 2019.4.0f1, 2020.1.0b11, 2020.2.0a13)
Could not test with: 2018.4.23f1 (No XR Interaction Toolkit package)
First lines of the stack trace:
0x00007ff73670ee7e (Unity) XRInputSubsystem::TrySetTrackingOriginMode
0x00007ff7367ab8b5 (Unity) XRInputSubsystem_CUSTOM_TrySetTrackingOriginMode
0x0000016f040664b6 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.XR.XRInputSubsystem:TrySetTrackingOriginMode (UnityEngine.XR.XRInputSubsystem,UnityEngine.XR.TrackingOriginModeFlags)
0x0000016f04065ff3 (Mono JIT Code) [XRRig.cs:245] UnityEngine.XR.Interaction.Toolkit.XRRig:SetupCamera (UnityEngine.XR.XRInputSubsystem)
0x0000016e9f6ec71b (Mono JIT Code) [XRRig.cs:191] UnityEngine.XR.Interaction.Toolkit.XRRig:SetupCamera ()
0x0000016e9f6ec5a3 (Mono JIT Code) [XRRig.cs:157] UnityEngine.XR.Interaction.Toolkit.XRRig:TryInitializeCamera ()
Notes:
The issue occurs when there is an XRRig in the scene
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note:
Valve now own the OpenVR XR Plugin, and we've forwarded the details of this bug over to them. Please consult them for a related fix. This also only occurs when no HMD is present. So a workaround is to ensure the HMD is connected.