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
- Editor layout does not save custom Editor windows when they are declared using file-scoped namespaces
- Crash on VFXManager::CollectShadowCullResults when opening a specific scene
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
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