XML:TRGE: Difference between revisions

XML:TRGE (view source)

439 bytes removed , 30 March 2021

attempting an update to the export/import section, but I don't know how to actually replace the data intelligently

18,700

edits

@@ Line 33: / Line 33: @@
 ==Embedded M3GM==
 ===Export===
-You would need to cut TRGE instance so that only the M3GM and its connected instances remain and convert it to oni.
+To extract the DAE of the trigger head, use:
-:    onisplit -extract:xml output_folder input_folder\TRGEfile.oni
+ onisplit -extract:xml output_folder input_folder\TRGEfile.oni
-:    onisplit -create output_folder input_folder\cutfile.xml
-Version advice:
-: OniSplit v0.9.61.0 can extract M3GM only as OBJ.
-: OniSplit [http://mods.oni2.net/node/38 v0.9.41.0] can extract M3GM as OBJ or DAE.
-Convert the M3GMfile.oni to OBJ:
-: onisplit -extract:obj output_folder input_folder\M3GMfile.oni
 ===Import===
-You can replace the M3GM content with data from another M3GM.
+You will need to replace the M3GM content with data from another M3GM after running:
+ onisplit -create output_folder -tex:texture_file input.dae
-You can create M3GM meshes from OBJ files.
+("-tex" is optional; the TXMP file must created separately if needed.)
-: onisplit -create:m3gm output_folder -tex:texture_file input_folder/weapon.obj
-:: -tex is optional
-:: The TXMP file must created separately (if needed).
-Then you can convert the file to XML and replace the TRGE's old M3GM XML code. Remember to change the links (#N) and instance IDs of the new data.
+Then you can replace the TRGE's old M3GM data with the new M3GM's data. Remember to change the links (#N) and instance IDs of the new data.
 {{XML}}