Search Issue Tracker
Won't Fix
Fix In Review for 6000.5.X
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.60f1
6000.2.9f1
6000.3.0b7
6000.4.0a3
6000.5.0a1
Issue ID
UUM-122929
Regression
No
Rendering Debugger - “Go to Section” does nothing
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Open the Rendering Debugger window (Window > Analysis > Rendering Debugger)
- Open the Rendering tab in the Rendering Debugger window
- Click the burger button on the right side of the Rendering Debug section
- Select "Go to Section"
- Observe the Rendering Debugger window
Actual results: Nothing happens because the section/tab is already opened
Expected results: The "Go to Section" button should only be available in the "Frequently Used" tab
Reproducible with versions: 6000.0.60f1, 6000.2.9f1, 6000.3.0b7, 6000.4.0a3
Tested on (OS): MacOS Silicon Sequoia 15.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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
In order to properly fix this we need need public API to be just deprecated.
This is really a small issue that will be solved with the UITK implementation.
Resolution Note (6000.5.X):
In order to properly fix this we need need public API to be just deprecated.
This is really a small issue that will be solved with the UITK implementation.