Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.4p4
Issue ID
984168
Regression
No
Animator Controller causes Asset Bundle to load significantly slower
To reproduce:
1. Open attached project;
2. Open "Main" scene and enter Play mode;
3. Click buttons "LoadAsbOne", "LoadAsbCtrl" and "LoadAsbNoCtrl" and see the loading results in the Console.
Note:
LoadAsbOne: loads all assets built in one Asset Bundle;
LoadAsbCtrl: animation and animator built into a common Asset Bundle. Other assets built in a bundle. Prefab Avatar_Theresa_C1_YD_bak's animator controller is not null.
LoadAsbNoCtrl: animation and animator built in a common Asset Bundle. Other assets build in a bundle. Prefab Avatar_Theresa_C1_YD_bak's animator controller is null.
Result: when a prefab in the Asset Bundle has an Animator Controller, loading it from Streaming Assets takes significantly more time:
LoadAsbOne: 187.5 ms
LoadAsbCtrl: 1128.4 ms
LoadAsbNoCtrl: 31.4ms
Reproduced on versions: 5.6.5f1, 2017.1.3f1, 2017.2.1p1, 2017.3.0p1, 2018.1.0b1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment