Creating Large Areas - Revision history

Nbohr1more: /* Recent Observations */

2024-04-24T16:36:30Z

Recent Observations

← Older revision		Revision as of 16:36, 24 April 2024
Line 103:		Line 103:

	=== Recent Observations ===		=== Recent Observations ===
			See the '''[[Performance_Tweaks\|Performance Tweaks]]''' article for the latest config recommendations

	Note:		Note:
Line 111:		Line 112:
	can help a larger map dmap before resorting to the 4GB patch.		can help a larger map dmap before resorting to the 4GB patch.

	* For 64bit patch details see: [[Dmap#Malloc_Errors\|Malloc Errors]]		* For 64bit patch details see: '''[[Dmap#Malloc_Errors\|Malloc Errors]]'''

	Users who experience these errors may also need to enable texture compression. This has been reported more often in v1.04 and v1.05.		Users who experience these errors may also need to enable texture compression. This has been reported more often in v1.04 and v1.05.

Nbohr1more: /* Recent Observations */

2024-04-24T16:01:02Z

Recent Observations

← Older revision		Revision as of 16:01, 24 April 2024
Line 115:		Line 115:
	Users who experience these errors may also need to enable texture compression. This has been reported more often in v1.04 and v1.05.		Users who experience these errors may also need to enable texture compression. This has been reported more often in v1.04 and v1.05.

	(verify these settings in your DoomConfig.cfg)		(verify these settings in your <s>DoomConfig.cfg</s> Darkmod.cfg)

	<pre>		<pre>

Thebigh: /* "L" Technique */ -typo

2023-06-09T10:03:05Z

"L" Technique: -typo

← Older revision		Revision as of 10:03, 9 June 2023
Line 76:		Line 76:
	= "L" Technique =		= "L" Technique =

	The L Technique is a simple but extremely effective way for cramming a bunch of interiors into a small area. Say you have a street with 6 houses, 3 on either side. If you open every door you will have lag because the Doom3 engine will be rendering some of the insides of those houses. What you must do is create an L shaped entrance with minimum detail to prevent a performance drop. The image below ~~illustraits~~ this point:		The L Technique is a simple but extremely effective way for cramming a bunch of interiors into a small area. Say you have a street with 6 houses, 3 on either side. If you open every door you will have lag because the Doom3 engine will be rendering some of the insides of those houses. What you must do is create an L shaped entrance with minimum detail to prevent a performance drop. The image below illustrates this point:

	[[Image:Large area tutorial ltechnique.jpg]]		[[Image:Large area tutorial ltechnique.jpg]]

Thebigh: typo

2021-10-18T12:26:45Z

typo

← Older revision		Revision as of 12:26, 18 October 2021
Line 38:		Line 38:
	''The lights with the red circles around them are the only lights which cast shadows. The rest are using "noshadows 1" on them. Note: The strange jagged lines in this picture are from using noclip.''		''The lights with the red circles around them are the only lights which cast shadows. The rest are using "noshadows 1" on them. Note: The strange jagged lines in this picture are from using noclip.''

	In the above picture you may also notice that ~~non~~ of the lanterns are casting shadows. This is because on the model itself, the "noshadows 1" parameter is applied. This prevents the object from rendering a shadow. This can help drastically because the mapper can pick and choose which objects cast shadows, and the less shadows, the better the performance. Many times players will not even notice if an object is not casting a shadow, especially if it is on the edge of a light.		In the above picture you may also notice that none of the lanterns are casting shadows. This is because on the model itself, the "noshadows 1" parameter is applied. This prevents the object from rendering a shadow. This can help drastically because the mapper can pick and choose which objects cast shadows, and the less shadows, the better the performance. Many times players will not even notice if an object is not casting a shadow, especially if it is on the edge of a light.

	The above image also shows how no shadow lights can be used to illuminate windows. There will rarely be an exception to using "noshadows 1" on window illumination lights as the shadows will rarely ever be important.		The above image also shows how no shadow lights can be used to illuminate windows. There will rarely be an exception to using "noshadows 1" on window illumination lights as the shadows will rarely ever be important.

Nbohr1more: /* Recent Observations */

2019-02-27T06:17:08Z

Recent Observations

← Older revision		Revision as of 06:17, 27 February 2019
Line 120:		Line 120:

	seta image_usePrecompressedTextures "1"		seta image_usePrecompressedTextures "1"
	seta image_useNormalCompression "2"		seta image_useNormalCompression "1"
	seta image_useAllFormats "1"		seta image_useAllFormats "1"
	seta image_useCompression "1"		seta image_useCompression "1"

Petike: adding category tag

2018-11-21T13:57:49Z

adding category tag

← Older revision		Revision as of 13:57, 21 November 2018
Line 136:		Line 136:
	* [[SEED]]		* [[SEED]]

	~~{{tutorial-editing}}~~		[[Category:Editing]]
			[[Category:Tutorial]]
			[[Category:Mapping Tutorials]]
			[[Category:Visportal]]
	[[Category:Lighting]]		[[Category:Lighting]]
	~~[[Category:Visportal]]~~

Stgatilov: Added image for printMemInfo command.

2018-03-24T12:19:27Z

Added image for printMemInfo command.

← Older revision		Revision as of 12:19, 24 March 2018
Line 95:		Line 95:

	If you have problems with memory consumption, you can see how much memory is taken by each particular asset (images, models or sounds) by running '''printMemInfo''' command in console. The generic results will be printed into console, but text files with detailed data (with file granularity) are put into the directory where your map file is located.		If you have problems with memory consumption, you can see how much memory is taken by each particular asset (images, models or sounds) by running '''printMemInfo''' command in console. The generic results will be printed into console, but text files with detailed data (with file granularity) are put into the directory where your map file is located.

			[[Image:PrintMeminfo.jpeg\|500px]]

	Starting with TDM 2.06, you can run 64-bit executable of TDM, which does not suffer from 2 GB memory limit. But keep in mind that the amount of VRAM in GPUs is still limited.		Starting with TDM 2.06, you can run 64-bit executable of TDM, which does not suffer from 2 GB memory limit. But keep in mind that the amount of VRAM in GPUs is still limited.

Stgatilov: Added a note about printMemInfo, fixed reason of malloc errors.

2018-03-24T08:53:28Z

Added a note about printMemInfo, fixed reason of malloc errors.

← Older revision		Revision as of 08:53, 24 March 2018
Line 85:		Line 85:


	Although the Doom3 engine is extremely flexible, you may come into a particular error if your map exceeds the limit that your computer can handle. As far as I've been able to decipher, this specific error is not related to how "large" your map is on either the X,Y or Z axis, rather it's related to the amount of texture your map has. The Doom3 engine is only limited by current hardware in this aspect. If your map is using too many different textures (textures are used on models as well, do not forget that!) your graphics card may not be able to load all the textures into it's memory ~~resulting in~~ a Malloc failure:		Although the Doom3 engine is extremely flexible, you may come into a particular error if your map exceeds the limit that your computer can handle. As far as I've been able to decipher, this specific error is not related to how "large" your map is on either the X,Y or Z axis, rather it's related to the amount of texture your map has. The Doom3 engine is only limited by current hardware in this aspect. If your map is using too many different textures (textures are used on models as well, do not forget that!) your graphics card may not be able to load all the textures into it's memory. Also, 32-bit build of DarkMod can only use 2 GB of RAM. If the total size of assets used by your map exceeds this limit, then you will get a Malloc failure:

	[[Image:Large area tutorial doom3 map error.png]]		[[Image:Large area tutorial doom3 map error.png]]
Line 94:		Line 94:
	This is an extreme case however. It was running on a 1.87ghz core 2 duo, 3 gigs of ram with a x1950 pro 256 card.		This is an extreme case however. It was running on a 1.87ghz core 2 duo, 3 gigs of ram with a x1950 pro 256 card.

			If you have problems with memory consumption, you can see how much memory is taken by each particular asset (images, models or sounds) by running '''printMemInfo''' command in console. The generic results will be printed into console, but text files with detailed data (with file granularity) are put into the directory where your map file is located.

			Starting with TDM 2.06, you can run 64-bit executable of TDM, which does not suffer from 2 GB memory limit. But keep in mind that the amount of VRAM in GPUs is still limited.

	----		----

Nbohr1more at 22:45, 1 October 2012

2012-10-01T22:45:09Z

← Older revision		Revision as of 22:45, 1 October 2012
Line 133:		Line 133:
	{{tutorial-editing}}		{{tutorial-editing}}
	[[Category:Lighting]]		[[Category:Lighting]]
			[[Category:Visportal]]

Nbohr1more: /* Recent Observations */

2011-04-21T00:14:24Z

Recent Observations

← Older revision		Revision as of 00:14, 21 April 2011
Line 106:		Line 106:
	can help a larger map dmap before resorting to the 4GB patch.		can help a larger map dmap before resorting to the 4GB patch.

	* For 64bit patch details see: [[Dmap#Malloc_Errors]]		* For 64bit patch details see: [[Dmap#Malloc_Errors\|Malloc Errors]]

	Users who experience these errors may also need to enable texture compression. This has been reported more often in v1.04 and v1.05.		Users who experience these errors may also need to enable texture compression. This has been reported more often in v1.04 and v1.05.