Difference between revisions of "Version control"
Jump to navigation
Jump to search
no edit summary
imported>1shoedpunk (→Errors) |
imported>1shoedpunk |
||
| Line 91: | Line 91: | ||
Save the change and load Skyrim.esm in the CK. You'll get a good number of errors about strings and such, ignore them and press Yes to All. Now it's possible to Check Out forms that belong to Skyrim.esm. Merge any changed Skyrim.esm forms from your ESP into your own ESM, then exit the Creation Kit and revert the flag change. | Save the change and load Skyrim.esm in the CK. You'll get a good number of errors about strings and such, ignore them and press Yes to All. Now it's possible to Check Out forms that belong to Skyrim.esm. Merge any changed Skyrim.esm forms from your ESP into your own ESM, then exit the Creation Kit and revert the flag change. | ||
==Perforce Integration== | |||
Perforce is a 3rd Party Version Management software suite, available for free to groups under 20 members. When set up with the settings documented here, Perforce works hand-in-hand with the Version Control system to keep backups of previous iterations of scripts, and allow for each individual working on a project to pull the latest versions of all project scripts from the Perforce server. The full functionality of it has not yet been uncovered and tested, but research indicates that it may also handle version control for the DialogueViews folder. | |||
With Perforce integration unlocked, it is possible for networked teams working off of a master server using just the Creation Kit and Perforce from a common server for version control. | |||
===Setup=== | |||
First, set up Version Control per the above tutorial. | |||
Download the p4com.dll from this page and add it to your Skyrim folder. | |||
http://public.perforce.com/guest/robert_cowham/perforce/API/p4com/main/ | |||
In SkyrimEditor.ini in your Skyrim folder, make sure that, under the [Papyrus] Settings, you have the following set as it is below: | |||
<source lang="ini"> | |||
sScriptSourceFolder = "Data\Scripts\Source" | |||
sScriptCompiledFolder = "Data\Scripts\" | |||
sCompilerFolder = "Papyrus Compiler\" | |||
bPerforceEnabled = 1 | |||
</source> | |||
www.gameindustry.about.com/b/2012/07/29/version-control-management-and-games.htm | |||
I worked off of this tutorial by Warren Schultz, with a few changes that are necessary for the Creation Kit to properly read your script backup workspace. I also ignored some of the instructions more geared towards setting up Perforce on a server that would host multiple users. If you are aiming to collaborate over a network, you may want to heed them. | |||
I will outline the steps roughly for now, but for step by step instructions please refer to that tutorial. | |||
From http://www.perforce.com/downloads | |||
Install Perforce Server using the suggested default settings. Make your username the same as your Windows username. You must have administrator permissions. | |||
Set up your Perforce Depot to have the name TESVData. This is important, the depot name and subfolders that we will eventually set up in our workspace are paths that are hardcoded into the Creation Kit. | |||
Next, go back to the Perforce site and install the Perforce Visual Client, also using default settings. You can uncheck the Plug-in for Windows Explorer. | |||
Open up your Perforce Server, ensure it is set up per the tutorial, then open P4V (the visual client). You will need to create a new workspace named Papyrus (not sure if this is hardcoded but it seems like it may be. Feel free to test other workspace names). | |||
The workspace root should be in a new folder anywhere on your computer. I have mine in the folder above my Skyrim directory, since that is where the Source folder needed for LOD generation is kept. Don't add files yet if prompted. | |||
In Windows Explorer, open up the new directory you created and add the following folders: | |||
\current\Source\scripts | |||
Copy all of the contents of your Skyrim/Data/Scripts folder into the Scripts subfolder. This should be thousands of .psc files and the subfolders for each DLC. If you are using a custom prefix for your project, you will need to set it in your Creation Kit preferences as. Do not rename script fragments manually, even through the Creation Kit. | |||
Refresh your Perforce Client and you should see the new subfolders and files. Right click on the scripts folder and click add. It should put your files into a changelist. Then, right click again and click submit to commit those changes to the depot. You will need to add a comment, it can be anything. | |||
You should now be able to load up the Creation Kit and go to your preferences. At the very end is a tab for Perforce integration, where you can select your new workspace. Select it and hit apply. You shouldn't get any error messages but if you do one of the steps earlier went wrong. | |||
==Troubleshooting== | ==Troubleshooting== | ||