Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Fixed in 2017.4.X
Votes
3
Found in
2017.1.1f1
Issue ID
959858
Regression
No
Animated Procedural Textures break async level loading
how to reproduce:
build player (any platform will do) and run. To repro in editor open loader scene and play.
you can tweak TestLoad.cs to load Test_Simple scene instead to see that it will work just fine
original bug was happening because ios does async level load for "first scene" (thats different from all other platforms)
and due to the way we manage splash screen it resulted in black screen (faded-out splash screen rendering)
Expected fix in plugin from Allegorithmic.
Comments (1)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Thermos
Nov 30, 2017 02:54
Not only level async loading is effected, all AsyncOpertion would be blocked if this bug happens, including Resources.LoadAsync()(I'm pretty sure about this one).
If you refocus unity, or simply call Resources.Load(), all those hanging async opertions would be finished at once, but you can't do Resources.Load() every update as a workaround because Resources.Load() takes much much much much more time(0.01ms -> 80ms) than it usually would cost if this bug is happening.