XML:TRGE: Difference between revisions
Jump to navigation
Jump to search
m (putting nav header parameters in more logical order) |
m (copy-edit) |
||
Line 1: | Line 1: | ||
{{XML_File_Header | prev=TRBS | type=TRGE | next=TRIG | name=Trigger Emitter}} | {{XML_File_Header | prev=TRBS | type=TRGE | next=TRIG | name=Trigger Emitter}} | ||
== | ==General information== | ||
* The | * The XML on this page is compatible with OniSplit '''v0.9.61.0'''. | ||
* TRGE is stored globally | * TRGE is stored globally, in level0_Final.dat. | ||
* | * TRGE files hold the 3D models for laser triggers, however there's only one model used in all of Oni, TRGEtrigger_emitter_0. | ||
* | * The game crashes if you try to put a TRGEtrigger_emitter_0 file into an AE package to override the original. | ||
* | * Choose another file name if you want a different TRGE, create a new [[XML:TRIG|TRIG]] and name your TRGE in the <Emitter> tag, and then name your TRIG in the <Class> tag of the level's [[XML:BINA/OBJC/TRIG|BINACJBOTrigger]]. | ||
==File structure== | |||
== | |||
{| border=0 cellspacing=20 cellpadding=0 style="float:right" | {| border=0 cellspacing=20 cellpadding=0 style="float:right" | ||
| [[Image:Changed TRGE mesh.png|150px]]<br>test: replaced mesh<br>(screamer warhead) | | [[Image:Changed TRGE mesh.png|150px]]<br>test: replaced mesh<br>(screamer warhead) | ||
Line 25: | Line 24: | ||
+-- TXMP <Texture> (link to external file) | +-- TXMP <Texture> (link to external file) | ||
==XML tags== | |||
: '''TRGE''' | : '''TRGE''' | ||
:: <Position> - | :: <Position> - XYZ position of the emitter in connection to the M3GM | ||
:: <Direction> - | :: <Direction> - XYZ value of the normal vector of the emitter | ||
:: <Geometry> - link to | :: <Geometry> - link to M3GM instance | ||
:: <GunkFlags> - | :: <GunkFlags> - unused | ||
==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. | 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 -extract:xml output_folder input_folder\TRGEfile.oni | ||
: onisplit -create output_folder input_folder\cutfile.xml | : 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 | 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 can create M3GM meshes from OBJ files. | |||
You can create M3GM meshes from | |||
: onisplit -create:m3gm output_folder -tex:texture_file input_folder/weapon.obj | : onisplit -create:m3gm output_folder -tex:texture_file input_folder/weapon.obj | ||
:: -tex is optional | :: -tex is optional | ||
:: The TXMP file must created separately (if needed). | :: The TXMP file must created separately (if needed). | ||
Then you can convert the file to | 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. | ||
Remember to change the links (#N) and instance IDs of the new data. | |||
{{XML}} | {{XML}} |
Revision as of 14:35, 30 March 2021
TRGE : Trigger Emitter | ||
---|---|---|
XML
TRBS << Other file types >> TRIG |
General information
- The XML on this page is compatible with OniSplit v0.9.61.0.
- TRGE is stored globally, in level0_Final.dat.
- TRGE files hold the 3D models for laser triggers, however there's only one model used in all of Oni, TRGEtrigger_emitter_0.
- The game crashes if you try to put a TRGEtrigger_emitter_0 file into an AE package to override the original.
- Choose another file name if you want a different TRGE, create a new TRIG and name your TRGE in the <Emitter> tag, and then name your TRIG in the <Class> tag of the level's BINACJBOTrigger.
File structure
test: replaced mesh (screamer warhead) |
TRGE | +-- M3GM | +-- PNTA <Points> +-- VCRA <VertexNormals> +-- VCRA <FaceNormals> +-- TXCA <TextureCoordinates> +-- IDXA <TriangleStrips> +-- IDXA <FaceNormalIndices> +-- TXMP <Texture> (link to external file)
XML tags
- TRGE
- <Position> - XYZ position of the emitter in connection to the M3GM
- <Direction> - XYZ value of the normal vector of the emitter
- <Geometry> - link to M3GM instance
- <GunkFlags> - unused
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 advice:
- 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
You can replace the M3GM 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.