Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.2
2019.3
2019.3.0b12
2020.1
Issue ID
1199590
Regression
No
Preset Asset Icons for Assets using Editor.RenderStaticPreview do not change when Preset properties are changed while Project Wi
Preset Asset Icons for Assets using Editor.RenderStaticPreview do not change when Preset properties are changed while Project Window Icon Size is set to the minimum.
----
Example with Tile Asset:
Tile preset asset Icons image colour does not change on changing the color property.
Steps to repro:
1. Create a new project.
2. Window > Package Manager> 2D Tilemap Editor > Install.
3. Project Window > Right Click > Tile > Save.
4. Select Tile asset > Assign Sprite > Create its preset.
5. Change color property in Tile preset asset.
Actual Result:
Tile preset asset Icons image colour does not change
Expected Result:
Tile preset asset Icons image colour should be changed.
Tested with Unity Version: 2020.1.0a14, 2019.3.0b12, 2019.2.0f1.
Tested with Package Version: 1.0.0.
Environment:
Windows 10 & Mac 10.14.
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note (2021.1.X):
This issue requires a lot of changes in the underlying Preset mechanism to be fixed and has a minor impact on the current product.
For this reason, we are not fixing this for now.
But, an internal development task has been added to our roadmap to fix this issue in our next Preset iteration phase that will be part of 2021.2 development cycle.