Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
0
Found in
2019.4
2022.1
Issue ID
1375627
Regression
No
Go wide on shader compression
Shader compression is currently single-threaded and frequently takes >1 minute (HDRP scenario). For large shaders it can actuallly take longer to compress the results than it takes to compile the shader variants.Seems like there could potentially be some easy player build wins from going wide on this compression task.
Tested in 2021.2b16 + HDRP 2021.2/staging.
Some timings from a recent player build
Compressed shader 'HDRP/Lit' on d3d11 in 75.56s from 447.65MB to 116.39MB
Compressed shader 'Hair/KajiyaKay' on d3d11 in 435.21s from 8849.37MB to 2486.63MB
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a16