Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.3.11f1
6000.4.0b12
6000.5.0a8
Issue ID
UUM-136450
Regression
No
The Build Profiles Window scrolls up when toggling the "Enable Adaptive Performance" flag in Adaptive Performance Settings
Steps to reproduce:
- Create and open a new URP 3D Project
- Navigate to File > Build Profiles
- Click the "Add Build Profile" buttons to create a Custom Profile
- Click the "Add Settings" button and add a couple type of Settings, then add the "Adaptive Performance Settings"
- Disable the "Enable Adaptive Performance Settings" flag in them and observe the window and the vertical scrollbar
- Enable the "Enable Adaptive Performance Settings" flag in them and observe the window and the vertical scrollbar
Actual results: The Build Profile Window scrolls to the top when toggling the Enable Adaptive Performance Settings" flag
Expected results: The Build Profile Window doesn't scroll when enabling or disabling the flag
Reproducible with versions: 6000.3.11f1, 6000.4.0b12, 6000.5.0a8
Can’t test with versions: 6000.0.70f1 (No Adaptive Performance Settings in Build Profiles)
Tested on (OS): Windows 11
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:
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.5.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.