Search Issue Tracker
Fixed in 6000.3.6f1
Fixed in 6000.4.0b6, 6000.5.0a5
Won't Fix in 6000.2.X, 6000.3.X
Votes
0
Found in
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131482
Regression
Yes
Frame Debugger "Levels" value fields resize unpredictably when changing between events
Steps to reproduce:
- Create a new Unity project using a 3D Universal Template
- Open the Frame Debugger window (Window > Analysis > Frame Debugger)
- Enable the Frame Debugger
- Move through the events (with slider or arrow buttons)
- Observe the "Levels" value fields
Actual results: Value fields change size, become bigger/smaller with different events selected, for no apparent reason
Expected results: Value fields remain the same consistent size, no matter the selected event
Reproducible with versions: 6000.2.0a5, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Not reproducible with versions: 6000.0.65f1, 6000.2.0a4
Reproducible on: Windows 11
Not reproducible on: macOS 26.1 (M1 Pro)
Note:
- After the regression, the field generally seems a lot bigger, even though I would assume there is no need to have the field as big as it is now
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 window icon is blurry and low quality when the Shader Graph is created using the Universal 2D template
- “Export HDRP Sky to Image” command error message does not indicate that Game view must be visible
- Adaptive Performance Settings Framerate field doesn't display the "supported without VSync" warning, when the field is collapsed in Build Profiles
- “MissingReferenceException”, “NullReferenceException” and GUI errors are spammed in the Console when selecting “Boris” GameObject in the Prefab field of the “Plunkah” GameObject in the “_IK” Sample scene
- "Upload Symbols Failed" is thrown when Archive validation is being done in Xcode
Resolution Note (fix version 6000.3.6f1):
Fixed in 6000.3.6f1
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.3.6f1
Resolution Note (fix version 6000.4.0b6):
Fixed in 6000.4.0b6
Resolution Note (6000.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.