XML:ONLV: Difference between revisions

=====Debugging (OniSplit v0.9.93.0+)=====

=====... used for exceptions=====

The flags Transparent, TwoSided and NoOcclusion are only set if the same texture source is used for diffuse and transparency and if transparency setting are enabled. See the subsection under "[[#... used for exceptions|... used for exceptions]]" called "TwoSided and transparent objects".

The AKEV core geometry is more or less unique while this furniture file adds standard objects (e.g. crates and desks) to it.

!width=120px| content type

! description

| File path to an [[XML:OFGA|OFGA]] (*.oni) file. Make sure that the OFGA comes also with the files it needs: M3GM and TXMP.

OFGA can hold multiple M3GM. That 3d content will be integrate into the AKEV.

| This name gets written into <Tag> inside ONLV (ENVP section) and can be used with BSL commands.

 

E.g. you can take control over a particle via "particle BSL_name start". For more commands see [[XML:BINA/OBJC/PART#BSL_support|HERE]].

Caution with new OFGA files. The particle name will be composed of 2 parts and always includes an "_" underscore. '''Examples:'''

 

 

This file is for objects with "physics". Unlike AKEV core geometry or furniture, those objects can be animated.

: Little video tutorial: how to create [https://www.youtube.com/watch?v=CFNseg_2UxA a simple animated object]

!width=120px| content type

! description

| Use an unique name for each object.

| Tested with BSL command ...

:obj_create Id [Id]

:obj_kill Id [Id]

:env_anim Id [Id]

:env_setanim Id [Id]

The script Id will be stored in ONLV's OBOA instance.

| Optional tag of Object.

:Newton (used with <Flags> FaceCollision to [https://www.youtube.com/watch?v=YICB7qugrtc make object pushable])

| Optional tag of Animation. Frame number. Used to define the end of an OBAN from an *.dae file.

| Optional tag of Animation. Frame number. Used to define the start of an OBAN from an *.dae file.

For documentation purpose the file here has been trimmed down.

 

 

In this example OniSplit takes the "export.dae" file, looks what parts it contains and creates geometry files from it.

* M3GMmotocycle.oni

It's a nice feature that hierarchies are supported here.

The reason for the interruption at frame 880 is probably to give barabas a few more frames of glory in the cutscene.

 

The bio lab script file use the motorcycle objects and animations like this:

  env_show 9 0 # hide static motorcycle parts (because they get visible at level start)

  # in the original game the motorcycle is separated in object 8, 9 and 10

  # static and animated objects are totally independent from each other

  # they are stored in different arrays so their script ids can be the same or different

  obj_create 8 10 # create animation-ready motorcycle parts

  # the first animations would loop because of "AutoStart"

  # so get the right timing to apply the other animations

  # "motorcycle02_stop00" and the others will not loop because they don't have "AutoStart"

  env_setanim 8 motorcycle02_stop00 # motorcycle

  env_setanim 9 motorcycle02_stop01 # hubs

  env_setanim 10 motorcycle02_stop02 # hubs_rear

  obj_kill 8 10 # delete animated parts

  env_show 9 1 # show static motorcycle parts

CRSA can now be imported from an xml file if registered in the master file. See [[#CRSA|HERE]]. (Two formats available.)

For indirect import, see [http://oni.bungie.org/forum/viewtopic.php?id=2657 HERE] (OniTools v7.1.5+) how to get corpse data.

 

Older onisplit versions (like 0.9.86.0) may generate ONLV files that are not re-packable with newer versions.

With Neo's matrix to euler code the rotations can be recovered from CRSA. But due to the character's hierarchy things get messy again (<nowiki>https://dl.dropboxusercontent.com/u/139715/OniGalore/CRSA_to_Mod_Tool_wip.png</nowiki>, dead link). (Wip code (<nowiki>https://dl.dropboxusercontent.com/u/139715/temp/CRSA_to_Mod_Tool.txt</nowiki>, dead link))

After the oni files have been exported, the extraction of objects can fail if their textures can't be found. Those objects probably use textures stored in level 0.

In that case use the "-search" argument to make correct extractions. In total the commands will look like this:

Reimporting dae files (except for env_markers) will merge them with env (AKEV core geometry).

This is also known as scene export. All content exported by the scene file will be combined and saved in one single dae.

For the following example the scene.xml must be present in a folder containing all files used by the scene. In this case it's level3_Final (biolab).

When you load the dae in [[Mod_Tool|XSI]] you'll find the motorcycle and the lab level intro camera. If you select the camera (for better visibility) and press play you'll get to see the motorcycle into animation like you see it in game.

For real-time playback click on "Playback" option button and then "Real-Time Playback".

* Each node represents '''either one 3D object or one camera''' whereby the node name determines the object name inside the dae.

** 3D objects can be organized in a '''hierarchy''' that gets created by the help of '''sub-nodes'''. Each sub-node can also have animations.

<s>According to Neo that feature is still under development.</s> RIP.

 

Following files can be reused at <Objects> without any drawback:

 

For method b) you could use [http://mods.oni2.net/system/files/extract_ENVP.txt THIS] script.

 

The advantage is that you don't need to edit the new ONLV afterwards.

 

 

You can chose between those two methods for consoles, triggers, turrets and furniture without particle.

Doors and furniture with particle need always the xml method.

Don't want to make a scene.xml and physics.xml file? All animated physics can be restored if you aren't afraid of post-editing ONLV.

# Look into the original level folder and copy OBAN and M3GM files to your project's output folder.

# Create your level. Then convert the new ONLV to xml. Now you are able to compare the new and old ONLV file.

# Each OBOA has a <Geometry> tag which links to an M3GA instance by Id. So, collect also all M3GAs that are used by your OBOAs.

# Add these collected OBOAs and M3GAs to you new ONLV. Make sure that your M3GA Ids aren't already taken, change them if necessary.

# Save ONLV and convert to oni. Make package or plugin, and test your reimported level.

 

level 19 reimport (<nowiki>https://dl.dropboxusercontent.com/u/139715/OniGalore/Level_19_reimport.zip</nowiki>, daed link)

 

For example, it imports animated objects from *.dae files which result in a few bugs: Konoko's motocycle is too low, at another point it is completely missing, and the van at the end of the level has some strange unnecessary gunks.

In this second demo, the ENVP and OBOA/M3GA instances were manually reimported. So, if you have fun to RE stuff, try to make sense of the second demo, too.

* Consoles tend to have an collision issue with the player, keeping him trapped. (Jump backwards to escape.)

** This issue might get solved by using a sole BINACJBOConsole.xml file. Or we try to edit the collision boxes of compound_cons.dae.

 

 

This section is only about xml files. For dae export see [[#Level_reimport|HERE]].

 

The most parts of an Oni level are made of ONLV and AKEV. For AKEV's xml tags see [[XML:AKEV|HERE]].

You would only want to export those two files as xml if you want to check if a texture or an object really made it into the level or not.

!width=120px| content type

! description

| Link to [[XML:AKEV|AKEV]] via '''file''' name (AKEV''name''), don't use file suffix .oni

: The OBOA instance holds doors, animated objects (usually for cut scenes) and pushable object (they are not used the original game).

| Link to [[XML:ONSK|ONSK]] via '''file''' name (ONSK''name''), don't use file suffix .oni

: This is the sky box.

| Link to [[XML:AISA|AISA]] via '''file''' name (AISA''name''), don't use file suffix .oni

: This "AI Setup Array" is an alternative character list. [[XML:BINA/OBJC/CHAR|CHAR]] is more powerful.

: This "Object Array" holds functional objects - doors, furniture, turrets, triggers and consoles - in addition it appears that the engine only searches for door type.

: Those "Environment Particle" contains traditionally only door lock lights and particles used by [[XML:OFGA|OFGA]].

: This is a "Corpse Array". It's used to 'spawn dead characters' like Chung in level 1.