OniGalore

XML:ONLV: Difference between revisions

XML Discussion

XML:ONLV (view source)

Revision as of 10:08, 6 June 2012

4,590 bytes added ,  6 June 2012
m
should put the content into tables ... later
m (should put the content into tables ... later)
Line 2: Line 2:




Custom levels that has been created so far:
Custom levels that have been created so far:
* [http://oni.bungie.org/community/forum/viewtopic.php?id=1506 Maze]
* [http://oni.bungie.org/community/forum/viewtopic.php?id=1506 Maze]
* [http://oni.bungie.org/community/forum/viewtopic.php?id=1736 Arena]
* [http://oni.bungie.org/community/forum/viewtopic.php?id=1736 Arena]
Line 23: Line 23:




===xml section===
==xml section==
For praxis information see: "Creating the Lair - A level tutorial" link.
For praxis information see: "Creating the Lair - A level tutorial" link.




ONLV = Oni Level file
===ONLV: Oni Level===


file structure
file structure
Line 56: Line 56:


'''flags in the <OBOAObject> section'''
'''flags in the <OBOAObject> section'''
: <Flags>
 
these are also used for the physics.xml file
: '''<Flags>'''
:: <!-- None -->
:: <!-- None -->
:: InUse
:: InUse
Line 62: Line 64:
:: NoGravity
:: NoGravity
:: FaceCollision
:: FaceCollision
: <PhysicsType>
: '''<PhysicsType>'''
:: <!-- None -->
:: None
:: Static
:: Static
:: Linear
:: Linear
:: Animated
:: Animated
:: Newton
:: Newton




Line 157: Line 160:




'''not empty ENVP - example from level 19''''
'''not empty ENVP - example from level 19'''
             <ENVPParticle>
             <ENVPParticle>
                 <Class>locklight</Class>
                 <Class>locklight</Class>
Line 168: Line 171:
<Transform> - the last 3 values are the position (x, y, z)
<Transform> - the last 3 values are the position (x, y, z)


<Flags>
: <!-- None -->
: NotInitiallyCreated


===spawnable geometry===
In Oni's last level, the platform of the big satellite dish can be spawned/deleted from BSL. Characters on it will fall down when the platform becomes deleted.


I tested that long time ago, I think OBOA used for it (at least in the original data).
====spawnable geometry====
In Oni's last level, the platform of the big satellite dish can be spawned/deleted from BSL. Characters on it will fall down when the platform becomes deleted (tested long time ago).


If OBOA import is not allowed maybe we can add more such things with the physics.xml and then use the <ScriptId> for BSL? What options exist for <Flags> and <Physics> ?
If OBOA import is not allowed maybe we can add more such things with the physics.xml and then use the <ScriptId> for BSL?




Possible applications:
Possible applications:
* grids in front of ventilation shafts
* grids in front of ventilation shafts (a little door object should be a good alternative here)
* ground/ceiling/objects for cutscenes that become partially destroyed
* ground/ceiling/objects for cutscenes that become partially destroyed
* destrucable walls [http://www.youtube.com/watch?v=qgJUbPWX5yE like in Deus Ex 3] (trigger volume, replacing punch anim with punch-through-wall anim)
* destrucable walls [http://www.youtube.com/watch?v=qgJUbPWX5yE like in Deus Ex 3] (trigger volume, replacing punch anim with punch-through-wall anim)
Line 199: Line 204:


[[User:EdT|EdT]] 01:11, 6 June 2012 (CEST)
[[User:EdT|EdT]] 01:11, 6 June 2012 (CEST)
: Okay, i see, another thing to wait for. Will test the physics.xml a bit during weekend. [[User:Paradox-01|paradox-01]] 12:08, 6 June 2012 (CEST)
====breakable glass with BSL recognition====
Not tested.
BSL command:
: env_broken (ID_1, ID_N)
It's used in the training level and determines if glass got shot through or not. How do we set such things up?
====texture exchange====
Not tested.
([[OBD:IDXA_AKEV_2]])
BSL command [[BSL:PC_vs._Mac_Comparison_(table)|supported]] by PC and Mac:
: env_texswap ID texture
Might be useful to switch on/off static and animated textures. (News screen: running or smashed. Lava stream: flowing or stagnating or cooled down. Etc.)
===AKEV: Akira Environment===
Somehow I would like to have the AKEV and ONLV information on one page (like the sound stuff on SNDD). Let's see how this turns out.
'''AGQG flags''' - appears to be used by '''textures.xml <GunkFlags>''' (just some or all of them ?)
<!-- : None -->
: DoorFrame (invisible quad that uses the TXMP_DOOR_FRAME texture)
: Ghost (pathfinding volume separator, see [[OBD:AKVA|AKVA]] etc)
: StairsUp
: StairsDown
: Stairs
: Triangle
: Transparent
: TwoSided
: NoCollision
: Invisible
: NoObjectCollision
: NoCharacterCollision
: NoOcclusion
: Danger
: Horizontal (slope > 70°)
: Vertical (slope < 70°)
: GridIgnore
: NoDecals
: Furniture
: ProjectionBit0
: ProjectionBit1
: SoundTransparent
: Impassable
'''(Copied from hex page. Is this still up to date ?)'''
;Triangles
:Many quads are in fact triangles: the last two vertices have the same [[OBD:PNTA|PNTA]] and [[OBD:TXCA|TXCA]] entries, and the ARGB color is (255, 205, 205, 205) (80% gray, 100% opaque). There is also a flag specifying that.
;Ghost, StairsUp, StairsDown
:These flags are used for BNV adjacencies, see [[AKAA]]. Stairs up/down are used instead of Ghost when the quad is placed at the bottom/top of the stairs. These quads are not visibile. The script variable env_show_ghostgqs is intended to control the visibility of such quads but it requires "debug" level files.
:There are a couple of ghost quads that aren't referenced from [[AKAA]]. It's likely that those quads are useless.
;DoorFrame
:This appears to be another type of "ghost" quad (its visibility is controlled by the same env_show_ghostgqs variable). Sometimes it is used together with the Ghost flag but not always. Only the door frames that also have the Ghost flag are used as adjacencies so it's unclear if the rest of the door frames serve any purpose. In fact it appears that this flag has no effect other than making the quad invisible.
;Stairs
:This is applied to the invisible ramp quad that covers the stairs. In general this flag is also applied to the visible stairs geometry but there are some exceptions (errors? see level 19 stairs).
;NoOcclusion
:This flag tells the octtree raycaster to ignore the quad when doing ray/quad intersections. This is tipically used for small quads that are unlikely to affect the overall environment visibility.
;ProjectionBit
:These 2 flags can be 00, 01, 10 and 11. That means the values 0,1,2 and 3 which have the following meanings:
:*0 - No projection plane specified. One can be computed if needed. Never used in files, may slow down the game if used.
:*1 - Project quad on XY plane.
:*2 - Project quad on XZ plane.
:*3 - Project quad on YZ plane.
:The projection plane is used to determine if a point is in a quad (this point is usually the result of an intersection between a ray and the quad plane).
;GridIgnore
:Appears to be unused. Its likely purpose is to mark quads that don't count as obstacles in the pathfinding grid.
;Danger
:Appears to be unused. Its likely purpose is to create danger areas in the pathfinding grids. Usually there's a trigger volume nearby that hurts/kills the character. This quads are always invisible.
;Invisible
:Invisible quads have a couple of different uses:
:* block player access to some parts of the environment
:* stairs ramp
:* collision geometry (used by some "complex" furniture)
:* danger quads (see above)
:* some other apparently useless quads
;Furniture
:Set for all quads that belong to a furniture object. It doesn't appear to be used. It is also redundant since all the furniture quads have an object id.
;NoDecals
:Prevents the creation of decals on the quad. Set for door quads because the decals would disappear when the door opens. That's why shooting a door doesn't leave a mark.
;Impassable
:Probably used by forcefields and end of level boundaries (like in state archive level).
Paradox-01
8,452

edits

Retrieved from "https://wiki.oni2.net/Special:MobileDiff/19944"