Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.3.0p2
Issue ID
991101
Regression
No
Dragging multiple sprites to object with Image component creates Sprite Renderer animation instead of Image component animation
Steps to reproduce:
1. Open attached “ImageAnimation.zip” Unity project
2. Expand “Spritesheet” asset in Project window
3. Select multiple sprites
4. Drag selected sprites to “Image” object (child of Canvas) in Hierarchy
Expected results:
A new animation is created where Image component Source Image value is animated
Actual results:
A new animation is created, Sprite Renderer component is added to the object and Sprite value is animated
Reproduced in: 2018.2.0a1, 2018.1.0b4, 2017.3.0p3, 2017.2.1p2,, 2017.1.3f1, 2017.1.0a1
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
- Addressables Profiles and Analyze windows no minimum window size
- [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”
Add comment