Search Issue Tracker
Fix In Review
Fix In Review for 6000.3.13f1, 6000.4.1f1, 6000.5.0b2, 6000.6.0a2
Votes
0
Found in
6000.3.11f1
6000.4.0b12
6000.5.0a8
6000.6.0a1
Issue ID
UUM-136445
Regression
No
Scaler Profile new element has a “Properties” button in the context menu that does nothing when pressed
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Open the Project Settings window (Edit > Project Settings)
- Open the Adaptive Performance tab in the Project Settings window
- Enable Adaptive Performance
- Open the Basic tab in the Adaptive Performance Settings
- Expand the "Default Scaler Profile" foldout
- Click the "+" button to add a new element to the list
- Right-click the new elements selection field
- Click the "Properties" button
- Observe the Editor
Actual results: Nothing happens
Expected results: Either the button is deactivated or something happens when the button is pressed
Reproducible with versions: 6000.3.11f1, 6000.4.0b12, 6000.5.0a8
Can’t test with versions: 6000.0.70f1 (due to not being able to add a new element to the Scaler Profile)
Tested on (OS): Windows 11, MacOS Silicon Tahoe 26.2
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.6.0a2):
Fixed in 6000.6.0a2
Resolution Note (fix version 6000.5.0b2):
Fixed in 6000.5.0b2
Resolution Note (fix version 6000.4.1f1):
Fixed in 6000.4.1f1
Resolution Note (fix version 6000.3.13f1):
Fixed in 6000.3.13f1