Search Issue Tracker
Fixed in 2017.4.X
Votes
0
Found in
5.6.0b4
Issue ID
881722
Regression
No
Shader compilation times regressing and caching is non-optimal
Steps to reproduce:
1. Create a new project
2. Import Standard Assets Image Effects package
3. Add several Image Effect scripts(e.g. at least Bloom, DoF, Twirl, Vortex, Sun shafts...)
4. Enter Play mode
Expected result: quick enter into Play mode
Actual result: the first launch takes a relative long time to load, following launches enter play mode quickly
Reproduced on 5.4.5p1, 5.5.2p4, 5.6.0f2, 2017.0a4 on Windows 10
Not reproduced on OSX
5.4.5p1 load times are slightly better
Notes:
-This behavior resets on every restart of the system, may be required to do so once scene is set-up (cant be cached effectively)
-Not post-processing related (general shader compilation)
-Reproducible with other effects packages besides the Standard Assets(e.g. Post-Processing Stack)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
Add comment