Search Issue Tracker
Fixed
Fixed in 1.21.1
Votes
0
Found in [Package]
1.21.1
Issue ID
ADDR-2170
Regression
Yes
[Addressables] Increased game loading time when using the Addressable package 1.18.4+
How to reproduce:
1. Open the "case_1355900" project
2. Open the "SampleScene" Scene
3. Build the Addressables bundles by clicking "Windows -> Asset Management -> Addressables -> Groups -> Build -> New Build -> Default Build Script"
4. Build and run the project by clicking "File -> Build and Run"
5. Open the "%LOCALAPPDATA%\\Gentlymad Studios\\AddressablesLoadingPerformance\\Player.txt" text file
6. Observe the loading time (in ms) after "Total time:"
Expected result: the loading time is ~6000 ms
Actual result: the loading time is ~15000 ms
Reproducible with: 1.18.4, 1.18.15 (2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a5)
Not reproducible with: 1.8.2 (2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a5)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 1.21.1):
Fixed in 1.21.1
There was a change in the implementation of the .Task API for async operation handles that was needed to ensure correctness. This does affect the loading behavior and results in a significant slowdown when many items are loaded as in this bug report. there are other ways of loading that do not exhibit this performance hit and should be used instead