Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
Issue ID
1189850
Regression
No
Addressable asset loading takes longer than loading them using Resources.LoadAll
To reproduce:
1. Open the QA's attached project
2. Play in Editor
3. Build and Run on mobile or standalone
Expected: Loading 1000 scriptable objects using Addressables.LoadAssetsAsync takes a shorter amount of time than loading them using default Resources.LoadAll
Actual: Loading 1000 scriptable objects using Addressables.LoadAssetsAsync takes a longer amount of time than loading them using default Resources.LoadAll
Reproduced with: 2018.4.11f1, 2019.2.9f1, 2019.3.0b6, 2019.2.9f1, 2020.1.0a8
The below numbers in brackets are times to load 1000 scriptable objects using (Resources.LoadAll, Resources.LoadAsync, Addressables.LoadAssetsAsync):
Editor 2019.2.9f1, 2019.3.0b6, 2019.2.9f1, 2020.1.0a8 (0.25 , 10.53 , 16.98)
Only with Editor 2018.4.11f1 it was (0.1, 0.6, 20)
On mobile (0.34, 11.62, 15.69)
On Windows standalone (0.03, 0.28, 0.35)
Not reproduced with 2017.4 - no Addressables package for that version
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
Due to other priorities we will not be addressing this issue at this time.