Search Issue Tracker
Fixed
Fixed in 4.0.3, 5.1.1
Votes
0
Found in [Package]
4.0.2
5.1.1
Issue ID
APB-45
Regression
No
Custom Adaptive Performance Scaler is not updated in the Profiler when it does not have an overridden name
Reproduction steps:
1. Open the attached “ASDQWE” project
2. In the Game Window, select the “Game” drop-down
3. Select the “Simulator” field
4. In the Simulator Window, click the “Control Panel” button
5. Enter the Play Mode
6. In the Simulator Window’s Control Panel tab, enable the “ualityScaler” Custom Scaler
7. Change the “Max Level” property value
8. In the Profiler Window, select the “Adaptive Performance” tab
9. In the tab, observe the “TextureQualityScaler”
Expected result: The “Max Level” property has increased from 4 to the changed value
Actual result: The “Max Level” property value remains equal to 4
Reproducible with: 4.0.1, 5.1.0 (2021.3.44f1, 2022.3.48f1), 5.1.0 (6000.0.21f1)
Reproducible on: MacOS 14.6.1 (Intel), Windows 11 (user’s)
Not reproducible on: No other environment tested
Workaround:
- Rename the scaler class to start with "Adaptive". This will fix the label in the Control Panel
- Add an override for the “Name” property and set the name to start with "Adaptive". This will fix the “Level Override” bar values
Notes:
There are other issues as well with the Custom Scaler:
- The Custom Scaler name is incorrect - it should be “TextureQualityScaler” while it is “ualityScaler”
- Increasing the “Level Override” property does not change the Level value of the Custom Scaler
- The “Level Override” property does not take into account the “Max Level” property value
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note (fix version 5.1.1):
The custom scaler will now be properly displayed in the Simulator.
Change the sample to showcase that the classname and name of the scaler settings need to be the same to propergate the values to the profiler properly.