Dmap - Revision history

Datiswous: /* Optimization Options */

2025-11-25T20:32:52Z

Optimization Options

← Older revision		Revision as of 20:32, 25 November 2025
Line 74:		Line 74:

	You can actually dmap your level with leaks using dmap noflood (your map). Obviously this will make it a broken map, but its useful when you're just moving stuff around and want to quickly see how it looks without having to seal everything up.		You can actually dmap your level with leaks using dmap noflood (your map). Obviously this will make it a broken map, but its useful when you're just moving stuff around and want to quickly see how it looks without having to seal everything up.

			<pre>

			dmap noflood map_name.map

			</pre>

Datiswous: /* Even further, advanced mappers can use: */

2025-11-25T20:29:12Z

Even further, advanced mappers can use:

← Older revision		Revision as of 20:29, 25 November 2025
Line 79:		Line 79:


	===Even further, advanced mappers can use:===		=== Even further, advanced mappers can use ===

	* The "noFragment" keyword in materials to '''prevent''' some surfaces from splitting during compile		* The "noFragment" keyword in materials to '''prevent''' some surfaces from splitting during compile

Datiswous: /* Optimization Options */ Added noflood (info from Kingsal)

2025-11-25T20:28:21Z

Optimization Options: Added noflood (info from Kingsal)

← Older revision		Revision as of 20:28, 25 November 2025
Line 37:		Line 37:

	You can improve the way the map compiler optimizes the map through the use of "switches".		You can improve the way the map compiler optimizes the map through the use of "switches".

			=== Shadowopt 2 ===

	The most commonly used switch is "shadowopt 2"		The most commonly used switch is "shadowopt 2"
Line 47:		Line 49:

	</pre>		</pre>

			=== LightCarve ===

	Another more common switch is "lightCarve".		Another more common switch is "lightCarve".
Line 66:		Line 70:
	* By most accounts manually splitting light counts is more beneficial than LightCarve so using this switch can be seen as a "lazy technique".		* By most accounts manually splitting light counts is more beneficial than LightCarve so using this switch can be seen as a "lazy technique".
	* (Though it's arguably still cumbersome because proper LightCarve application usually requires some pre-planning...).		* (Though it's arguably still cumbersome because proper LightCarve application usually requires some pre-planning...).

			=== Noflood ===

			You can actually dmap your level with leaks using dmap noflood (your map). Obviously this will make it a broken map, but its useful when you're just moving stuff around and want to quickly see how it looks without having to seal everything up.

Datiswous: /* Even further, advanced mappers can use: */

2025-11-25T20:20:03Z

Even further, advanced mappers can use:

← Older revision		Revision as of 20:20, 25 November 2025
Line 78:		Line 78:
	These techniques are also referred to as [[Performance:_Essential_Must-Knows#Brush_Carving\|"Brush Carving"]]		These techniques are also referred to as [[Performance:_Essential_Must-Knows#Brush_Carving\|"Brush Carving"]]

	* More details at: https://modwiki.~~xnet~~.fi/Dmap_~~%28console_command%29~~		* More details at: https://modwiki.dhewm3.org/Dmap_(console_command)

	== Troubleshooting ==		== Troubleshooting ==

Stgatilov: 2GB limit during dmapping: use 64-bit build

2018-03-24T07:48:00Z

2GB limit during dmapping: use 64-bit build

← Older revision		Revision as of 07:48, 24 March 2018
Line 84:		Line 84:
	=== Malloc Errors ===		=== Malloc Errors ===

	If you get malloc (memory allocation) errors while dmapping then this might be due to the limitation of the program even if you have plenty of RAM. If you have 3GB RAM or more then you can get Dark Mod (doom3) to access up to 4GB by using a 3rd party patch called NTCore. This is a simple Windows application. You just browse to Doom3.exe and click it and it fixes it and makes a backup just in case. That's it! Here is the link.....		If you get malloc (memory allocation) errors while dmapping then this might be due to the limitation of the program even if you have plenty of RAM.

	[[http://www.ntcore.com/4gb_patch.php NTCore]]		If you have more than 4GB of RAM and 64-bit OS, then you should dmap in 64-bit build of DarkMod (starting from 2.06). Keep in mind that memory consumption in 64-bit build is usually higher than in 32-bit build.

			If you have 3GB RAM or more then you can get 32-bit build of DarkMod to access up to 4GB by using a 3rd party patch called NTCore. This is a simple Windows application. You just browse to TheDarkMod.exe and click it and it fixes it and makes a backup just in case. That's it! Here is the link: [[http://www.ntcore.com/4gb_patch.php NTCore]]


	[[Category:Editing]]		[[Category:Editing]]

Nbohr1more: /* Even further, advanced mappers can use: */

2014-09-29T21:52:53Z

Even further, advanced mappers can use:

← Older revision		Revision as of 21:52, 29 September 2014
Line 78:		Line 78:
	These techniques are also referred to as [[Performance:_Essential_Must-Knows#Brush_Carving\|"Brush Carving"]]		These techniques are also referred to as [[Performance:_Essential_Must-Knows#Brush_Carving\|"Brush Carving"]]

	* More details at: ~~http~~://~~www~~.~~modwiki~~.~~net/wiki~~/Dmap_~~(console_command)~~		* More details at: https://modwiki.xnet.fi/Dmap_%28console_command%29

	== Troubleshooting ==		== Troubleshooting ==

Nbohr1more at 16:23, 9 May 2011

2011-05-09T16:23:20Z

← Older revision		Revision as of 16:23, 9 May 2011
Line 2:		Line 2:

	This article can include anything about dmap. I just started it as a placeholder to list when and when not to....		This article can include anything about dmap. I just started it as a placeholder to list when and when not to....

	~~== Delete Proc, CM, AAS ==~~

	~~When you dmap, in many cases the existing Proc, CM, and AAS files will not be overwritten.~~
	~~It is advisable to delete all the files except the map, script, and custom assets.~~

	Also... do not Dmap while a mission is installed. Uninstall the mission then dmap.		Also... do not Dmap while a mission is installed. Uninstall the mission then dmap.
Line 24:		Line 19:
	* After moving a brush or patch entity		* After moving a brush or patch entity
	* After changing a spawnarg (entity keyvalue), unless it affects the origin or rotation of a model.		* After changing a spawnarg (entity keyvalue), unless it affects the origin or rotation of a model.


			== Delete Proc, CM, AAS ==

			When you dmap, in many cases the existing Proc, CM, and AAS files will not be overwritten.
			It is advisable to delete all the files except the map, script, and custom assets.

	== Optimization Options ==		== Optimization Options ==

Nbohr1more at 16:22, 9 May 2011

2011-05-09T16:22:42Z

← Older revision		Revision as of 16:22, 9 May 2011
Line 2:		Line 2:

	This article can include anything about dmap. I just started it as a placeholder to list when and when not to....		This article can include anything about dmap. I just started it as a placeholder to list when and when not to....

			== Delete Proc, CM, AAS ==

			When you dmap, in many cases the existing Proc, CM, and AAS files will not be overwritten.
			It is advisable to delete all the files except the map, script, and custom assets.

			Also... do not Dmap while a mission is installed. Uninstall the mission then dmap.

	== When do I need to dmap? ==		== When do I need to dmap? ==

Nbohr1more: /* Optimization Options */

2011-04-26T00:29:20Z

Optimization Options

← Older revision		Revision as of 00:29, 26 April 2011
Line 59:		Line 59:
	* (Though it's arguably still cumbersome because proper LightCarve application usually requires some pre-planning...).		* (Though it's arguably still cumbersome because proper LightCarve application usually requires some pre-planning...).

	Even further, advanced mappers can use:
			----


			===Even further, advanced mappers can use:===

	* The "noFragment" keyword in materials to '''prevent''' some surfaces from splitting during compile		* The "noFragment" keyword in materials to '''prevent''' some surfaces from splitting during compile

Nbohr1more: /* Optimization Options */

2011-04-26T00:28:20Z

Optimization Options

← Older revision		Revision as of 00:28, 26 April 2011
Line 56:		Line 56:
	</pre>		</pre>

	By most accounts manually splitting light counts is more beneficial than LightCarve so using this switch can be seen as a "lazy technique" (~~though~~ it's proper application usually requires some pre-planning...).		* By most accounts manually splitting light counts is more beneficial than LightCarve so using this switch can be seen as a "lazy technique".
			* (Though it's arguably still cumbersome because proper LightCarve application usually requires some pre-planning...).

	Even further, advanced mappers can use:		Even further, advanced mappers can use: