Search Issue Tracker
Fixed in 7.0.0
Votes
0
Found in [Package]
5.6.1
Issue ID
1136543
Regression
No
Saving a Shader Graph does not prompt the user to checkout the file in VCS and saving read-only graphs results in a crash
How to reproduce:
1. Create a new LWRP/HDRP Project
2. Set it up to use Perforce's version control
3. In the Project Window create a new Shadergraph
4. Double click the graph, make changes and save
Expected result: A dialog is shown, stating that the Shader Graph is currently not editable. In the case of Perforce, if it’s an option to checkout the file to make it editable, allow the user to do so from this dialog.
Actual result: The Shader Graph is checked out and saved without asking the user.
Reproduced with: Shadergraph version 5.7.2; 5.6.1
Not reproducible with: Shadergraph version 5.3.1; 5.2.3
Note: Reproducible with both LWRP and HDRP
Additionally, to reproduce the crash:
1. Make another new Shadergraph and submit it
2. Make sure that it is not checked (Read-only)
3. Disconnect the version control
4. Open the graph, add any new property and close the graph
5. A save prompt will appear, click save
6. Observe the crash
Crash reproduced on: 2019.3.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- RenderDoc Capture Frame can't be completed after Particle System is simulated
- Editor crashes when attempting to connect the client machine to the host machine
- CameraDepthTexture is flipped upside down when URP is rendering without the final blit
- Camera.current returns null when Camera.targetTexture is set to null in OnPostRender
- Crash on BaseHierarchyProperty::Next when opening a specific project
Add comment