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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment