Creating a level: Difference between revisions

==Level releases and resources==

===Fan-made levels===

|-

|2019/09/16

|31

|-

|2016/02/13

|7

|-

|2014/01/19

|17

|-

|2013/09/07

|29

|-

|2013/07/12

|28

|-

|2013/06/01

|25

|-

|2012/05/12

|24

|-

|2012/03/18

|23

|-

|2012/02/12

|22

|-

|2012/01/23

|21

|-

|2012/01/16

|21

|-

|2011/07/25

|5

|-

|2011/10/03

|20

|-

|2011/07/03

|16

|-

|2011/06/23

|15

|-

|-

|2010/11/08

|7

|-

|2010/11/06

|5

|-

|2010/02/15

|5

|-

|[http://mods.oni2.net/node/4 Arena of Pain]

|30

|}

===Forum tutorials on level creation===

===Wiki pages on level creation===

===Free asset sources===

==Engine limitations==

Be sure to uncheck automatic triangle creation when exporting (BNV) geometry used for pathfinding. Ghost (''doors'') must be quads.  

The level import demo files can be downloaded [http://mods.oni2.net/node/299 HERE].

Instead of "-nosep" you can now also use "-pc" for the import. Macs, however, do use "-sep".

If the game crashes while loading at ~90% progress, be sure that the texture's x and y dimensions are powers of two: 64, 128, 256, 512….

  OniSplit.exe -create:txmp out env/markers/*.tga

''The project file for level creation.''  

'''Common mistake:'''

|-

| <Environment>

|valign="top"| <Import>

|valign="top"| link

: [[XML:BINA/OBJC/CHAR|Character.xml]] (has to contain player character if there's no AISA file with it)

: [[XML:BINA/OBJC/CONS|Console.xml]]

: [[XML:BINA/OBJC/WEAP|Weapon.xml]]

: [[XML:BINA/OBJC/MELE|Melee.xml]] (overrides global MELE; not used in vanilla levels)

|-

| <Films>

This tag is mandatory (it must be present to avoid errors); the model section contains one import path to the AKEV (level) geometry (*.dae) and can contain additional import paths for exceptions (*.dae).

-->

'''Mod Tool versus SketchUp'''

-->

Broken environmental objects can be recognized by the BSL command ''env_broken (ID_1, ID_N)''. However, this requires additional code to work.

targets_are_gone() eventually disables the TV to prevent memory overflow; this function also contains all the things ("[...]") that you want to happen after the glass target is broken.

BSL command supported on Windows and Mac:

: env_texswap ID texture

A similar effect can be achieved by showing/hiding geometries with different textures as EdT has demonstrated in a private test. That way it should also be possible to have different vertex coloring for an area.

[http://web.archive.org/web/20170529111607/http://softimage.wiki.softimage.com/xsidocs/tex_vcolor_CreatingColoratVerticesCAVMaps.htm SoftImage documentation.] Observation: The sniper tower from level 19 Syndicate Mountain Compound can be isolated and re-imported as it is. It will appear quite dark.

So, how do we modify that data?

If there's already a vertex color property, you can use Shift + W to activate the Paint Vertex Color Tool. With Control + W you can change the brush color. R + Hold Click + Move Mouse let you change the brush size. The more vertices (points) you have, the more detailed you can make the shadows/colors. But keep in mind that too many polygons can destroy collision, making characters fall through the ground.

If there's no vertex color property, the first usage of Shift + W will create that property. But you can also manually create it via Property > Color under Vertices Map.

[[Image:light_test_modtool.png|right|thumb]]

[[Image:light_test_ingame.png|right|thumb]]

To get general shading/lighting you can set up light sources. "Infinite" lights are useful for global lighting, while "Light Box", "Point", "Neon" and "Spot" are more suitable as local light sources. They can be accessed via Primitives > Light.

* Property > Color At Vertices Map

* Property > Render Map

* "Shaded" let you see the illumination only.

* "Textured" let you see the textured object with illumination and vertex coloring.

If you use '''env_shade''', use it with caution. It completely overwrites the vertex coloring.

  env_shade 7 10 1 1 1 # object 7, 8, 9, 10 lose all their shading

A drawback of this method, AKA shadow maps, is the high number of [[XML:BINA/TMBD|TMBD]] changes and new textures for every wall, requiring a lot of memory. How to create shadow maps:

** Can be used on a new overlying, transparent surface

With this approach there are two meshes, whereby the shadow effects on one mesh get drawn in front of the regular level texture.

[[Image:Oni_Lightmaps_double_polygon_method.jpg|center]]

The Rooms tag is mandatory. It contains an import path to BNV and ghosts (*.dae) which are used to create pathfinding grids. For information on the binary data behind this, see [[OBD:AKVA|HERE]].

:: Striker follows you again

Pathfinding works on slightly uneven ground as long as the polygons are 0.5 world units beneath or 4 world units above the BNV.

: '''Solution:''' Use either '''chr_lock_active ''AI_name''''' or '''chr_all_active = 1'''

'''(OniSplit v0.9.93.0+)'''

[[Image:OniBrowser.jpg|thumb|200px|right|OniBrowser displaying level geometry plus PF and ghosts.]]

AIs appear to have trouble shooting through ghost quads that got registered in the octtree/BSP tree as seen here (<nowiki>https://www.youtube.com/watch?v=-ZugVBgBVKc</nowiki>, dead link).

[[Image:Pathfinding_creation__merge_polygons_to_fix_connections.jpg|thumb|200px|right|Fixed PF in compound level after underground construction...]]

It can help to merge polygons to one object and merge their edges. These become white. (Outer edges are blue.)

The [[#textures_tag|textures tag]] is mandatory.

See '''Figure 1'''.

OniSplit automatically imports textures of objects in the [[#<Model>|<Model> section]]. Those objects could be considered as AKEV core geometry.

Caution: textures will be fixed to one set of flags. You can't use the same texture A for a one-sided cluster/object B and a two-sided cluster/object C. You would need to create a differently-named clone of that texture and apply that to cluster/object C.

Marker textures are used to import certain objects with special flags. Import those objects alongside [[#<Model>|AKEV core]] geometry.

Don't use this.

Information on regular object lists can be looked up here:

: [[XML:BINA/OBJC/CHAR|Character.xml]] (has to contain player character if there's no AISA file with it)

: [[XML:BINA/OBJC/WEAP|Weapon.xml]]

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

|valign="top"| <Class>

|valign="top"| link

An OFGA can hold multiple M3GMs. That 3D content will then be integrated 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]].

: FURN <Particle>test</Particle> + OFGA <Tag>streetlight</Tag> = '''test_streetlight'''

  </Oni>

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

|}

  <?xml version="1.0" encoding="utf-8"?>

  <Oni>

  env_show 9 1 # show static motorcycle model where Konoko parks her bike

An empty Corpse element (<Corpse />) is treated as unused and placed at the end of the array. If no such empty elements are provided, OniSplit automatically adds 5. OniSplit also ensures that there are at least 20 corpses in the array.

|

|}

<!--

[[Image:ONLV_CRSA_XSI_aided_import.jpg|thumb|200px]]