Search Issue Tracker
Fixed in 2020.1.X
Votes
1
Found in
2018.4
2019.2
2019.3
2019.3.0f3
2020.1
Issue ID
1210560
Regression
No
Default Sprite Renderer preset is not applied when dragging a sprite asset from the Project window to the Scene/Hierarchy window
How to reproduce:
1. Open the attached 'project-1210560.zip' project
2. In the Project window select 'SpriteRenderer.preset' asset
3. In the Inspector window observe the set values of the preset
4. Drag the 'Sprite' sprite from the Project window to the Hierarchy window
5. In the Inspector window observe the SpriteRenderer component's values
Expected result: SpriteRenderer.preset values match with the newly created Sprite's SpriteRenderer component's values
Actual result: SpriteRenderer.preset values DO NOT match with the newly created Sprite's SpriteRenderer component's values
Reproducible with: 2018.4.15f1, 2019.2.18f1, 2019.3.0f5, 2020.1.0a19
Could not test with: 2017.4.36f1 (presets not available)
Note: adding the SpriteRenderer to a game object as a new component set the values correctly
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a22