Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.2.14f1
6000.3.0f1
6000.5.0a4
Issue ID
UUM-129720
Regression
No
[RenderingDebugger] Can't open Rendering Debugger on Quest device
Steps to reproduce:
- Download attached project and open in Unity.
- Open SampleScene.
- Change the platform to Android in the Build Profiles.
- Enable Development Build and Autoconnect Profiler.
- Build and Run project on the device.
- Once the build completes, press the controller's primary2DAxis and secondary2DAxis at the same time to enable the Rendering Debugger overlay.
Actual results: No Rendering Debugger overlay appears on Meta Quest device.
Expected results: Rendering Debugger overlay should appear.
Reproducible with versions:
6000.2.14f1, 6000.3.0f1, 6000.5.0a4
Tested on (OS):
Meta Quest 3 headset
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment