Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2021.2
2021.2.0a5
Issue ID
1313689
Regression
No
[Enlighten] Quality Settings missing "CPU Usage" setting. Users unable to tune Realtime GI performance
Repro:
Using 2021.2.0a5, navigate to Project Settings > Quality Settings.
Observed:
"CPU Usage" property is not there (sad)
Expected:
We need a property there for how wide Enlighten can go on the CPU.
Notes:
Issue discussed in a little greater detail: here
In Unity 5.6, "CPU Usage" for Enlighten Realtime GI used to be in the Lighting Window. Around 2017, we moved it to the Quality Settings window.
It appears at the time of Enlighten Deprecation (2020.1), we removed "CPU Usage" from Quality settings. However, it looks like the Documentaion wasn't update before deprecation to describe the property. This therefore also needs a Docs ticket, which I'll open.
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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Resolution Note (2021.2.X):
This will be solved as part of a larger area refactor.