<li><aclass="backlink"title="Click to do a full-text search for this title"href="./LevelEditor_Clipping?action=fullsearch&value=linkto%3A%22LevelEditor+Clipping%22&context=180">LevelEditor Clipping</a></li>
<spanclass="anchor"id="line-2"></span><spanclass="anchor"id="line-3"></span><pclass="line874">Not to be confused with the CSG clip operation you can perform on brushes, clipping your level will help optimize player collision and help avoid stuck spots, both for players and AI. <spanclass="anchor"id="line-4"></span><spanclass="anchor"id="line-5"></span>
<imgclass="attachment"src="airdefense1_editor_clipped.jpg"title="attachment:airdefense1_editor_clipped.jpg"/><spanclass="anchor"id="line-6"></span><spanclass="anchor"id="line-7"></span><pclass="line874">You can see in this comparison shot how drastically the collision landscape of your level might become after a clipping pass. We'll get into specifics on this later, but first, an overview of the clip texture types available to you: <spanclass="anchor"id="line-8"></span><spanclass="anchor"id="line-9"></span><pclass="line867">
<spanclass="anchor"id="line-10"></span><spanclass="anchor"id="line-11"></span><pclass="line874">Quake 4 makes use of a host of varying clip textures, including a couple additions over the Doom 3 set. These textures can all be found in textures/common/ and are listed by material name. Keep in mind that these textures are defined in materials just as with any others, so you can mix and match these keys in your own materials: <spanclass="anchor"id="line-12"></span><spanclass="anchor"id="line-13"></span><pclass="line867"><strong>clip:</strong> Generates collision for players and monsters. Generates AAS information. <spanclass="anchor"id="line-14"></span><spanclass="anchor"id="line-15"></span><pclass="line867"><strong>full_clip:</strong> Generates collision for all players and monsters, and blocks all weapons fire. Generates AAS information and tactical features. Blocks monster line of sight. <spanclass="anchor"id="line-16"></span><spanclass="anchor"id="line-17"></span><pclass="line867"><strong>player_clip:</strong> Generates collision for players only. <spanclass="anchor"id="line-18"></span><spanclass="anchor"id="line-19"></span><pclass="line867"><strong>monster_clip:</strong> Generates collision for monsters. Generates AAS information. <spanclass="anchor"id="line-20"></span><spanclass="anchor"id="line-21"></span><pclass="line867"><strong>monster_full_clip:</strong> Generates collision for monsters. Generates AAS information and tactical features. Blocks monster line of sight. <spanclass="anchor"id="line-22"></span><spanclass="anchor"id="line-23"></span><pclass="line867"><strong>moveable_clip:</strong> Generates collision for physics objects and ragdolls. <spanclass="anchor"id="line-24"></span><spanclass="anchor"id="line-25"></span><pclass="line867"><strong>shot_clip:</strong> Blocks all weapons fire. <spanclass="anchor"id="line-26"></span><spanclass="anchor"id="line-27"></span><pclass="line867"><strong>largeshot_clip:</strong> Blocks only weapons fire specified with "clipmask_largeshot" "1" set on the projectile/hitscan entityDef (see rocket launcher, grenade launcher, etc). <spanclass="anchor"id="line-28"></span><spanclass="anchor"id="line-29"></span><pclass="line867"><strong>trigshotclip:</strong> Only used on teleporters to allow weapons fire to teleport in multiplayer. <spanclass="anchor"id="line-30"></span><spanclass="anchor"id="line-31"></span><pclass="line867"><strong>vehicle_clip:</strong> Generates collision for vehicles. <spanclass="anchor"id="line-32"></span><spanclass="anchor"id="line-33"></span><pclass="line867"><strong>fly_clip:</strong> Remnant clip type from previous version of Strogg Hornet AI. No longer used in favor of standard monster_clip variants. <spanclass="anchor"id="line-34"></span><spanclass="anchor"id="line-35"></span><pclass="line867">
<spanclass="anchor"id="line-36"></span><spanclass="anchor"id="line-37"></span><pclass="line874">In addition to standard clip textures, a pair of AAS-specific textures can be found in textures/editor/: <spanclass="anchor"id="line-38"></span><spanclass="anchor"id="line-39"></span><pclass="line867"><strong>aassolid:</strong> Generates no collision (despite 'solid' in the name) <spanclass="anchor"id="line-40"></span><spanclass="anchor"id="line-41"></span><pclass="line867"><strong>aasobstacle:</strong> Used on <aclass="nonexistent"href="./Entity_FuncAASObstacle.html">func_aas_obstacle</a> entities. <spanclass="anchor"id="line-42"></span><spanclass="anchor"id="line-43"></span><pclass="line867">
<spanclass="anchor"id="line-44"></span><spanclass="anchor"id="line-45"></span><pclass="line874">An important phase of every single player level is a clipping pass for AAS generation. While AAS data is generated for the level on every standard compile, a careful pass will prevent navigation issues and help the AI take full advantage of your level's layout. <spanclass="anchor"id="line-46"></span><spanclass="anchor"id="line-47"></span><pclass="line874">Notes on AAS Generation: <spanclass="anchor"id="line-48"></span><spanclass="anchor"id="line-49"></span><ul><li>AAS only generates on the tops of brushes. <spanclass="anchor"id="line-50"></span><spanclass="anchor"id="line-51"></span></li><liclass="gap"><pclass="line862">AAS floods from all monsters placed in the world as well as the spawn points on <ahref="./Entity_FuncSpawner.html">func_spawners</a>. AAS flooding will spread across parallel surfaces, up ramps, and over small steps. In almost all cases, this covers all areas where AI of a given AAS size will be navigating. <spanclass="anchor"id="line-52"></span><spanclass="anchor"id="line-53"></span></li><liclass="gap"><pclass="line862">If AAS for some reason fails to flood in a zone, an <aclass="nonexistent"href="./Entity_AASFlood.html">aas_flood</a> entity exists for each AAS size. Place one of these in the non-flooded area to force AAS data of that size to flood. <spanclass="anchor"id="line-54"></span><spanclass="anchor"id="line-55"></span></li><liclass="gap">AAS flooding generates tactical features around solid geometry, monster_full_clip, and full_clip that can be used as cover points by tactical AI - the Strogg tactical transfers and the friendly marines. Cover points can either be full height or half height (half height is between 24-64 units and works best with the animations in the 40-48 unit range , full height cover is 64 units or taller). Cover points are best generated against right angles, so try to keep your monster_full_clip brushes as squared off as possible, and use additional monster_full_clip brushes to square off other appropriate cover points. <spanclass="anchor"id="line-56"></span><spanclass="anchor"id="line-57"></span></li><liclass="gap">Models and patch meshes do not generate AAS and require clipping if AI will be navigating on or near them. <spanclass="anchor"id="line-58"></span><spanclass="anchor"id="line-59"></span></li><liclass="gap">Terrain, as it is done as a model, poses some problems for AAS generation. Typically you will need to generate AAS under the terrain - AI will path over the terrain surface using the data generated below. For large elevation changes, you may need to create ramps of monsterclip under the terrain to link AAS areas. <spanclass="anchor"id="line-60"></span><spanclass="anchor"id="line-61"></span></li></ul><pclass="line874">Some additional notes on clipping you may find useful: <spanclass="anchor"id="line-62"></span><spanclass="anchor"id="line-63"></span><ul><li>If a player can stand on top of something, make sure that object's monsterclipping only goes as high as the player can go, and not to the ceiling - melee units will otherwise have trouble continuing their attacks, and any enemy will lose the player entirely if he becomes hidden in a monster_full_clip brush. <spanclass="anchor"id="line-64"></span><spanclass="anchor"id="line-65"></span></li><liclass="gap">To generate cover points around complex shapes, start with a squared-off monster_full_clip, then layer a more precise monster_clip brush over it. Cover points will generate based off the monster_full_clip locations, but AAS will be generated around the monster_clip brush. (Take care that monsters can still fire their weapons accurately from the cover points.) <spanclass="anchor"id="line-66"></span><spanclass="anchor"id="line-67"></span></li><liclass="gap"><pclass="line862">When creating elevators, place an AASSolid brush (with an <aclass="nonexistent"href="./Entity_AASFlood.html">aas_flood</a> entity, if needed) and a <aclass="nonexistent"href="./Enti
<spanclass="anchor"id="line-73"></span></li><liclass="gap">Patch meshes will not generate AAS, but will generate collision on the 'visible' face. You can use clip textures on patch meshes to create one-way barriers, though it's best avoided for non-flying monsters. Patch mesh clips were used in a couple instances to allow Strogg Hornets to enter, but not leave, confined areas in the Construction Zone (game/walker.map) level. <spanclass="anchor"id="line-74"></span><spanclass="anchor"id="line-75"></span></li></ul><pclass="line867">
<spanclass="anchor"id="line-76"></span><spanclass="anchor"id="line-77"></span><pclass="line874">Clipping in multiplayer is generally a much less involved task. Most important is player mobility - players should not get stuck on anything they're not intended to. A good rule is if something isn't large enough to hide behind, you should clip it off. A common practice in clipping multiplayer levels is to place angled clip brushes on small protrusions from walls to allow players to bounce off with no loss in speed: <spanclass="anchor"id="line-78"></span><spanclass="anchor"id="line-79"></span>
<pclass="line867"><imgclass="attachment"src="mp_angleclip.jpg"title="attachment:mp_angleclip.jpg"/><spanclass="anchor"id="line-80"></span><spanclass="anchor"id="line-81"></span><pclass="line874">Stairs are known to interrupt strafe jumping, which we remedied by ramp-clipping stairways in the stock maps. This prevents hitches in movement in addition to opening more ramp-jumping opportunities, which of course we all love. <spanclass="anchor"id="line-82"></span><spanclass="anchor"id="line-83"></span><pclass="line874">Since AAS is not an issue, you can in some cases get away with clipping that would fail in a single player environment - one-way or curved patch mesh clipping, for example. <spanclass="anchor"id="line-84"></span><spanclass="anchor"id="line-85"></span><pclass="line874">Community-made multiplayer bots may make use of AAS hulls for bot navigation. Consult individual bot documentation files for information on preferred clipping methods - they may differ slightly from what is described here. <spanclass="anchor"id="line-86"></span><spanclass="anchor"id="line-87"></span><pclass="line867"><hr/><pclass="line874"><spanclass="anchor"id="line-88"></span>Back to <ahref="./LevelEditor.html">LevelEditor</a><spanclass="anchor"id="line-89"></span><spanclass="anchor"id="bottom"></span></div><pid="pageinfo"class="info"lang="en"dir="ltr">LevelEditor Clipping (last edited 2005-12-12 23:06:56 by <spantitle="AndrewWeldon @ 24-240-36-51.dhcp.mdsn.wi.charter.com[24.240.36.51]"><aclass="nonexistent"href="./AndrewWeldon.html"title="AndrewWeldon @ 24-240-36-51.dhcp.mdsn.wi.charter.com[24.240.36.51]">AndrewWeldon</a></span>)</p>
<li><ahref="http://moinmoin.wikiwikiweb.de/">MoinMoin Powered</a></li><li><ahref="http://www.python.org/">Python Powered</a></li><li><ahref="http://validator.w3.org/check?uri=referer">Valid HTML 4.01</a></li>