Search Issue Tracker
Fixed in 5.5.1
Votes
5
Found in
5.3.1p1
Issue ID
766056
Regression
No
[Shaders] Shader compilation is slow for shaders with massive amounts of shader_features
Shader with >100 million possible variants (via shader_feature/multi_compile) is having shader import time problems.
Surface shaders to have problems (known issue, each variant is doing an analysis step). But this one is supposedly a non-surface shader.
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
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
Fewes
Apr 18, 2017 15:09
This is marked as fixed, but I am experiencing this exact issue on 5.5.2f1. I combine about 18 shader features, and shader compile/scene load times are absolutely excruciating. Are there any details on this "fix"?
michal_gjk
Dec 29, 2016 12:17
I reported my issue as case 825137 which was determined to be a duplicate of this one.
With the new unity 5.5 returning more verbose compiler errors this is what I get:
Parse error: syntax error, unexpected $end, expecting TOK_SHADER
This happens after an extremely long time so it must be something in the generated intermediate shader code -nothing on my part.
InversedOne
Aug 30, 2016 07:28
Having same issues, when we get to over 100 million variants compile time is awful and scene loading is starting to suffer aswell.
watsonsong
Jun 07, 2016 10:05
I combine 18 shader_feature, and the unity take almost 8G memory when loading, and extremely slow.