Difference between revisions of "XML:TRGE"

From OniGalore
Jump to navigation Jump to search
m
m (image fix)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:XMLModdingHints}}
+
{{XML_File_Header | type=TRGE | prev=TRBS | next=TRIG | name=Trigger Emitter }}
{| border=0 cellspacing=20 cellpadding=0 align=center
 
| The xml code on this page is compatible with onisplit '''v0.9.61.0'''
 
|}
 
  
'''general information'''
+
===general information===
* TRGE is stored globally (in edition/GameDataFolder/level0_Final)
+
* The xml code on this page is compatible with onisplit '''v0.9.61.0'''
 +
* TRGE is stored globally (in AE/AEInstaller/vanilla/level0_Final.dat)
 
* vanilla Oni has only one file of that type: TRGEtrigger_emitter_0
 
* vanilla Oni has only one file of that type: TRGEtrigger_emitter_0
 
* the game crashs if you try to put a TRGEtrigger_emitter_0 clone into an AE package
 
* the game crashs if you try to put a TRGEtrigger_emitter_0 clone into an AE package
Line 11: Line 9:
  
  
'''file structure'''
+
===file structure===
 
+
{| border=0 cellspacing=20 cellpadding=0 style="float:right"
 +
| [[Image:Changed TRGE mesh.png|150px]]<br>test: replaced mesh<br>(screamer warhead)
 +
|}
 
  TRGE
 
  TRGE
 
   |  
 
   |  
Line 25: Line 25:
 
         +-- TXMP <Texture> (link to external file)
 
         +-- TXMP <Texture> (link to external file)
  
{| border=0 cellspacing=20 cellpadding=0 align=right
 
| testing replaced mesh<br>(screamer warhead)<br>[http://i305.photobucket.com/albums/nn207/unknownfuture/Oni_Galore_Images/XML_modding/changed_TRGE_mesh.png http://i305.photobucket.com/albums/nn207/unknownfuture/Oni_Galore_Images/XML_modding/changed_TRGE_mesh_tn.png]<br>
 
|}
 
 
 
'''XML tags'''
 
  
 +
===XML tags===
 
: '''TRGE'''
 
: '''TRGE'''
 
:: <Position> - x y z position of the emitter in connection to the M3GM
 
:: <Position> - x y z position of the emitter in connection to the M3GM
Line 38: Line 33:
 
:: <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.
+
===embedded M3GM===
:: You can create M3GM meshes from obj files. and then convert it to xml.
+
====export====
:: onisplit v0.9.61.0 refuse to convert a single M3GM, use for that onisplit [http://mods.oni2.net/node/38 v0.9.41.0]
+
 
:: Then you can replace old M3GM xml code with your new one.
+
You would need to cut TRGE instance so that only the M3GM and its connected instances remain and convert it to oni.
:: Remember to change the links (#N) and instance IDs of the new data.
+
:    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.
 +
 
 +
{{XML}}

Latest revision as of 02:13, 27 March 2020

TRGE : Trigger Emitter
XML modding tips
  • See HERE to start learning about XML modding.
  • See HERE if you are searching for information on how to handle object coordinates.
  • See HERE for some typical modding errors and their causes.
XML.png
XML

TRBS << Other file types >> TRIG

switch to OBD page

general information

  • The xml code on this page is compatible with onisplit v0.9.61.0
  • TRGE is stored globally (in AE/AEInstaller/vanilla/level0_Final.dat)
  • vanilla Oni has only one file of that type: TRGEtrigger_emitter_0
  • the game crashs if you try to put a TRGEtrigger_emitter_0 clone into an AE package
  • choose another file name if you want a different TRGE, then create a new TRIG and use your TRGE in the <Emitter> tag, finally modify <Class> tag of BINACJBOTrigger


file structure

Changed TRGE mesh.png
test: replaced mesh
(screamer warhead)
TRGE
  | 
  +-- M3GE
        |
        +-- PNTA <Points>
        +-- VCRA <VertexNormals>
        +-- VCRA <FaceNormals>
        +-- TXCA <TextureCoordinates>
        +-- IDXA <TriangleStrips>
        +-- IDXA <FaceNormalIndices>
        +-- TXMP <Texture> (link to external file)


XML tags

TRGE
<Position> - x y z position of the emitter in connection to the M3GM
<Direction> - x y z value of the normal vector of the emitter
<Geometry> - link to baked in M3GM instance
<GunkFlags> - ?


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.

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 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.