Search Issue Tracker
Fixed
Fixed in 2021.3.17f1, 2022.2.3f1, 2023.1.0a23
Votes
0
Found in
2021.3.13f1
2022.1.22f1
2022.2.0b14
2023.1.0a17
Issue ID
UUM-19330
Regression
Yes
Changing the color for material is not available if shader is set to Sprites/Default
Reproduction steps:
- Open “MaterialTest” project
- Select “New Material” in the Asset folder
- Note that in the Inspector user can change the Albedo (color) of the material
- In the Inspector for the “New Material” change Shader to Sprites/Default
- Observe the Inspector
Expected result: user can still change the color of the material
Actual result: user can’t change the color of the material
Reproducible with: 2021.3.7f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b14, 2023.1.0a17
Not reproducible: 2020.3.41f1, 2021.3.6f1
Reproduced on: Windows 10
Note: in Sprites/Default shader the Albedo alternative would be called Tint. User can change color if the shader is reverted back to Standard
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
- Pressing “+” to add new Property throws “NullReferenceException” error after deleting Categories with Properties from Blackboard
- Reuse Collisions Callbacks is not enabled by default when opening a new project with HDRP template
- Bloom and Exposure Artifacting around GameObject appears when setting Scale of Z Axis to 0
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
Resolution Note (fix version 2022.2.3f1):
fixed in 2022.2.3f1
Resolution Note (fix version 2021.3.17f1):
fixed in 2021.3.17f1