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
- SetComponentEnabled uses class instead of struct when constraining Enableable Component type
- [iOS] Application.deepLinkActivated does not get invoked while app is running when UIApplicationSceneManifest is added in Info.plist
- Inspector scroll area stretches when using components with nested serialized arrays on FBX model prefab instances
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
Add comment