Search Issue Tracker
Won't Fix
Won't Fix in 1.18.X
Votes
0
Found in [Package]
1.18.13
Issue ID
ADDR-2316
Regression
No
Inconsistent behaviour with SpriteManager.atlasRequested callback
Reproduction steps:
1. Open the attached "1089491_PlayStudios-AtlasRequested-v3.zip" project
2. Set Project Settings > Editor > Sprite Packer Mode to Always Enabled
3. Open the "Scenario8" Scene
4. Enter Play Mode
5. Observe the Console
Expected result: No errors
Actual result: Error displaying the inconsistent behaviour with SpriteManager.atlasRequested callback
Reproducible with: 2019.4.30f1, 2020.3.19f1, 2021.1.22f1, 2021.2.0b13, 2022.1.0a10
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
By design. The user is attempting to load a prefab with an Image component that will bind to a SpriteAtlas. Because Sprite Packer Mode is set to "Always Enabled" and the referenced atlas has "Include In Build" disabled, loading the atlas will fail and the SpriteManager.atlasRequested callback will be triggered. Note that this behavior only applies when using the "Use Asset Database" Play Mode Script, which loads all Addressables assets through the Editor AssetDatabase.
Resolution Note (1.18.X):
Added note about Sprite Atlas options in the documentation.