Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.19.19
1.20.0
1.20.3
1.20.5
Issue ID
ADDR-2947
Regression
No
AsyncOperationHandle.PercentComplete always returns 0 when loading from cache
Reproduction steps:
1. Open the attached project "ADDR-2947 repro.zip"
2. Click “Build > New Build > Default Build Script” in the Addressables Groups window
3. Open the “Loader” Scene
4. Enter Play mode
Expected result: The current loaded percentage is logged in the Console window
Actual result: “Loading percent = 0” is logged multiple times
Reproducible on: 1.19.19 (2020.3.39f1, 2021.3.9f1), 1.20.0 (2022.1.14f1), 1.20.3 (2022.2.0b6), 1.2.5 (2023.1.0a9)
Reproducible with: macOS 12.4 (Intel)
Comments (2)
-
BrianDuffyGames
Feb 13, 2025 03:58
This is crazy! Responding "Won't Fix" on such a critical bug is completely negligent. Loading bars are a basic function of video games, but I guess that's not your target market anymore is it.
-
unity_028AE3B1F1BC5DECE8AD
May 15, 2024 13:54
Wow, a bug that causes issues such as preventing being able to show an accurate loading bar when loading async, and unity just "won't fix". Probably too busy working on the next batch of new editor bugs to implement.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.