Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.26f1
6000.0.0b16
6000.1.0a7
Issue ID
UUM-70410
Regression
No
Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
Steps to reproduce:
1. Have a project with lots and lots of individual shaders. A production example of a project with 1000 VFX Assets resulted in over 15k individual shaders. Shader compilation during build takes > 1hour on i9-10980xe
2. Build the project, watch CPU utilisation during shader compilation stage.
Actual results: Shader compilation time during build can be incredibly slow as the shaders are compiling linearly on a single-thread. The number of shader-variants (post-stripping) should be very low so this scenario is not taking advantage of shader-variant multi-threading.
Expected results: Individual shaders are compiled over multiple threads to take advantage of multi-threading.
Reproducible with versions: All
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Notes:
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
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
- LocalizationSettings.InitializationOperation hangs when re-entering Play Mode with Domain Reload disabled
Resolution Note:
After careful consideration, we decided we will not fix this issue at this point.
We may reevaluate it later.
Resolution Note:
After careful consideration, we decided we will not fix this issue at this point.
We may reevaluate it later.