Compiling:Healthy Map - Revision history

JRandomNoob: Extended and streamlined a bit

2013-11-19T08:56:46Z

Extended and streamlined a bit

Rylius at 14:42, 13 September 2011

2011-09-13T14:42:59Z

Rylius at 12:50, 23 August 2011

2011-08-23T12:50:06Z

V3nd3tta at 11:35, 23 August 2011

2011-08-23T11:35:20Z

V3nd3tta at 11:34, 23 August 2011

2011-08-23T11:34:43Z

V3nd3tta at 11:34, 23 August 2011

2011-08-23T11:34:17Z

Pickles at 13:09, 21 August 2011

2011-08-21T13:09:11Z

Majkifajki: First version of article about do's and don't's

2011-08-21T12:48:18Z

First version of article about do's and don't's

Majkifajki: started

2011-08-21T09:54:24Z

started

New page

TO DO

← Older revision		Revision as of 08:56, 19 November 2013
Line 1:		Line 1:
−	{{~~WIP~~}}	+	__NOTOC__
		+
		+	The fact that your map compiles fine and is playable doesn’t mean it’s ''good''. There are several factors which define your map as healthy or unhealthy. An unhealthy map has poor fps, huge .pk3 size and long loading time. Your objective is to create a map as small and lean as possible — great visuals or loads of gimmicks will not ensure a long popular life on their own.
		+
		+	==== Don’t build a big box filled with smaller boxes ====
		+
		+	The first map people build will usually conform to the infamous “box map” stereotype — a map where every area can see most other areas, resulting in most of the map (and the players in it!) being drawn at any moment. Quake 3 engine (and by extension Urban Terror) works best with maps that are built like corridors or series of rooms connected by doorways. Fear not for your artistic vision, because most maps you’ve played indeed do look like this without you being able to realize this; their corridorness is simply well hidden.
		+
		+	For an old-but-good article about building a reasonable-looking yet efficient outdoors map, see [http://www.twisted-strand.com/ut_tutorials/map_tut1/index.html SweetnutZ’s site]. For a more in-depth explanation of how the Q3 vis culling works, see the [http://www.web.archive.org/web/20110205062503/http://www.nibsworld.com/rtcw/tutorial_detail_and_hint_brushes_part1.shtml Nib’s World article] (Wayback copy, original site is dead).
		+
		+	==== Always use unique folder names and shader paths ====
		+
		+	Breaking other people’s maps — and the old versions of your own map(s) — is a very common thing beginners do. While you have no control over others you can still do your best to aovid conflicts by using only folder and map names that are unique to your map (and its current version). I.e., for a map named ut4_example_b1, you would:
		+
		+	*put all your textures in textures/ut4_example_b1
		+	*put all your sounds in sounds/ut4_example_b1
		+	*put all your models in models/ut4_example_b1
		+	*put all your shaders in scripts/ut4_example_b1.shader
		+	*and use only textures/ut4_example_b1 in your shader paths
		+
		+	Doing this is a bit more work-intensive than just igoring possible conflicts, but it pays off. To see what I’m talking about you can download ut4_tohunga_b8 and ut4_tohunga_b9 — the newer version causes flickering “missing texture” on the walls of the older one. (As you can see, even an accomplished mapper like Delirium can make this mistake.)
		+
		+	The same principles also apply to recycled stuff — if you reuse something from another map and change it in any way, rename anything that might cause a conflict!
		+
		+	==== Use as few assets from other maps as possible ====
		+
		+	Many mappers have released a map that looks perfectly fine on their system but is completely unplayable for anyone else who doesn’t have all those other maps that lent their shaders, textures and sounds. (This is also a good argument for having a separate clean install for mapping.) Even if you restrict yourself to only textures found in the default installation, your map can and will break when the game is updated. There are even some maps that rely on some particular textures only found in 4.1, displaying copious amounts of tricolors when played in 4.2. The older the map compared to the game version, the worse it gets.
		+
		+	==== All texture sizes must be power of 2 ====
		+
		+	Power-of-two values are 64, 128, 256, 512, 1024, 2048 — and so forth, but you can’t use anything larger in UrT (in fact even modern games rarely use larger sizes). Textures can of course have differing height and width values (16×128, 1024×512, etc).
		+
		+	The way Quake 3 engine works, non-conforming textures are scaled ''down'' to the nearest power-of-two values. For example, a 1024×1023 texture will end up looking just like a 512×512 texture, except its filesize remains as large as that of a 1024×1024 texture.
		+
		+	FIXME: [http://www.gotdelirium.com/site/articles_9.html Delirium’s demonstration] (dead link, no Wayback copy)
		+
		+	==== Don’t include model files (.ase, .md3, .qc) ====
		+
		+	Models are “baked” into the BSP during compilation so the original files would be useless, only increasing the PK3 size. (You still need to include the textures though.)
		+
		+	==== Remove unused shaders and textures ====
		+
		+	During the development process you will most likely try out many shaders. Some of them will not make it to the final map, yet if they’re included in the .shader file they will still get loaded. The same applies to textures — you can reduce the PK3 size quite a bit by making sure only files that are needed are included.
		+
		+	==== Don’t create shaders for textures that don’t need them ====
		+
		+	textures/infiltration/bunkerwall3
		+	{
		+	{
		+	map $lightmap
		+	}
		+	{
		+	map textures/infiltration/bunkerwall3.jpg
		+	blendFunc filter
		+	}
		+	}
		+
		+	This shader represents completely normal, common, solid wall. Don’t write shaders for them, because texture*lightmap is the standard format. It will save loading time and PK3 space.
		+
		+	==== Don’t leave textured surfaces on invisible brushes sides ====
		+
		+	Players won’t see everything during gameplay, make sure you texture these surfaces with caulk.
		+
		+	This is what player see during game. He sees building, but not complete roof:
		+
		+	[[File:Healthy map 02.jpg]]
		+
		+
		+	In ghost mode you can see, that mapper textured roof top with caulk texture:
		+
		+	[[File:Healthy map 01.jpg]]
		+
		+	Roof top cannot be seen during gameplay, so it does not need to be textured. Keep that rule in your mind, it will increase FPS count on your map.
		+
		+	==== Use areaportals to cull rooms that have all their doors shut ====
		+
		+	Learn how to use areaportals and use them in rooms with doors. It will slightly increase FPS on your map. (This suggestion was much more relevant back in the day when Quake 3 was new and Urban Terror could bring a quite beefy machine to its knees. Nonetheless, it can be useful in certain cases.)
		+

−	<p>The fact that your map compiles fine and it's playable, doesn't mean your map is 'good'. There are several factors which define your map as healthy or unhealthy. An unhealthy map has poor fps, huge .pk3 size and takes longer to load. Your objective is to create a map as small as possible, as fast as possible. In order to do that, make sure you do the right things.
−	~~<br />~~
−	~~<br />~~
−	~~<br />~~
−	~~<br />~~
−	~~<br /><strong>ALL texture sizes must be power of 2 (64,128,256,512,1024 etc).</strong>~~
−	~~</p>~~
−	~~<p>It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game [http://www.gotdelirium.com/site/articles_9.html Delirium's Article]~~
−	~~<br />~~
−	~~<br />~~
−	~~<br /><strong>Don't include .md3 or .qc model files.</strong>~~
−	~~</p>~~
−	~~<p> These files are "baked" into .bsp file during compilation, so they are not needed in pk3. This will reduce pk3 size.~~
−	~~<br />~~
−	~~<br /><strong>Don't create shaders for standard textures:</strong>~~
−	~~<br />~~
−	~~</p>~~
−	~~<pre>textures/infiltration/bunkerwall3~~
−	{
−	{
−	~~map $lightmap~~
−	}
−	{
−	~~map textures/infiltration/bunkerwall3.jpg~~
−	~~blendFunc filter~~
−	}
−	~~}</pre>~~
−	~~<p>~~
−	~~<br />This shader represents completely normal, common, solid wall. Don't write shaders for them, because texture *lightmap is the standard format. It will save loading time and pk3 space.~~
−	~~<br />~~
−	~~<br /><strong>Remove unused shaders from shader file.</strong>~~
−	~~<br />~~
−	~~<br />During developing process you will test many shaders in your shader file. Some of them you will not use in the end. Remove them from shader file.~~
−	~~<br />~~
−	~~<br />~~
−	~~<br /><strong>Remove unused textures from pk3</strong>~~
−	~~<br />~~
−	~~<br />Like above - some textures are dropped in final version. You stop using them for many reasons - make sure you don't put them in final .pk3. It will reduce .pk3 size.~~
−	~~<br />~~
−	~~<br />~~
−	~~<br /><strong>Use areaportals to cull rooms hat have all their doors shut.</strong>~~
−	~~<br />~~
−	~~<br />Learn how to use areaportals and use them in rooms with doors. It will slightly increase FPS on your map.~~
−	~~<br />~~
−	~~<br /><strong>Don't leave textured surfaces on invisible brushes sides.</strong>~~
−	~~<br />~~
−	~~<br />Player won't see everything during gameplay - make sure you texture these surfaces with caulk.~~
−	~~<br />~~
−	~~<br />This is what player see during game. He sees building, but not complete roof:~~
−	~~<br />~~
−	~~<br />[[File:Healthy map 02.jpg]]~~
−	~~<br />~~
−	~~<br />~~
−	~~<br />In ghost mode you can see, that mapper textured roof top with caulk texture:~~
−	~~<br />~~
−	~~<br />[[File:Healthy map 01.jpg]]~~
−	~~<br />~~
−	~~<br />Roof top cannot be seen during gameplay, so it does not need to be textured. Keep that rule in your mind, it will increase FPS count on your map.~~
−	~~<br />~~
−	~~<br />~~
−	~~<br />~~
−	~~<br />~~
−	~~</p>~~

	[[Category:Compiling]]		[[Category:Compiling]]

← Older revision		Revision as of 14:42, 13 September 2011
Line 64:		Line 64:
	<br />		<br />
	</p>		</p>
		+
		+	[[Category:Compiling]]

@@ Line 8: / Line 8: @@
    <br /><strong>ALL texture sizes must be power of 2 (64,128,256,512,1024 etc).</strong>
 </p>
-<p>It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game [[[http://www.gotdelirium.com/site/articles_9.html Delirium's Article]]]
+<p>It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game [http://www.gotdelirium.com/site/articles_9.html Delirium's Article]
    <br />
    <br />

@@ Line 8: / Line 8: @@
    <br /><strong>ALL texture sizes must be power of 2 (64,128,256,512,1024 etc).</strong>
 </p>
-<p>It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game <a href="http://www.gotdelirium.com/site/articles_9.html">Delirium's Article</a>
+<p>It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game [[[http://www.gotdelirium.com/site/articles_9.html Delirium's Article]]]
    <br />
    <br />

@@ Line 8: / Line 8: @@
    <br /><strong>ALL texture sizes must be power of 2 (64,128,256,512,1024 etc).</strong>
 </p>
-<p>It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game [url=http://www.gotdelirium.com/site/articles_9.html]Delirium's Article[/url]
+<p>It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game <a href="http://www.gotdelirium.com/site/articles_9.html">Delirium's Article</a>
    <br />
    <br />

@@ Line 1: / Line 1: @@
 {{WIP}}
-<p>The fact that your map compiles fine and it's playable, doesn't mean your map is 'good'. There is several amount of factors, that define your map as healthy or unhealthy. Unhealthy map has poor fps, huge .pk3 size and loads long. Your objective is to create map as small as possible, as fast as possible. In order to do that, make sure You do the right things.
+<p>The fact that your map compiles fine and it's playable, doesn't mean your map is 'good'. There are several factors which define your map as healthy or unhealthy. An unhealthy map has poor fps, huge .pk3 size and takes longer to load. Your objective is to create a map as small as possible, as fast as possible. In order to do that, make sure you do the right things.
    <br />
    <br />

← Older revision		Revision as of 12:48, 21 August 2011
Line 1:		Line 1:
−	~~TO DO~~	+	{{WIP}}
		+
		+	<p>The fact that your map compiles fine and it's playable, doesn't mean your map is 'good'. There is several amount of factors, that define your map as healthy or unhealthy. Unhealthy map has poor fps, huge .pk3 size and loads long. Your objective is to create map as small as possible, as fast as possible. In order to do that, make sure You do the right things.
		+	<br />
		+	<br />
		+	<br />
		+	<br />
		+	<br /><strong>ALL texture sizes must be power of 2 (64,128,256,512,1024 etc).</strong>
		+	</p>
		+	<p>It will save pk3 space by not wasting texture data. Moreover, it affects your textures quality in game [link]
		+	<br />
		+	<br />
		+	<br /><strong>Don't include .md3 or .qc model files.</strong>
		+	</p>
		+	<p> These files are "baked" into .bsp file during compilation, so they are not needed in pk3. This will reduce pk3 size.
		+	<br />
		+	<br /><strong>Don't create shaders for standard textures:</strong>
		+	<br />
		+	</p>
		+	<pre>textures/infiltration/bunkerwall3
		+	{
		+	{
		+	map $lightmap
		+	}
		+	{
		+	map textures/infiltration/bunkerwall3.jpg
		+	blendFunc filter
		+	}
		+	}</pre>
		+	<p>
		+	<br />This shader represents completely normal, common, solid wall. Don't write shaders for them, because texture *lightmap is the standard format. It will save loading time and pk3 space.
		+	<br />
		+	<br /><strong>Remove unused shaders from shader file.</strong>
		+	<br />
		+	<br />During developing process you will test many shaders in your shader file. Some of them you will not use in the end. Remove them from shader file.
		+	<br />
		+	<br />
		+	<br /><strong>Remove unused textures from pk3</strong>
		+	<br />
		+	<br />Like above - some textures are dropped in final version. You stop using them for many reasons - make sure you don't put them in final .pk3. It will reduce .pk3 size.
		+	<br />
		+	<br />
		+	<br /><strong>Use areaportals to cull rooms hat have all their doors shut.</strong>
		+	<br />
		+	<br />Learn how to use areaportals and use them in rooms with doors. It will slightly increase FPS on your map.
		+	<br />
		+	<br /><strong>Don't leave textured surfaces on invisible brushes sides.</strong>
		+	<br />
		+	<br />Player won't see everything during gameplay - make sure you texture these surfaces with caulk.
		+	<br />
		+	<br />This is what player see during game. He sees building, but not complete roof:
		+	<br />
		+	<br />[[File:Healthy map 02.jpg]]
		+	<br />
		+	<br />
		+	<br />In ghost mode you can see, that mapper textured roof top with caulk texture:
		+	<br />
		+	<br />[[File:Healthy map 01.jpg]]
		+	<br />
		+	<br />Roof top cannot be seen during gameplay, so it does not need to be textured. Keep that rule in your mind, it will increase FPS count on your map.
		+	<br />
		+	<br />
		+	<br />
		+	<br />
		+	</p>