Search Issue Tracker
Won't Fix
Won't Fix in 1.18.X
Votes
0
Found in [Package]
1.18.13
Issue ID
ADDR-2103
Regression
Yes
Subassets are loaded in a wrong order when using packed assets in addressables
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Build the Addressable group
3. Set the Play Mode Script to "Use Existing Build"
4. Enter the Play Mode
5. Inspect the loaded Sprites order (under "GameObject" Sprite Error component)
Expected result: Subassets are loaded in order
Actual result: Subassets are loaded not in a sequential order
Reproducible with: 1.18.13 (2020.3.15f1, 2021.1.16f1, 2021.2.0b6, 2022.1.0a4)
Not reproducible with: 1.18.13 (2019.4.29f1)
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
- Importing a theme through the Inspector allows circular import
- FocusNextInDirection not focusing when used on multiline TextFields
- Single click calls UI Element renaming with a delay when clicked on the UI Element name
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
Resolution Note:
This will not be fixed
Resolution Note (1.18.X):
Objects loaded from an asset bundle are not guaranteed to be in any specific order. Addressables uses AssetBundle.LoadAssetWithSubAssetsAsync and passes back the results in the order they are loaded.