Search Issue Tracker
Fixed
Fixed in 2021.3.44f1, 2022.3.47f1, 2023.3.0a10, 6000.0.14f1, 7000.0.0a3
Votes
0
Found in
2021.3.30f1
2022.3.13f1
2023.1.19f1
2023.2.0b11
2023.3.0a7
6000.0.0b12
7000.0.0a1
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
- UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
Add comment