Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2021.3.25f1
2022.2.20f1
2023.1
2023.2.0a15
2023.3.0a3
Issue ID
UUM-36540
Regression
No
[HDRP] Setting quality setting to custom through code should be less painful
[https://forum.unity.com/threads/cant-see-changes-on-depthoffield.1437040/]
"Bug" comes from this forum post and the idea would be to be able to have something like
dof.quality.value = (int)ScalableSettingLevelParameter.Level.Custom;
Instead of relying on using (int) directly since ScalableSettingLevelParameter doesn't really contain Custom, it's infered from the other properties IIRC
Also, it's not possible to override the Quality settings by code as well if you have your volume at runtime for exemple which creates problems
Maybe by adding an example to the doc in the runtime page as well.
[https://docs.unity3d.com/Packages/com.unity.render-pipelines.high-definition@16.0/manual/Volumes-API.html]
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
Closing it for now, it is track for future quality setting improvement, but not for unity 6
Resolution Note (2023.3.X):
Closing it for now, it is track for future quality setting improvement, but not for unity 6