LFS Editor/Guides/Collaboration

Vehicle Mods
LFS Editor Vehicle Mod Features Vehicle Mod Submission Vehicle Mod Licenses
Vehicle Mods at LFS.net

There is a feature in the LFS Editor to help with sharing a complete vehicle mod with its development files. Unlike exporting for upload, this function copies png files rather than creating dds textures. It doesn't automatically create a zip. It simply gathers all the files and saves them in a structured share folder ready for copying.

After creating the initial vehicle and working on it a bit, you can click export to share vehicle for development at the top right.

That exports veh, engine sound, animations, png in a directory structure in a 'share' folder. So you can zip up those folders inside 'share', send it to your collaborator who will unzip it to 'data' on their computer. Now the exact same mod exists on both computers.

From that point on, if only the collaborator works on it they could do the same to return the updated mod back to you. But if you both continue to work on the project at the same time you will probably manually share updated files.

Two people should usually not work on the actual vehicle editor settings at the same time, as you would need to manually merge the changes. It may be that one person works on the vehicle settings, while another works on the 3D model. The 3D model can be saved out from the modeller and sent to be loaded in on the remote computer. A complete wheel style file can also be saved or loaded - LOAD WHL / SAVE WHL in the wheel object section. Engine can also be saved separately.

There is also a function export for DV in the Textures section. This copies all png textures to data\png_export. For example the person working on the 3d model might save the 3D model into data\3dob and do a png export then send those files to the person working on the veh. The veh person would then save the png files into data\png load the model (in the modeller, accessed from the vehicle editor).