git-svn-id: svn://svn.code.sf.net/p/actiongame/code/trunk/ac@3356 e016b1c5-ed68-44aa-a2f7-31cac88cffde
This commit is contained in:
RandumKiwi
2008-10-31 17:38:06 +00:00
parent cc38bf3164
commit 639c9c99fc
+83 -54
View File
@@ -16,77 +16,106 @@
</div>
<div id="content">
<h1>Map editing: Tips, tricks and advice</h1>
<h2>Size does matter!</h2>
<p>Tips, tricks and advice:</p>
<ul>
<li>
<a href="#size">Size matters!</a>
<li>
<a href="#co-op">Co-operative map editing</a>
</li>
</ul>
<h2 id="size">Size Matters!</h2>
<p>
Don't make fanatically huge maps. Size DOES matter in AssaultCube, as huge maps will lag players down -
not to mention, it will take forever for players to find/frag each other, in what is supposed to be a fast paced game.
Due to the restrictions of the cube engine, it is generally a bad idea to try to rebuild your favourite map A from
your favourite game B - most engines allow for larger rooms and longer lines of sight than Cube does.
Size DOES matter in AssaultCube! Don't make fanatically huge maps as they will lag players down.
Not to mention, it will take forever for players to find/frag each other, in what's supposed to be a fast paced game.
Due to the restrictions of the cube engine, it is generally a BAD idea to try and rebuild your favourite map from
a different game, as most engines allow for larger rooms and bigger lines-of-sight than the Cube engine does!
</p>
<p>
<b>WQD (world quads)</b><br clear="none"/>
<h3>World Quads (WQD)</h3>
The WQD count can be found by typing <b>/hidestats 0</b>. Some figures will appear at the right of
your screen, one of them will be <i>WQD</i>.
your screen, one of them will be <i>WQD</i>...
</p>
<p>
WQD is a good way to measure how good your map will/won't lag. Your map should ideally
WQD is a good way to measure how good your map will or won't lag. Maps should ideally
average a maximum of 5000 WQD (less is better). It's okay for your map to exceed this if it's only a
little bit more in a short area. Keep in mind that lights and details will raise the wqd counts, so a rough layout
won�t really represent the final wqd values of a scene. In an empty map(layout) wich has only corridors and basic
geometry, wqd should never be above 1000. This leaves enough headroom for details, lightning and mapmodels.
The key to a good wqd value are occluders or "solids" (f-key)- these block the view, and the engine can stop rendering
whatever is behind those. To undersand the concept, do the following: Load any of the official maps, enter edit-mode
and fly above the map. You will see occlusion at work. You can toggle it on and off using the f5 key. This
should give you a good idea about how occlusion works and where to place solid cubes while you lay out your map.
Keep in mind, the better your map runs, the more people will want to play it. If your map looks awesome, but
can only be run on a very recent computer, people won�t play it. Many people play AC with very old computers!
</p>
little bit more in a short area. Keep in mind that lights and details will raise the WQD counts, so a rough layout
won't really represent the final WQD values of a map. In an empty map (layout is the only completed part)
which only has corridors and basic geometry, WQD shouldn't be above 1000. This leaves enough overhang for details, lightning and mapmodels.
</p>
<p>
The key to getting a good WQD count is by using occluders or "solids" (press <b>F</b>). These are full-sized walls
that block the view, and it allows the engine to know that it can stop rendering whatever is behind it.<br clear="none"/>
To undersand the concept of occluding, do the following:
</p>
<ol>
<li>
Load one of the official AssaultCube maps.
</li>
<li>
Enter edit-mode (Press <b>E</b>).
</li>
<li>
Fly above the map (beyond the skymap).
</li>
<li>
You will now see occlusion at work. The blacked out parts of the map are where solids exist,
and the engine has decided not to render past them. Parts you can see have, of course, not been occluded.
</li>
</ol>
<p>
You can toggle occlusion on and off by using the <b>F5</b> key (<b>Warning: This may be very laggy!</b>).
Viewing occlusion at work will give you an idea on where to place solid cubes while creating the layout for your map.
</p>
Keep in mind, the better your map runs, the more people will want to play it. If your map looks awesome, but
can only be run on a decent, new computer, then people won't play it as their computer simply won't be able to
handle it. Many AssaultCube players are still using quite old hardware!
</p>
<h2>Layout and design</h2>
<p>
When creating a map, make sure not to make areas far too small. Six or more cubes wide is a good dimension for
doorways, to allow people to pass through them easily. Once again, take reality as your guide. If you�re unsure
about how large your door/window/stairs should be, look at those in your house or outside somewhere.
If players block a doorway for teammates, just because the doorway is only 4 cubes wide, people won�t like
the map very much.
When you build your map, use more that one level. Flat maps are boring. By adding vertical variety, you also
make the gameplay more intresting. Even small alterations in floor height usually make things more diverse.
Second floors
Due to the design of the cube engine, it�s not possible to build a second floor. You can use architectural models
to create them, but don�t try to build a 5-storey building with them. If will be impossible to make it look
right, since mapmodels are lit with one value throughout, simply the light vvalue of the cube that it sits on.
This means it will be very hard to light it up evenly, while having intresting lightning in the rest of the room.
<p>
When creating a map, make sure not to make areas far too small. Six or more cubes wide is a good dimension for
doorways, to allow people to pass through them easily. Take reality as your guide. If you're unsure
about how large your door/window/stairs should be, look at those in your house or outside somewhere.
If players block a doorway for teammates, just because the doorway is only 4 cubes wide, people won't like
the map very much.
</p>
<p>
When you build your map, use more than one level. Flat maps are boring. By adding vertical variety, you also
make the gameplay more intresting. Even small alterations in floor height usually makes things more diverse.
</p>
<p>
Be sure that players aren't <i>"fighting the map"</i> too much. They should be fighting each other after all.
Also make sure that players aren't constantly bumping
their heads, especially against the skymap, as it can be annoying, and unrealistic.
</p>
<p>
Try to keep wall sizes about 3-4 cubes thick, to allow for detail and realism.
</p>
<h3>Second floors</h3>
Due to the limitations of the Cube engine, it's simply not possible to build a second floor out of geometry.
You can however use architectural <a href="mapediting3.html#models">mapmodels</a>
to create them... but don't try to build a 5-storey building with them, otherwise it will be impossible to make it look
right, especially with lighting, since lights in the Cube engine are circular (not spherical), meaning you can't change
the lighting on each level of the platform.
By creative use of levels, you can make maps that very well give the impression of multiple floors!
If you use the bridge model, use it with care!
</p>
<p>
Make sure players aren't "fighting the map" too much. They should be fighting each other after all.
Be sure to make sure that people aren't constantly bumping
their heads, especially against the skybox, as it can be annoying, and unrealistic.
</p>
<p>
Try to keep wall sizes about 3-4 cubes thick, to allow for detail and realism.
</p>
If you use the bridge mapmodels, use it with care!
<h2>Textures</h2>
<p>
Take your time in chosing them. Also, don�t just look at "how it looks", consider reality to be your guide.
Don�t put a floor texture on the ceiling, or wall textures on the floor. Although there are exeptions, try to use
Some common sense. Your nice wooden structure will probably not support a concrete roof too well, or your factory
will probably not have a wooden flooring. Brickwalls on the ground are very uncommon ... etc, etc.
At the end of the texture list is a black/white cross sort-of texture. <b>DON'T</b> use it, it's not a texture,
Take your time in chosing textures. Don't just decide by "how it looks", consider reality to be your guide.<br clear="none"/>
Don't put a floor texture on the ceiling, or wall textures on the floor (although there are exeptions). Try to use
some common sense. A nice wooden structure will probably not support a concrete roof too well, or your factory
will probably not have a wooden flooring. Brickwalls on the ground are very uncommon... etc, etc.
<p>
At the end of the texture list is a texture imprinted with the words "missing content". <b>DON'T</b> use it, it's not a texture,
in-fact, it's lack of a texture. It looks ugly and shouldn't be used in any map, because it's actually there to show if
textures and skins did not load properly.
</p>
<h2>Mapmodels</h2>
<p>
Though they can add some nice and neccesary detail to your map, don�t rely on them! It is advised to add
Though they can add some nice and neccesary detail to your map, don't heavily rely on them! It is advised to add
mapmodels at a late stage in mapping. Think of them more like the icing on the cake.
A boring room won�t look better if you add lots of mapmodels.
When you add them, less is often more. If every square meter has a cigarette and a leaflet on the ground, the
A boring room won't look better if you add lots of mapmodels.
When you add them, less is often more. If every square metre has a cigarette and a leaflet on the ground, the
effect will be lost.
</p>
<h2 id="co-op">Co-operative map editing</h2>