Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.0a16
Issue ID
UUM-4670
Regression
No
[HDRP] [VT] Massive viewport slowdown after tweaking GPU Cache Size per Format
Steps to reproduce:
1) Create an Empty scene or open attached project
2) Make sure VT is enabled, go to HDRP asset and at the bottom tweak GPU Cache Size per Format (could be something small incrementally, like 64 -> 65)
3) Observe that viewport starts to slow down, tweak Cache size more, wait a minute, observe that Viewport becomes unusable
Notes: issue is gone after a domain reload.
If you check Task Manager before tweaks, notice that Unity eats ~3% of CPU on idle, after cache tweaks it starts to eat ~12%
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:
Given the age of this "regression" (it's so long ago that it's no longer a regression imo), the fact that it's on a relatively unused IMGUI field, and the lack of duplicates/user upvotes, I'm going to close this bug as Won't Fix. The few users that encounter this issue should consider switching that part of the UI to UI Toolkit.
If this issue comes back from a user, via a public bug, we might then take another look.
Resolution Note (2022.2.X):
Given the age of this "regression" (it's so long ago that it's no longer a regression imo), the fact that it's on a relatively unused IMGUI field, and the lack of duplicates/user upvotes, I'm going to close this bug as Won't Fix. The few users that encounter this issue should consider switching that part of the UI to UI Toolkit.
If this issue comes back from a user, via a public bug, we might then take another look.