Search Issue Tracker
Fixed
Fixed in 2021.3.20f1, 2022.2.1f1, 2023.1.0a6
Won't Fix in 2022.1.X
Votes
0
Found in
2022.2.0a9
Issue ID
UUM-17896
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
- Screen.resolutions returns resolutions that include the notch area when called on Macs with a notch
- Shader Graph Editor Throws Exception When Deleting Custom Function Node
- Outlines are visible on Mesh when Alpha Clipping is enabled and Surface Type is set to Opaque
- UI Elements are not getting focused when navigating through using arrow keys if they’re placed in a specific position
- Deleted scene selection is wonky in the Build Settings
Resolution Note (fix version 2022.2.1f1):
Fixed in 2022.2.1f1
Resolution Note (2022.1.X):
No further releases in 2022.1
Resolution Note (fix version 2021.3.20f1):
Fixed in 2021.3.20f1