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
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a22