LFS Editor/Guides/Collaboration - Revision history

Flame CZE at 10:29, 14 February 2026

2026-02-14T10:29:42Z

Flame CZE at 21:31, 7 February 2024

2024-02-07T21:31:02Z

Flame CZE: links & folder

2024-01-26T16:24:44Z

links & folder

Flame CZE: Flame CZE moved page Vehicle Mod Collaboration to LFS Editor/Guides/Collaboration

2024-01-26T14:59:41Z

Flame CZE moved page Vehicle Mod Collaboration to LFS Editor/Guides/Collaboration

Flame CZE at 13:55, 26 January 2024

2024-01-26T13:55:33Z

Flame CZE at 22:46, 1 December 2023

2023-12-01T22:46:56Z

Flame CZE at 22:40, 1 December 2023

2023-12-01T22:40:55Z

Flame CZE: Created page with "There is a feature to help with sharing a complete vehicle mod with its development files. Unlike exporting for upload, this function copies png files rather..."

2023-04-20T21:59:23Z

Created page with "There is a feature to help with sharing a complete vehicle mod with its development files. Unlike exporting for upload, this function copies png files rather..."

New page

There is a feature to help with sharing a complete [[Vehicle Mods|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 {{old button|export to share vehicle for development|#959595}} 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 - {{old button|LOAD WHL|#a1ffa1}} / {{old button|SAVE WHL|#a1ffa1}} in the wheel object section. Engine can also be saved separately.

There is also a function {{old button|export for DV|#a1a1ff}} in the {{old button|Textures|#a1ffa1}} 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).

@@ Line 3: / Line 3: @@
 There is a feature in the [[LFS Editor]] to help with sharing a complete [[Vehicle Mods|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 {{old button|export to share vehicle for development|#959595}} at the top right.
+After creating the initial vehicle and working on it a bit, you can click {{old button|export to share vehicle for development|darkgrey}} at the top right.
 That exports veh, engine sound, animations, png in a directory structure in a {{folder|share}} folder. So you can zip up those folders inside {{folder|share}}, send it to your collaborator who will unzip it to {{folder|data}} on their computer. Now the exact same mod exists on both computers.
@@ Line 9: / Line 9: @@
 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 - {{old button|LOAD WHL|#a1ffa1}} / {{old button|SAVE WHL|#a1ffa1}} in the [[../../Vehicle Editor/Wheel Object|wheel object]] section. Engine can also be saved separately.
+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 - {{old button|LOAD WHL|palegreen}} / {{old button|SAVE WHL|palegreen}} in the [[../../Vehicle Editor/Wheel Object|wheel object]] section. Engine can also be saved separately.
-There is also a function {{old button|export for DV|#a1a1ff}} in the {{old button|Textures|#a1ffa1}} section. This copies all png textures to {{folder|data|png_export}}. For example the person working on the 3D model might save the 3D model into {{folder|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 {{folder|data\png}} and load the model in the [[Modeller|modeller]], accessed from the [[Vehicle Editor|vehicle editor]].
+There is also a function {{old button|export for DV|paleviolet}} in the {{old button|Textures|palegreen}} section. This copies all png textures to {{folder|data|png_export}}. For example the person working on the 3D model might save the 3D model into {{folder|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 {{folder|data\png}} and load the model in the [[Modeller|modeller]], accessed from the [[Vehicle Editor|vehicle editor]].
 [[Category:LFS Editor Guides|{{SUBPAGENAME}}]]

←Older revision		Revision as of 21:31, 7 February 2024
Line 13:		Line 13:
	There is also a function {{old button\|export for DV\|#a1a1ff}} in the {{old button\|Textures\|#a1ffa1}} section. This copies all png textures to {{folder\|data\|png_export}}. For example the person working on the 3D model might save the 3D model into {{folder\|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 {{folder\|data\png}} and load the model in the [[Modeller\|modeller]], accessed from the [[Vehicle Editor\|vehicle editor]].		There is also a function {{old button\|export for DV\|#a1a1ff}} in the {{old button\|Textures\|#a1ffa1}} section. This copies all png textures to {{folder\|data\|png_export}}. For example the person working on the 3D model might save the 3D model into {{folder\|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 {{folder\|data\png}} and load the model in the [[Modeller\|modeller]], accessed from the [[Vehicle Editor\|vehicle editor]].

−	[[Category:LFS Editor Guides]]	+	[[Category:LFS Editor Guides\|{{SUBPAGENAME}}]]

←Older revision		Revision as of 13:55, 26 January 2024
Line 1:		Line 1:
−	{{Infobox ~~vehicle mods~~}}	+	{{Infobox LFS Editor}}

	There is a feature in the [[LFS Editor]] to help with sharing a complete [[Vehicle Mods\|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.		There is a feature in the [[LFS Editor]] to help with sharing a complete [[Vehicle Mods\|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.

←Older revision		Revision as of 22:46, 1 December 2023
Line 14:		Line 14:

	[[Category:LFS Editor Guides]]		[[Category:LFS Editor Guides]]
−	~~[[Category:LFS Editor]]~~

@@ Line 1: / Line 1: @@
-There is a feature to help with sharing a complete [[Vehicle Mods|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.
+{{Infobox vehicle mods}}
 After creating the initial vehicle and working on it a bit, you can click {{old button|export to share vehicle for development|#959595}} at the top right.
@@ Line 10: / Line 12: @@
 There is also a function {{old button|export for DV|#a1a1ff}} in the {{old button|Textures|#a1ffa1}} 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).