Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4.9f1
2020.2
Issue ID
1277325
Regression
No
SpriteAtlasManager.atlasRequested event silently fails if the sprite is called upon before the event is triggered
How to reproduce:
1. Open tester-attached project (SpriteAtlasEvent.zip)
2. Open the SampleScene
3. Enter Play Mode - see that a warning is printed from atlasRequested event
4. Open the AddressableImage.cs script and uncomment line 24(Debug.Log inside OnValidate())
5. Enter Play Mode again
Expected result: a warning is printed from atlasRequested event
Actual result: no warning is printed from atlasRequested event
Reproducible with: 2018.4.27f1, 2019.4.10f1, 2020.1.6f1, 2020.2.0b3
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (2020.2.X):
Since OnValidate awakes the Sprite even before entering Playmode, the atlasRequested does not get registered by design. Also note OnValidate is only called in Editor mode.
Please modify OnValidate as follows :
protected void OnValidate()
{
#if UNITY_EDITOR
if (!UnityEditor.EditorApplication.isPlayingOrWillChangePlaymode)
Debug.Log(image.sprite);
#endif
}