Search Issue Tracker
Fixed
Fixed in 6000.6.0a6
Under Consideration for 6000.3.X, 6000.4.X, 6000.5.X
Votes
0
Found in
6000.3.15f1
6000.4.6f1
6000.5.0b7
6000.6.0a4
Issue ID
UUM-141453
Regression
Yes
Adaptive Performance Settings Framerate field doesn't display the "supported without VSync" warning, when the field is collapsed in Build Profiles
Steps to reproduce:
- Create and open a new project
- Open the File -> Build Profiles window
- Create a new Windows Profile
- Add the "Adaptive Performance Settings" setting
- Expand Runtime Settings -> Scaler Profiles
- Observe the "Framerate" field
Actual results: The "Framerate" field is collapsed and the "Adaptive Framerate is only supported without VSync." warning is not displayed
Expected results:
- The "Framerate" field is expanded by default, and the "Adaptive Framerate is only supported without VSync." warning is displayed by default
- The "Framerate" field is collapsed, but the warning is still displayed
Reproducible with versions 6000.3.15f1, 6000.4.6f1, 6000.5.0a5, 6000.5.0b7, 6000.6.0a4
{}Not reproducible with versions{}: 6000.5.0a4
Can’t test with versions: 5.1.6 (6000.0.73f1, 6000.2.0b2) (No Runtime Settings reference in Build Profiles)
Tested on (OS): Windows 11 Pro (25H2)
Notes:
- VSync is enabled by default in the Quality settings, therefore this will reproduce at least once in each project where "Adaptive Performance Settings" is added
- After regression, when the Framerate field is collapsed, the Framerate field appears to be too tall, which suggests that the warning should be displayed even when it is collapsed
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note:
Fixed in 6000.6.0a6
Resolution Note (fix version 6000.6.0a6):
Fixed in 6000.6.0a6