XML:TURR: Difference between revisions

XML:TURR (view source)

Revision as of 12:26, 5 October 2013

678 bytes added , 5 October 2013

I totally forgot onisplit now can also extract other embedded M3GMs, not just ONWCs. That will help creating a TURR depot for Mod Tool. -- Caution: there's garbage in some <ParticleClass> tags.

Paradox-01

8,201

edits

@@ Line 322: / Line 322: @@
 ===embedded M3GM===
-====export====
+====new export method====
+With OniSplit '''v0.9.94.0+''' (and possibly a few older versions) you can extract dae together with xml from the oni.
+:    onisplit -extract:xml output_folder input_folder\TURRfile.oni
+====old export method====
 You would need to cut TURR instance so that only the M3GM and its connected instances remain and convert it to oni.
 :    onisplit -extract:xml output_folder input_folder\TURRfile.oni
@@ Line 336: / Line 340: @@
-====import====
+====new import method====
+There's a bug in OniSplit. Before you can re-convert dae and xml to oni, you must clean some tags in the xml file.
+For example TURRvdg_turret_wall.xml
+ <ParticleCount>4</ParticleCount>
+That means 4 <ParticleClass> are used, the others are not.
+They contain garbage like <ParticleClass>�ޭޭޭޭޭޭޭ�</ParticleClass>. Remove that content, make it: <ParticleClass></ParticleClass>.
+Then you can re-convert.
+====old import method====
 Are there some tags which make together the mesh but you basically need to know that you can replace that content with data from another M3GM.