Helix Core — version control from Perforce — offers plugins and integrations for everyone on your team. Developers, designers, and third-party contributors can use the tools they love. And you can still maintain a single source of truth across teams.
Full Video Transcript
In this video, you’ll learn about versioning operations using the P4Connect plug-in within Unity.
Here we are in Harry’s project. To edit a file, you need to check it out. To check-out a file, right-click on the file and select “Perforce>Checkout”. A red checkmark appears on the file. Alternatively, you can simply open a file and it will automatically be checked-out.
Harry has edited this “readme” file by adding, “P4Connect RULES!” He is now ready to submit this changed file to the server. One method is to go to Window>Perforce to open the Perforce Changes window. A better way, however, is to right-click on the file, and select Perforce>Commit. This will pull up the same window, but now just the “readme” file is checked for submit. The boxes on the left allow you to select which files will be submitted at this time.
Before you submit, a description needs to be added. Next, click Submit Selected, and then Submit. Notice the “readme” file is no longer checked-out.
You may also lock files—particularly binary files. Locking ensures that no other user can edit the files while you are working on them. First, the file needs to be checked-out. With the file selected, right-click and choose Perforce>Lock. The file now has the lock decorator.
Let’s switch over to Sally’s game.
You can see that the “Rabbit_Eye” file has a blue checkmark, indicating that another user has the file checked out. It is also locked, which means she cannot modify the file.
The “readme” file now has a yellow triangle, indicating that she no longer has the latest version since Harry just edited it. Right-click on the file and select, Perforce>Get Latest Revision. The file now has a green dot indicating that she has the updated version. Notice the “P4Connect RULES!”
When you create a new file, or even drag-and-drop a file into your Project window, a red plus decorator gets applied to the file. New files are automatically Marked for Add in the Perforce Changes window. You can decide when to submit new files to the server by checking them here. Note, that the icons on the far right tell you whether or not a metafile is associated with the files. In this case, 3 of the files have metafiles associated with them.
When files are opened in Unity, P4Connect automatically mirrors the changes within the P4V Default Changelist. Thus, the Pending Change Window may have additional files listed.
It’s a good idea to keep P4V handy--logged into your current workspace. If there is a conflict during a Check-in, Perforce will move files from a Pending Default changelist to a numbered changelist. P4Connect does not see numbered changelists, so you’ll need to resolve conflicts in P4V. Use P4V to move the files back into the default changelist so they will be recognized once again in P4Connect.
Here is a great online resource--the Perforce Workshop. The Overview tab describes how P4Connect releases are distributed and has installation instructions in documentation and in the release notes. The Files tab shows source code, and the Job tab is where you can browse jobs, which are another name for bugs that have been filed against P4Connect. Also, read the Forums for community discussions about P4Connect.
Join the Workshop and help the Community grow!
Thank you for watching.