Search Issue Tracker
Fixed in 2021.3.44f1
Fixed in 2021.3.X, 2022.3.X, 2023.3.X, 6000.0.X, 7000.0.0a3, future release
Votes
0
Found in
2021.3.30f1
2022.3.13f1
2023.1.19f1
2023.2.0b11
2023.3.0a7
6000.0.0b12
Issue ID
UUM-17912
Regression
Yes
ShaderGraphs get checked out in Perforce every time they get reimported
Reproduction steps:
1. Create a new HDRP 3D project
2. Create an HDRP Lit Shadergraph asset
3. Enable Perforce in the Project Settings
4. Submit the HDRP Lit Shadergraph asset to Perforce in the Inspector
5. Reimport the HDRP Lit Shadergraph asset
Expected result: No changes to the Shadergraph happen
Actual result: The Shadergraph asset gets checked out
Reproducible with: 2021.2.0b2, 2021.3.6f1, 2022.1.6f1, 2022.2.0a18, 2023.1.0a1
Not reproducible with: 2020.3.36f1, 2021.2.0b1
Reproducible on: MacOS 12.4 (Intel)
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
Add comment