|How do you use documentation throughout your workflow? Share your experience with us by taking this survey.|
For more information on Perforce, visit www.perforce.com.
Follow the setup process described in the Version ControlA system for managing file changes. You can use Unity in conjunction with most common version control tools, including Perforce, Git, Mercurial and PlasticSCM. More info
See in Glossary documentation. See Perforce documentation if you encounter any problems.
Note: If your Perforce workspace has multi-factor authentication enabled you will first need to login through the command line using p4 login2 or by using a visual client like P4V to be able to login in the Unity Editor as well.
Only use this if you know how to work offline in Perforce without a Sandbox. Refer to the Perforce documentation for further information.
If Unity cannot commit your changes to Perforce (for example, if the server is down, or you experience licensing issues), your changes are stored in a separate changeset. If the console doesn’t list any info about the issue, you can use the P4V client for Perforce to submit this changeset to see the exact error message.
You cannot submit changes if you are sharing a workspace with another user. A workspace should be dedicated to one user only.
It’s possible to configure Perforce to revert unchanged files on submit. To do this in P4V, select Connection > Edit Current Workspace, view the Advanced tab and set the value of On submit to Revert unchanged files.