Search Issue Tracker
Fixed in 4.3.X
Votes
0
Found in
3.0
Issue ID
564121
Regression
No
Shaders: Sometimes material properties aren't saved
When there's a material created, and a shader adds new properties behind it's back (i.e. material is not loaded at that time), then these new shader properties aren't "saved". They are visible in the inspector, but aren't actually saved to disk. Confusing!
Workaround is changing the shader of the material to something else, and then changing it back.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Add comment