Search Issue Tracker
Fixed in 1.5.0+
Votes
2
Found in [Package]
1.4.3
Issue ID
1275361
Regression
No
[XR][Quest][Frame Debugger] Frame Debugger first freezes Unity, then breaks XR rendering and head tracking
Repro steps:
1. Open SampleScene
2. Press Play
3. Note Game View is black
4. Open Window > Analysis > Frame Debugger
5. Press "Enable"
6. Note freeze for 30s-1min
7. Select something in the Frame Debugger hierarchy
8. Disable Frame Debugger
9. Note XR is now black and broken
Actual: Note GameView has some image but head tracking is broken
-
CreepyLamppost
Aug 13, 2022 15:52
I have this also in 2019.4.6f1 on my oculus quest 1. Getting really frustrating to optimize the app when I basically have to choose the perfect moment to enable frame debugger cuz thats all I get before it crashes and I have to restart the app twice on the headset before getting back to optimizing again.
-
PhilFaily
Jun 10, 2021 11:31
Still happening with 2020.3.1
-
leftClaw
Dec 28, 2020 01:02
I still see this behavior in unity 2020.2.1 and Oculus 1.6.1
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 1.5.0+):
Fix for frame debugger freezes Unity Editor and then breaks XR rendering when XR enabled.