Search Issue Tracker

Active

Under Consideration for 6000.6.X

Votes

0

Found in

6000.3.11f1

6000.4.0b12

6000.5.0a8

6000.6.0a1

Issue ID

UUM-137746

Regression

No

Editing and saving a GraphToolkit custom graph does not automatically get checked out when using Perforce integration

Version Control

-

Steps to reproduce: (For Package)
1. Create a new project
2. Install the com.unity.graphtoolkit package (Window → Package Management → Package Manager)
3. Import the “VisualNovelDirector” sample (Package Manager → Graph Toolkit → Samples)
4. Connect to your Workspace in Perforce (Edit → Project Settings → Version Control)
5. Submit your project to Perforce
6. Edit the “My Visual Novel Graph” asset and save
7. Observe the Version Control window

Alternative steps to reproduce: (For Module)
1. Create a new project
2. Import the attached “MySimpleGraph.cs” script
3. Create the folder “Editor” in the Assets folder
4. Place the imported “MySimpleGraph.cs” script into the “Editor” folder
5. Connect to your Workspace in Perforce (Edit → Project Settings → Version Control)
6. Submit your project to Perforce
7. Create a custom graph (Tools → Graph Toolkit → Create My Custom Graph)
8. Submit the created graph to your Perforce workspace
9. Open the created graph and edit it by adding a node
10. Save the graph
11. Observe the Version Control window

Actual Result: The file does not show up in “Outgoing” section
Expected Result: The file appears in the “Outgoing” section

Reproducible with: 6000.2.0a9, 6000.3.11f1 (Package), 6000.4.0b12, 6000.5.0a8, 6000.6.0a1 (Module)
Could not test with: 6000.0.70f1 (Graph Toolkit has a minimum version of 6000.2.0a9)

Reproducible on: macOS Sequoia 15.7.4 (M1 Max)
Not reproducible on: No other environments tested

Note:
- You can still manually check out the asset
- Does not reproduce with Shader Graphs, Script Graphs

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.