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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment