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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
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