Jump to content

XML:TRGE: Difference between revisions

555 bytes added ,  20 April 2012
m
no edit summary
mNo edit summary
mNo edit summary
Line 38: Line 38:
:: <GunkFlags> - ?
:: <GunkFlags> - ?


:'''M3GM'''
 
:: 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.
===M3GM===
:: You can create M3GM meshes from obj files. OniSplit v0.9.61.0 refuse to create a single M3GM. Instead, use OniSplit [http://mods.oni2.net/node/38 v0.9.41.0]
'''export'''
:: 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.
You would need to cut TRGE instance so that only the M3GM and its connected instances remain and convert it to oni.
:   onisplit -extract:xml output_folder input_folder\TRGEfile.oni
:    onisplit -create output_folder input_folder\cutfile.xml
 
version hint:
: 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'''
 
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.
 
You can create M3GM meshes from obj files.
: 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.
8,046

edits