Search Issue Tracker
Fixed in 2021.3.20f1
Fixed in 2021.2.X
Votes
0
Found in
2021.2.0a18
Issue ID
UUM-17895
Regression
Yes
Changes made to assets are not saved when renaming the asset while using Perforce
Reproduction steps:
1. Set up users attached project to work with Perforce
2. Select M_Test1 Material in the Project window
3. Set Metallic value to 1
4. Rename the M_Test1 Material in the Project window
Expected result: Metallic value is set to 1
Actual result: Metallic value reverts back to 0.5
Reproducible with: 1.15.15 (2021.2.0a18, 2021.2.19f1, 2021.3.0f1, 2022.1.0b15, 2022.2.0a9
Not reproducible with: 1.15.15 (2020.3.33f1, 2021.1.26f1, 2021.2.0a17)
Could not test with: 2019.4.37f1 (could not downgrade the project)
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 (fix version 2021.3.20f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-17896
Resolution Note (fix version 2021.2):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-17896