UserDoc:Warp3D - Revision history

Karl Churchill: /* Configuration */

2013-01-14T13:07:01Z

Configuration

← Older revision		Revision as of 13:07, 14 January 2013
Line 260:		Line 260:
	:When set to "on", causes Z buffer format to change from 24-bit to 16-bit and disables all support for the stencil buffer (which together with the 24-bit Z buffer is stored as a 32-bit combined buffer). All applications written for Warp3D v4 or earlier have no access to stencil support. Switching to 16-bit reduces Video RAM usage and doubles the effective Z buffer bandwidth, at a slight loss in precision.		:When set to "on", causes Z buffer format to change from 24-bit to 16-bit and disables all support for the stencil buffer (which together with the 24-bit Z buffer is stored as a 32-bit combined buffer). All applications written for Warp3D v4 or earlier have no access to stencil support. Switching to 16-bit reduces Video RAM usage and doubles the effective Z buffer bandwidth, at a slight loss in precision.
	:When set to "off", Z buffer depth is 24-bit. In the absence of any manual value, this is the default setting.		:When set to "off", Z buffer depth is 24-bit. In the absence of any manual value, this is the default setting.
			* MaxPacketSize
			:'''Caution! This feature is experimental.'''
			:Sets a limit on the maximum amount of data that can be sent to the card as a single render command. Lowering this value may improve performance for some titles that make heavy use of large vertex array drawing.
			:The valid range for this value is 1024 - 7800. Values outside this range will be clamped. In the absence of any manual value, 7800 is the default setting.

Karl Churchill: /* Radeon (R100) */

2013-01-14T13:06:44Z

Radeon (R100)

← Older revision		Revision as of 13:06, 14 January 2013
Line 216:		Line 216:
	:When set to "off", Z buffer depth is 24-bit. In the absence of any manual value, this is the default setting.		:When set to "off", Z buffer depth is 24-bit. In the absence of any manual value, this is the default setting.
	* MaxPacketSize		* MaxPacketSize
	:Caution! This feature is experimental.		:'''Caution! This feature is experimental.'''
	:Sets a limit on the maximum amount of data that can be sent to the card as a single render command. Lowering this value may improve performance for some titles that make heavy use of large vertex array drawing.		:Sets a limit on the maximum amount of data that can be sent to the card as a single render command. Lowering this value may improve performance for some titles that make heavy use of large vertex array drawing.
	:The valid range for this value is 1024 - 7800. Values outside this range will be clamped. In the absence of any manual value, 7800 is the default setting.		:The valid range for this value is 1024 - 7800. Values outside this range will be clamped. In the absence of any manual value, 7800 is the default setting.

Karl Churchill: /* Permedia 2 */

2013-01-14T13:05:55Z

Permedia 2

← Older revision		Revision as of 13:05, 14 January 2013
Line 71:		Line 71:
	* If a title allows it, consider using lower detail textures		* If a title allows it, consider using lower detail textures
	* If a title allows it, stick to double buffering or windowed mode.		* If a title allows it, stick to double buffering or windowed mode.
			* If a title does not provide user control over texture detail and makes use of large textures, you may be able to force it to use lower detail versions by setting the LimitTextureSize variable. This requires that the application queries the driver capabilities and respects the maximum texture size that it reports by downsampling textures larger than the limit.

	=== Configuration ===		=== Configuration ===
Line 99:		Line 100:
	:When set to "off", disables tiled Z buffer. In the absence of any manual value, this is the default setting.		:When set to "off", disables tiled Z buffer. In the absence of any manual value, this is the default setting.
	* ClampDelta		* ClampDelta
	:Caution! This feature is experimental.		:'''Caution! This feature is experimental.'''
	:When set to "on", enables clamping of various values calculated by the Permedia's delta unit.		:When set to "on", enables clamping of various values calculated by the Permedia's delta unit.
	:When set to "off", no delta unit clamping is applied. In the absence of any manual value, this is the default setting.		:When set to "off", no delta unit clamping is applied. In the absence of any manual value, this is the default setting.
	* XLimitEnable		* XLimitEnable
	:Caution! This feature is experimental.		:'''Caution! This feature is experimental.'''
	:When set to "on", enables early horizontal clipping of polygons before the scissor unit. This may improve performance for applications which rely on scissoring to perform clipping of large polygons that are mostly outside the scissor area.		:When set to "on", enables early horizontal clipping of polygons before the scissor unit. This may improve performance for applications which rely on scissoring to perform clipping of large polygons that are mostly outside the scissor area.
	:When set to "off", no X limits testing is performed. In the absence of any manual value, this is the default setting.		:When set to "off", no X limits testing is performed. In the absence of any manual value, this is the default setting.
	* YLimitEnable		* YLimitEnable
	:Caution! This feature is experimental.		:'''Caution! This feature is experimental.'''
	:When set to "on", enables early vertical clipping of polygons before the scissor unit. This may improve performance for applications which rely on scissoring to perform clipping of large polygons that are mostly outside the scissor area.		:When set to "on", enables early vertical clipping of polygons before the scissor unit. This may improve performance for applications which rely on scissoring to perform clipping of large polygons that are mostly outside the scissor area.
	:When set to "off", no Y limits testing is performed. In the absence of any manual value, this is the default setting.		:When set to "off", no Y limits testing is performed. In the absence of any manual value, this is the default setting.

Karl Churchill: /* General tips */

2013-01-14T13:01:31Z

General tips

← Older revision		Revision as of 13:01, 14 January 2013
Line 177:		Line 177:
	=== General tips ===		=== General tips ===

	Radeon cards with ~~only~~ ~~32MB~~ of Video RAM may be at a disadvantage when running 3D applications that expect more memory to be available for textures ~~ans~~ buffers. To save memory, consider the following		Radeon cards with 64MB or less of Video RAM may be at a disadvantage when running 3D applications that expect more memory to be available for textures and buffers. To save memory, consider the following
	* Disabling compositing for Workbench screen.		* Disabling compositing for Workbench screen.
	* Switching to 16-bit screen depth for workbench screen.		* Switching to 16-bit screen depth for workbench screen.

Karl Churchill: /* Configuration */

2013-01-14T13:00:21Z

Configuration

← Older revision		Revision as of 13:00, 14 January 2013
Line 32:		Line 32:
	The hardware supported by Warp3D varies considerably in performance, implementation and available capabilities. For this reason, each driver is separately configurable through the use of environment variables. These settings are located in driver-specific subdirectories of the main ENV:Warp3D/ directory.		The hardware supported by Warp3D varies considerably in performance, implementation and available capabilities. For this reason, each driver is separately configurable through the use of environment variables. These settings are located in driver-specific subdirectories of the main ENV:Warp3D/ directory.

		⚫	=== Application Profiles ===
⚫	{{Note\|text=In the driver specific documentation that follows, all settings marked as experimental may be changed or removed without warning in future releases.}}

		⚫	Over time, the addition of new features and correction of bugs has resulted in a situation where compatibility with older titles has been affected. For example, in version 4 of Warp3D, an update to the Permedia2 driver added a new blending mode. While this was required for MiniGL titles such as Heretic 2, it resulted the famous "engine trail" bug in WipeOut 2097. Although the feature could be turned on and off through the use of an environment variable, there was no way to have a single configuration suitable for all.

		⚫	To address this problem, a feature has been added to selected drivers in Warp3D 5 that allows the driver configuration to be overridden on a per application basis. This works through the use of appropriately named subdirectories within the driver's own environment directory. The general path to these settings is ENV:Warp3D/<driver name>/<application name>/. Thus, when the application "ShootEmUpFTW" running on a Radeon 9250 allocates the 3D resources, the driver checks to see whether any of the driver's environment settings in the ENV:Warp3D/RadeonR200/ directory have also been set in the ENV:Warp3D/RadeonR200/ShootEmUpFTW/ directory. Any that have will override those in the main ENV:Warp3D/RadeonR200/ directory. This ensures that only those settings requiring customisation need be defined, rather than duplicating all of the settings.

	=== Using DOS Commands ===		=== Using DOS Commands ===
Line 48:		Line 52:
	The directories and files can also be manipulated directly but using the DOS commands is easier and guaranteed to be backwards compatible.		The directories and files can also be manipulated directly but using the DOS commands is easier and guaranteed to be backwards compatible.

		⚫	{{Note\|text=In the driver specific documentation that follows, all settings marked as experimental may be changed or removed without warning in future releases.}}
⚫	=== Application Profiles ===

⚫	Over time, the addition of new features and correction of bugs has resulted in a situation where compatibility with older titles has been affected. For example, in version 4 of Warp3D, an update to the Permedia2 driver added a new blending mode. While this was required for MiniGL titles such as Heretic 2, it resulted the famous "engine trail" bug in WipeOut 2097. Although the feature could be turned on and off through the use of an environment variable, there was no way to have a single configuration suitable for all.

⚫	To address this problem, a feature has been added to selected drivers in Warp3D 5 that allows the driver configuration to be overridden on a per application basis. This works through the use of appropriately named subdirectories within the driver's own environment directory. The general path to these settings is ENV:Warp3D/<driver name>/<application name>/. Thus, when the application "ShootEmUpFTW" running on a Radeon 9250 allocates the 3D resources, the driver checks to see whether any of the driver's environment settings in the ENV:Warp3D/RadeonR200/ directory have also been set in the ENV:Warp3D/RadeonR200/ShootEmUpFTW/ directory. Any that have will override those in the main ENV:Warp3D/RadeonR200/ directory. This ensures that only those settings requiring customisation need be defined, rather than duplicating all of the settings.

	== Permedia 2 ==		== Permedia 2 ==

Karl Churchill: /* Configuration */

2013-01-02T02:00:48Z

Configuration

← Older revision		Revision as of 02:00, 2 January 2013
Line 113:		Line 113:
	:When set to "on", interprets the colour format used for chroma testing to be ABGR, rather than the correct RGBA format. Older versions of the Permedia2 driver incorrectly implemented chroma testing using the hardware native ABGR format. Some applications, e.g: WipeOut2097, expect this to be the case and will not render transparency properly without it.		:When set to "on", interprets the colour format used for chroma testing to be ABGR, rather than the correct RGBA format. Older versions of the Permedia2 driver incorrectly implemented chroma testing using the hardware native ABGR format. Some applications, e.g: WipeOut2097, expect this to be the case and will not render transparency properly without it.
	:When set to "off", interprets the colour format to be RGBA as specified by the API. In the absence of any manual value, this is the default setting.		:When set to "off", interprets the colour format to be RGBA as specified by the API. In the absence of any manual value, this is the default setting.
			* LimitTextureSize
			:Normally, the Permedia2 permits textures up to 2048 pixels and applications which query Warp3D to determine the largest size for a texture will be given this value. Thus an application may try to allocate textures that, while legal, are impractically large. This parameter allows control over the value that is reported by the driver. Legal values are 128, 256, 512, 1024 and 2048. Any other values will be rounded to the nearest supported power of 2.

	=== Unsupported features ===		=== Unsupported features ===

Karl Churchill: /* Supported cards */

2013-01-02T01:49:01Z

Supported cards

← Older revision		Revision as of 01:49, 2 January 2013
Line 172:		Line 172:
	=== Supported cards ===		=== Supported cards ===
	* Radeon7000		* Radeon7000
	* (todo add rest)

	=== General tips ===		=== General tips ===

Steven Solie: /* Using DOS Commands */

2012-09-05T20:27:57Z

Using DOS Commands

← Older revision		Revision as of 20:27, 5 September 2012
Line 44:		Line 44:

	To unset an environment variable just use UnSetEnv instead of SetEnv as follows		To unset an environment variable just use UnSetEnv instead of SetEnv as follows
	UnSetEnv ~~SAVE~~ Warp3D/RadeonR200/GLQuake/Anisotropic		UnSetEnv DELETE Warp3D/RadeonR200/GLQuake/Anisotropic

	The directories and files can also be manipulated directly but using the DOS commands is easier and guaranteed to be backwards compatible.		The directories and files can also be manipulated directly but using the DOS commands is easier and guaranteed to be backwards compatible.

Steven Solie: /* Configuration */

2012-09-05T15:29:34Z

Configuration

← Older revision		Revision as of 15:29, 5 September 2012
Line 32:		Line 32:
	The hardware supported by Warp3D varies considerably in performance, implementation and available capabilities. For this reason, each driver is separately configurable through the use of environment variables. These settings are located in driver-specific subdirectories of the main ENV:Warp3D/ directory.		The hardware supported by Warp3D varies considerably in performance, implementation and available capabilities. For this reason, each driver is separately configurable through the use of environment variables. These settings are located in driver-specific subdirectories of the main ENV:Warp3D/ directory.

	~~'''NOTE''':~~ In the driver specific documentation that follows, all settings marked as experimental may be changed or removed without warning in future releases.		{{Note\|text=In the driver specific documentation that follows, all settings marked as experimental may be changed or removed without warning in future releases.}}

	=== Using DOS Commands ===		=== Using DOS Commands ===

Steven Solie: /* Using DOS Commands */

2012-09-05T15:28:22Z

Using DOS Commands

← Older revision		Revision as of 15:28, 5 September 2012
Line 45:		Line 45:
	To unset an environment variable just use UnSetEnv instead of SetEnv as follows		To unset an environment variable just use UnSetEnv instead of SetEnv as follows
	UnSetEnv SAVE Warp3D/RadeonR200/GLQuake/Anisotropic		UnSetEnv SAVE Warp3D/RadeonR200/GLQuake/Anisotropic

			The directories and files can also be manipulated directly but using the DOS commands is easier and guaranteed to be backwards compatible.

	=== Application Profiles ===		=== Application Profiles ===