Difference between revisions of "Team Files"
m (Text replacement - "{{toc}}" to "") |
|||
Line 9: | Line 9: | ||
* to merge a team file you have to load the master project and import the team file | * to merge a team file you have to load the master project and import the team file | ||
* after all team files are imported you can export a new team file and all files get a new revision -> start workflow at beginning | * after all team files are imported you can export a new team file and all files get a new revision -> start workflow at beginning | ||
− |
Revision as of 00:52, 4 November 2014
If multiple users are working on the same .ved file you have to use team files. Load the project (.ved file) in the editor and export a team file. In the game section under the tab 'Game info' you find the project type. Possible values are 'Default', 'Master project' and 'Team file'. For a new project the project type is 'Default'. When you export a team file the project gets the project type 'Master project'. The exported ved file gets the project type 'Team file'. On the first export the Revision (also in the 'Game info' tab) is set to 1. The Revision is increased after each export, the exported team file always gets the same Revision. When you import a team file it should have the same Revision as the master project.
The workflow is the following:
- export team file
- the team file can be distributed to one or multiple team members
- you can work on the master project and on the team file(s) in parallel
- keep in mind that primitive types cannot be merged (e.g. scripts cannot be merged because a script is internally just a string), it is recommended that you work on separate objects (agree in advance who is working on which character/scene etc.) to avoid conflicts when merging the files
- after a certain time you should collect all modified team files and merge them into the master project
- to merge a team file you have to load the master project and import the team file
- after all team files are imported you can export a new team file and all files get a new revision -> start workflow at beginning