Search Issue Tracker
Fixed
Fixed in 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Votes
0
Found in
6000.3.2f1
6000.4.0b2
6000.5.0a5
Issue ID
UUM-131802
Regression
Yes
[RenderingDebugger] Opening Rendering Debugger after building the Player, does not register any debug items
Steps to reproduce:
- Download attached project and open in Unity.
- Open Rendering Debugger >> Window >> Analysis >> Rendering Debugger, and confirm it displays the information.
- Open Build Profiles.
- Make sure the Development Build and Autoconnect Profiler checkboxes are enabled.
- Build and Run project.
- Close the player.
- Open Rendering Debugger >> Window >> Analysis >> Rendering Debugger.
Observe the message in Rendering Debugger window: No debug items found.
Actual results: No debug items found in the Rendering Debugger window.
Expected results: Rendering Debugger should display debug items.
Reproducible with versions:
6000.3.2f1, 6000.4.0b2, 6000.5.0a5
Not reproducible with versions:
6000.2.14f1
Tested on (OS):
MacBook Pro (16-inch, 2021), CPU: Apple M1 Max, Memory: 64 GB, macOS Tahoe: 26.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
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- 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
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
Resolution Note:
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.4.0b7):
Fixed in 6000.4.0b7
Resolution Note (fix version 6000.3.7f1):
Fixed in 6000.3.7f1