Search Issue Tracker
By Design
By Design in 6000.2.X
Votes
0
Found in
6000.0.25f1
6000.1.0a2
6000.2.0a1
Issue ID
UUM-85881
Regression
Yes
Some Material Variants do not update when dirtied
How to reproduce:
1. Open the “Material_Variants“ project
2. In the menu, select Tools → Initialize Git repo
3. Wait for the “Success!“ log in the Console
4. Select Tools → Run Test
5. Observe the Console
Expected result: “All completed successfully.“ is seen
Actual result: An error with “Test failed“ is seen
Reproducible with: 2023.2.0a19, 6000.0.25f1, 6000.1.0a2
Not reproducible with: 2022.3.51f1, 2023.2.0a18
Could not test with: 2021.3.45f1 (missing functionality)
Reproducible on: Windows 10, macOS 14.6.1 (M1)
Not reproducible on: No other environment tested
Note: Extract the project before every test
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The reason for materials being modified in git in the first place is the change in the material data format in Unity 2022. We changed the representation of one of the internal fields. The materials are changed in git because of that - it happens in Unity 2022.3 as well.
Resolution Note (6000.2.X):
The reason for materials being modified in git in the first place is the change in the material data format in Unity 2022. We changed the representation of one of the internal fields. The materials are changed in git because of that - it happens in Unity 2022.3 as well.