Call of Duty 5: Compile Tools - Revision history

Zeroy: /* Build Fast File */

2008-11-24T16:13:09Z

Build Fast File

← Older revision		Revision as of 16:13, 24 November 2008
Line 55:		Line 55:
	===Build Fast File===		===Build Fast File===

	In order for the level and all of it’s assets to be loaded into the game within a reasonable amount of time a fast file is needed to be made. A fast file is one big file that contains all of the data for the level and all of the assets it uses. Since it is all in one file it can quickly be loaded directly to memory, instead of your hard drive having to search for thousands of files and load them individually which takes much longer.		*In order for the level and all of it’s assets to be loaded into the game within a reasonable amount of time a fast file is needed to be made. A fast file is one big file that contains all of the data for the level and all of the assets it uses. Since it is all in one file it can quickly be loaded directly to memory, instead of your hard drive having to search for thousands of files and load them individually which takes much longer.

	The first time you try to build the fast file for the level it will tell you that no zone files exist and ask you if you would like to make them. You’ll want to say “yes” at this prompt. Doing so will create [root]\ zone_source\[levelname].csv, where root is the game install path.		*The first time you try to build the fast file for the level it will tell you that no zone files exist and ask you if you would like to make them. You’ll want to say “yes” at this prompt. Doing so will create [root]\ zone_source\[levelname].csv, where root is the game install path.

	Within this .csv file is a list of assets the level uses. It will have some default assets in there that all levels use. This csv is looked at by the fast file builder and all the assets it references will be added to the level’s fast file. The fast file ends up containing the level BSP itself, plus all assets listed in [levelname].csv.		*Within this .csv file is a list of assets the level uses. It will have some default assets in there that all levels use. This csv is looked at by the fast file builder and all the assets it references will be added to the level’s fast file. The fast file ends up containing the level BSP itself, plus all assets listed in [levelname].csv.

	The fast file generated will be created at [root]\zone\[language]\[levelname].ff. This is the file you would want to give your friend or post online when you want to share your level since it contains all of the data used by the level. Anytime you change anything in the level, or any assets used in the level you’ll need to recompile the fast file so that those new or changed assets get put into the fast file for the game to read.

			*The fast file generated will be created at [root]\zone\[language]\[levelname].ff. This is the file you would want to give your friend or post online when you want to share your level since it contains all of the data used by the level. Anytime you change anything in the level, or any assets used in the level you’ll need to recompile the fast file so that those new or changed assets get put into the fast file for the game to read.

	===Update Zone File===		===Update Zone File===

Zeroy: /* Light Options */

2008-11-24T16:12:53Z

Light Options

← Older revision		Revision as of 16:12, 24 November 2008
Line 37:		Line 37:

	Once you have all the options you wish to use, check the “Compile BSP” option to start the compile using your specified options. The BSP will be compile first ( if you chose that option ), then the lighting ( if you chose that option ), then the game will be loaded to compile the AI Paths ( if you chose that option and your level is single player ).		Once you have all the options you wish to use, check the “Compile BSP” option to start the compile using your specified options. The BSP will be compile first ( if you chose that option ), then the lighting ( if you chose that option ), then the game will be loaded to compile the AI Paths ( if you chose that option and your level is single player ).

			----

	This process can take anywhere from a few seconds to several hours depending on the complexity of your level and the computer you are compiling on. For a frame of reference, most of the retail levels shipped with the game take about 30 minutes to and hour to compile bsp and lighting on quad core CPUs.		This process can take anywhere from a few seconds to several hours depending on the complexity of your level and the computer you are compiling on. For a frame of reference, most of the retail levels shipped with the game take about 30 minutes to and hour to compile bsp and lighting on quad core CPUs.

Zeroy: /* Compile BSP */

2008-11-24T16:12:36Z

Compile BSP

← Older revision		Revision as of 16:12, 24 November 2008
Line 11:		Line 11:
	Be sure to set up your BSP Options and Light Options before checking the "Compile BSP” option. Most of the time no BSP options will be used but I’ll go over them anyways since occasionally they may need to be used. Some light options are commonly used however.		Be sure to set up your BSP Options and Light Options before checking the "Compile BSP” option. Most of the time no BSP options will be used but I’ll go over them anyways since occasionally they may need to be used. Some light options are commonly used however.

	[[Image:warning.png]] Full light compile is set by default, you may want to use Fast light compile if you're just doing testing.		[[Image:warning.png]] Full light compile is set by default, you may want to use Fast light compile if you're just doing testing.

	====BSP Options====		====BSP Options====
Line 41:		Line 41:

	Part of lighting is the grid file. Entities (models, players, AI) in a map are lit by the lights in the map. In complex maps (as opposed to small test maps) calculating which lights affect which entities takes a lot of work. To prevent the engine from having to do this in real-time, this information can be written into the bsp using a mapname.grid file. If a map doesn’t have a grid, you will experience harsh hitches when entering new areas where entities are now visible. These hitches feel like texture thrashing. Grids are needed for both single player and multiplayer maps. A map must be recompiled after creating or modifying a grid. Select “make new grid” if you have never done a grid for the selected level, or “edit existing grid” to continue working on one that you previously made. The level will be loaded in grid mode. You’ll see lots of little dots throughout the level. You’ll need to walk around the level and touch as many of the dots as possible. This defines the areas a player will be able to go. For most areas however, you can just place a brush with the lightgrid material on it in CoDWaWRadiant and the touching dots will automatically be collected when the level is compiled. Doing a custom grid is really for certain detail areas. Most of the time you can just place brushes in CoDWaWRadiant to do the work for you.		Part of lighting is the grid file. Entities (models, players, AI) in a map are lit by the lights in the map. In complex maps (as opposed to small test maps) calculating which lights affect which entities takes a lot of work. To prevent the engine from having to do this in real-time, this information can be written into the bsp using a mapname.grid file. If a map doesn’t have a grid, you will experience harsh hitches when entering new areas where entities are now visible. These hitches feel like texture thrashing. Grids are needed for both single player and multiplayer maps. A map must be recompiled after creating or modifying a grid. Select “make new grid” if you have never done a grid for the selected level, or “edit existing grid” to continue working on one that you previously made. The level will be loaded in grid mode. You’ll see lots of little dots throughout the level. You’ll need to walk around the level and touch as many of the dots as possible. This defines the areas a player will be able to go. For most areas however, you can just place a brush with the lightgrid material on it in CoDWaWRadiant and the touching dots will automatically be collected when the level is compiled. Doing a custom grid is really for certain detail areas. Most of the time you can just place brushes in CoDWaWRadiant to do the work for you.


	===Compile Reflections===		===Compile Reflections===

Zeroy: /* Compile Tool */

2008-11-24T16:12:23Z

Compile Tool

← Older revision		Revision as of 16:12, 24 November 2008
Line 1:		Line 1:
	==Compile Tool==		==Compile Tool==
	[[Image:compiling_1.png\|right]]		[[Image:compiling_1.png\|right\|250px]]
	The “Level Compiling” tab in the [[Call of Duty 5: Launcher Overview#Launcher\|Launcher]] is where you can keep track of your .map files and compile bsp, lighting, paths, and reflections for those .map files.		The “Level Compiling” tab in the [[Call of Duty 5: Launcher Overview#Launcher\|Launcher]] is where you can keep track of your .map files and compile bsp, lighting, paths, and reflections for those .map files.

Zeroy at 16:11, 24 November 2008

2008-11-24T16:11:56Z

← Older revision		Revision as of 16:11, 24 November 2008
Line 1:		Line 1:
	==Compile Tool==		==Compile Tool==
			[[Image:compiling_1.png\|right]]
	The “Level Compiling” tab in the [[Call of Duty 5: Launcher Overview#Launcher\|Launcher]] is where you can keep track of your .map files and compile bsp, lighting, paths, and reflections for those .map files.		The “Level Compiling” tab in the [[Call of Duty 5: Launcher Overview#Launcher\|Launcher]] is where you can keep track of your .map files and compile bsp, lighting, paths, and reflections for those .map files.

Zeroy at 16:10, 24 November 2008

2008-11-24T16:10:48Z

Show changes

CoDEmanX at 14:06, 20 November 2008

2008-11-20T14:06:19Z

← Older revision		Revision as of 14:06, 20 November 2008
Line 4:		Line 4:

	Always have Compile BSP and Compile Lighting checked unless you want to compile your map without one or the other. BSP is for world geometry, models and entities. Lighting is for sun and level lights.		Always have Compile BSP and Compile Lighting checked unless you want to compile your map without one or the other. BSP is for world geometry, models and entities. Lighting is for sun and level lights.


	==BSP Options==		==BSP Options==
Line 10:		Line 11:

	[[Image:Information.png]] If you do make a geometry change and have "onlyents" toggled on, your map will not compile and the D3DBSP will remain the same.		[[Image:Information.png]] If you do make a geometry change and have "onlyents" toggled on, your map will not compile and the D3DBSP will remain the same.


	==Light Options==		==Light Options==

	*Fast- a quick rendering of your lights.<br>		*Fast - a quick rendering of your lights.<br>
	*Extra- High quality rendering of your lights.<br>		*Extra - High quality rendering of your lights.<br>
	*Model Shadow- Models cast shadows.<br>		*Model Shadow - Models cast shadows.<br>
	*No Model Shadow- Models are ignored when compiling shadows.<br>		*No Model Shadow - Models are ignored when compiling shadows.<br>


	=Compile Process=		=Compile Process=
Line 22:		Line 25:
	Launcher can conveniently compile, build your FastFile, and launch your map in-game with one click. You only need to check the options you want to be executed. The most common options are:		Launcher can conveniently compile, build your FastFile, and launch your map in-game with one click. You only need to check the options you want to be executed. The most common options are:

	*Compile BSP.		*Compile BSP
	*Compile Lights		*Compile Lights
	*Compile Paths (If you have nodes in your map)		*Compile Paths (If you have nodes in your map)
	*Compile Reflections.		*Compile Reflections
	*Build Fast File.		*Build Fast File
	*Run Map After Compile		*Run Map After Compile

Zeroy: /* Overview */

2008-11-20T12:05:42Z

Overview

← Older revision		Revision as of 12:05, 20 November 2008
Line 1:		Line 1:
	=Overview=		=Overview=

	After you create your map it will need compiled to be played in the game. You can view the different options for Launcher in [[Launcher Overview]] page. This tutorial will cover what is suggested for beginners.<br>		After you create your map it will need compiled to be played in the game. You can view the different options for Launcher in [[Call of Duty 5: Launcher Overview\|Launcher Overview]] page. This tutorial will cover what is suggested for beginners.<br>

	Always have Compile BSP and Compile Lighting checked unless you want to compile your map without one or the other. BSP is for world geometry, models and entities. Lighting is for sun and level lights.		Always have Compile BSP and Compile Lighting checked unless you want to compile your map without one or the other. BSP is for world geometry, models and entities. Lighting is for sun and level lights.
Line 8:		Line 8:

	The only useful option in BSP Options for those new to Radiant is “onlyents”. If you only added or edited entities then this will cut down your compile time by ignoring the geometry.<br>		The only useful option in BSP Options for those new to Radiant is “onlyents”. If you only added or edited entities then this will cut down your compile time by ignoring the geometry.<br>
	~~{{Note\|~~ If you do make a geometry change and have "onlyents" toggled on, your map will not compile and the D3DBSP will remain the same.}}
			[[Image:Information.png]] If you do make a geometry change and have "onlyents" toggled on, your map will not compile and the D3DBSP will remain the same.

	==Light Options==		==Light Options==

Zeroy: New page: =Overview= After you create your map it will need compiled to be played in the game. You can view the different options for Launcher in Launcher Overview page. This tutorial will cov...

2008-11-20T12:03:57Z

New page: =Overview= After you create your map it will need compiled to be played in the game. You can view the different options for Launcher in Launcher Overview page. This tutorial will cov...

New page

=Overview=

After you create your map it will need compiled to be played in the game. You can view the different options for Launcher in [[Launcher Overview]] page. This tutorial will cover what is suggested for beginners. 

Always have Compile BSP and Compile Lighting checked unless you want to compile your map without one or the other. BSP is for world geometry, models and entities. Lighting is for sun and level lights.

==BSP Options==

The only useful option in BSP Options for those new to Radiant is “onlyents”. If you only added or edited entities then this will cut down your compile time by ignoring the geometry. 
{{Note| If you do make a geometry change and have "onlyents" toggled on, your map will not compile and the D3DBSP will remain the same.}}

==Light Options==

*Fast- a quick rendering of your lights. 
*Extra- High quality rendering of your lights. 
*Model Shadow- Models cast shadows. 
*No Model Shadow- Models are ignored when compiling shadows. 

=Compile Process=

Launcher can conveniently compile, build your FastFile, and launch your map in-game with one click. You only need to check the options you want to be executed. The most common options are:

*Compile BSP.
*Compile Lights
*Compile Paths (If you have nodes in your map)
*Compile Reflections.
*Build Fast File.
*Run Map After Compile

Sources: [http://wiki.treyarch.com/wiki/Compile_a_map Treyarch's Wiki]
[[Category:Radiant]]
[[Category:Call of Duty 5]]
[[Category:Mapping]]
[[Category:Basic Editing]]