Jump to content

XML:DOOR: Difference between revisions

10 bytes removed ,  15 February 2014
m
no edit summary
mNo edit summary
mNo edit summary
Line 138: Line 138:
The 3D content can probably also be referenced with absolute file paths but to keep things simple the dae files should be in the same folder.
The 3D content can probably also be referenced with absolute file paths but to keep things simple the dae files should be in the same folder.


Such simple reference (relative path) is seen here in the [[#sample_code|sample code]]. So, it will be just the file name in <Geometry>.
A simple reference (relative path) can be seen in the [[#sample_code|sample code]] at <Geometry>.


Of course TXMP(s) are required for the new 3D content.
Of course TXMP(s) are required for the new 3D content.
Line 144: Line 144:


==door animation export==
==door animation export==
Basically it's:
Actually it would be ...


  onisplit -extract:dae output_path path_to/OBAN''file''.oni -geom:M3GM''file''.oni
  onisplit -extract:dae output_path path_to/OBAN''file''.oni -geom:M3GM''file''.oni
... but since we don't use standalone M3GM for doors anymore, use this instead:
onisplit -create output_path path_to/DOOR*.xml
onisplit -extract:dae output_path path_to/OBAN*.oni




Line 164: Line 168:
  * TXMP file (one for each embedded M3GM instance)
  * TXMP file (one for each embedded M3GM instance)
   
   
  '''in level 0 / level X*'''
  '''in level 0'''
  * DOOR file
  * DOOR file
  * OBAN file  
  * OBAN file
 
[...]


<nowiki>*</nowiki> As long as these two files are in the same folder it doesn't matter if they are stored 'globally' or 'locally' stored. Not tested on Mac.




8,046

edits