Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.4
2020.1
2020.1.13f1
2020.2
2021.1
Issue ID
1300620
Regression
No
LoadAssetAsync does not obey Application.backgroundLoadingPriority
How to reproduce:
1. Open the attached project ("ABC.zip")
2. Open the Profiler and start recording
3. Enter Play mode and press "L" on your keyboard
Expected results: The asset is loaded without a big hit in performance with low thread priority because Application.backgroundLoadingPriority is set to low
Actual results: The asset is loaded with a big hit in performance
Reproducible with: 2019.4.17f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0b1
Could not test with: 2018.4.30f1
Comments (2)
-
Peter77
Dec 28, 2020 16:03
-
ExodusOTH
Dec 28, 2020 15:55
The wording on this issue appears to be off, for the “Actual results: The asset is loaded with low thread priority because Application.backgroundLoadingPriority is set to low”. This is what the documentation says *should* be happening, however it is not, hence why this bug ticket & issue tracker were created. The Application.backgroundLoadingPriority is having no effect on the Addressables threading priority.
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
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
Resolution Note (2021.2.X):
Can't reproduce without crucial info from user