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
- 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:
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