Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.21.20
Issue ID
ADDR-3656
Regression
No
AssetBundleResource.Update is called multiple times on the same frame when in the Play mode
Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Open the "Assets/Scenes/SampleScene.unity" scene
3. Open the Addressables Groups window (Window > Asset Management > Addressables > Groups)
4. Create a new Default Build Script in the Addressables Groups window (Build > New Build > Default Build Script)
5. Enter the Play mode
6. Press the “Button” in the Game view
7. Observe the Console
Expected result: No debug messages “--> here frame: “ with the same frame count
Actual result: Multiple debug messages “--> here frame: “ with the same frame count are printed
Reproducible with: 1.21.20 (2021.3.36f1)
Couldn’t test with: 2.0.8 (Debug messages are not printed)
Reproducible on: macOS Sonoma 14.3.1 (M1 Max)
Not reproducible on: No other environment tested
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
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Resolution Note:
Fixed issue where operation that uses WaitForCompletion can timeout much earlier than it should. Note that due to the nesting of addressable operation callbacks, it's possible for AssetBundleResource.Update to be called multiple times on the same frame when using WaitForCompletion.
Resolution Note:
Fixed issue where operation that uses WaitForCompletion can timeout much earlier than it should.