Search Issue Tracker
Fixed
Fixed in 6000.1.0b1
Votes
0
Found in
6000.1.0a9
Issue ID
UUM-99606
Regression
No
Editor glitches and becomes unresponsive when AR Foundation Simulator's "Room XRay" Shader is present
Reproduction steps:
1. Open the attached “ArchiveXR“ project
2. Select the Museum > Museum_69ftx48ft environment and enable it by clicking on the globe icon in the XR Environment tab (lower right corner of the Game View)
3. Play around with it and observe
Expected result: No glitches are present, everything works as expected
Actual result: Editor flickers, becomes 90% unresponsive, graphics crashes, system menu bar turns magenta tinted
Reproducible with: 5.1.5 (2022.3.44f1), 6.0.3 (6000.0.17f1)
Reproducible on: M1 Max macOS 14.5 (Tested by CQA), M2 Ultra macOS 14.5 (User’s platform)
Not reproducible on: Windows 10
Notes:
- The user’s team has narrowed this down to when "Room XRay" shader compiles in the editor
- This occurs with both synchronous and asynchronous shader compilation.
- Somtimes "CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000" happens.
- Often seeing "Thread 0x<HEX PID> may have been prematurely finalized" when compiling "Room XRay" in the Editor
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Add comment