Search Issue Tracker
Won't Fix
Votes
1
Found in
5.5.2f1
Issue ID
895319
Regression
No
Starting Resources.LoadAsync will delay upcoming AssetBundle.LoadAsset's loading
Reproduction steps:
1) Download and open user's attached project
2) Build asset bundles ((upper menu) BuildTools -> Build -> Build AssetBundles for Android)
3) Build and run on any Android device
4) Press 'Load' button
-- Notice that in left top corner loading time is printed
Actual result:
When Resources.LoadAsync called next AssetBundle.LoadAsset takes 300 - 600 ms to load.
Expected result:
Resources.LoadAsync should not affect AssetBundle loading time.
Tested with Android and iOS and Windows 10. Every platform reproduces this issue.
Reproduced with:
2017.1.0a5, 5.6.0f2, 5.5.2p4, 5.4.5f1
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