Search Issue Tracker
Fixed in 2018.3.X
Won't Fix in 2017.1.X, 2017.2.X, 2017.4.X, 2018.1.X
Votes
0
Found in
2017.1.3p3
Issue ID
1038179
Regression
Yes
Image components not displaying sprite data when instantiated from a prefab and trigger a SpriteAtlas request
Reproduction steps:
1. Open the attached project "sprite-atlas-load-sprite-failure.zip";
2. Open the scene1.unity;
3. Enter a play mode;
4. Press "Load Image" button;
5. Observe three images in the Game View.
Expected results: all three images will look the same.
Actual results: Only one on the right looks like expected.
Reproduced on. 2017.1.3p3, 2017.1.4f1, 2017.2.3f1, 2017.3.2f1, 2018.1.1f1, 2018.1.1f1, 2018.2.0b5, 2018.3.0a1.
Not reproduced: 2017.1.3p2 or lower.
Reproduces on both OSX and on the iOS build.
Note: If pressing "Load Image" button again after the first time, second time sprites are loaded correctly.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment