Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.2.19f1
2021.3
2022.1
Issue ID
1419488
Regression
No
Materials with the HDRP/Decal shader are updated when the Scene is saved
Reproduction steps:
1. Open the user's attached "PlasticBug.zip" project
2. Make sure you enabled the "Manual Checkout for Unity Assets" in Window > Plastic SCM > Settings
3. Open the "SampleScene" Scene
4. Go to Hierarchy > GameObject > Prefab Mode
5. Disable the "GameObject" GameObject
6. Save the Scene
7. Open and observe the Plastic SCM window
Expected result: Decal.mat asset changes aren't checked in the Pending Changes tab
Actual result: Decal.mat asset changes are checked in the Pending Changes tab
Reproducible with: 2019.4.40f1, 2020.3.36f1, 2021.3.5f1, 2022.1.0b15
Not reproducible with: 2022.1.0b16, 2022.1.7f1, 2022.2.0a17, 2023.1.0a1
Note: If other more common shaders (HDRP/Lit or HDRP/Unlit) are used there are no date changes made in the .mat file
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
- Diagnostics logs are missing, duplicated, or out of order when viewing Player sessions in Cloud Diagnostics
- Prefab Overrides “Apply” button is too big and overlaps with the context menu’s outline
- Prefab Overrides “No Overrides” text is too large, and the the Context Menu of the Parent GameObject has a lot of empty space when opened
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b16
It seems to be a special behavior of Unity with HDRP. Every time the scene is saved, the materials with the HDRP/Decal shader are updated. You don't see any changes to the .mat files or their metas, but the date of the .mat file changes. Plastic detects the date change and does an automatic checkout to reflect the change. This is the correct behavior in version control.