Driver Profile Settings

This page is a work in progress - feel free to expand it with extra knowledge, before & after screenshots, etc.

Tools

There are two tools that can be used to edit the game profiles:

NVIDIA Inspector (English mirror)

and

GeForce 3D Profile Manager

Note that NVIDIA Inspector has some bugs and limitations, which may prevent some settings from being displayed (e.g. almost any text setting) and in some cases edited in full (Helifax noted this prevents changes to 2DDHUDSettings from taking effect).

NVIDIA Inspector Custom Stereo Settings Names

Download this CustomSettingNames_en-EN.xml file to replace the one from NVIDIA Inspector, which will add all the settings listed on this page to the Stereo category.

The Mystery Stereo Setting 0x701EB457

This setting is known to be very important to stereo profiles.

Observations

- The mere existance of this setting on a DX9 profile will enable Stereo in windowed mode, regardless of the value.

- This setting is required to enable a lot of stereo related code in the driver.

- Certain other stereo settings (e.g. StereoTextureEnable) may be ignored without this setting.

Bit Definitions

0xFFFFFFFF

UNKNOWN :(

Known Values

0x00000001	Seen in many stereo profiles created with Ctrl+F7
0x2241AB21	Used by many games (Aion, Prototype 2, ...)

Notable Settings

StereoTextureEnable (0x70edb381)

Believed to control the heuristics that determine which texture render targets are stereoised and which are not.

Observations

- Setting this to all F's will turn a game into mono, suggesting that some high bits might filter out some render targets, rather than enabling them.

Bit Definitions

Chiri determined a number of these (see this post)

0x00000001	[ET] = Stereoize render target textures which are of size or exceeding the size of the backbuffer (and are not square).
0x00000002	[ESMT] = Stereoize all non square render target textures smaller then backbuffer.
0x00000004	[ESQT] = Stereoize sqare render target textures.
0x00000008	[DBBST] = ???
0x00000010	[DBBS] = ???

StereoUseMatrix (0x70e34a78)

- Able to automatically fix halo type issues in many games

Known Values

0x1945B570

Used by Aion, Prototype 2, etc.

StereoFlagsDX10 (0x702442fc)

- Able to resolve mono depth buffer issues in DirectX 11 games, such as Far Cry 4 and Ryse: Son of Rome.

Bit Definitions

0x00004000	Fixes mono depth buffer issue in Far Cry 4 (SLI users can alternatively resolve this with custom SLI compatibility bits)
0x00000024	One of these two bits negated the separation value reported to 3Dmigoto in Far Cry 4, but not Max Payne 3?

Known Values

0x1C22FE24

Max Payne 3 (good profile to use for testing)

StereoCutoff (0x709a1ddf)

Present in almost all Stereo profiles, but meaning unknown. My complete guess is that it may be related to driver heuristics to decide when the stereo correction formula is applied (e.g. for UI elements)?

Observations

- Setting this to 0x00000000 broke shadows in Miasmata

More Settings

StereoConvergence (0x708db8c5)

Stores the convergence value of a profile. Unsure of encoding - sometimes interpreting this as a float gives a reasonable value, but other times it doesn't.

Comments (0x704d456e) - text

Stores the comments displayed in the green text by the driver. Sometimes this is clearly an ASCII string, other times it is gibberish, suggesting that it is not always encoded the same way.

Developer_Issues (0x704f5928) - text

Alternate setting for the comments displayed in the green text by the driver.

StereoMemoEnabled (0x707f4b45)

0x00000000	Green text disabled
0x00000001	Green text enabled

Compatibility Mode Settings

Helifax created a guide with more information about these settings: Guide: How to Enable and TWEAK 3D Compatibility Mode in any DX11 Game

2DD_Notes (0x709adadc) - text

Notes displayed when compatibility mode is enabled

VR Direct Settings

These settings have appeared in recent drivers and are believed to be related to VR Direct:

Key Bindings

These are believed to be key bindings due to their names. It has not been confirmed if these override the registry settings or are ignored. Some of these settings may not work at all in recent drivers.

There is a good guide for how these are encoded here: Modifying All 3D Vision Control Key Combinations as You Need

ToggleAutoConvergence (0x70085de3)

NOTE: AFAIK this was never implemented

ToggleAutoConvergenceRestore (0x703bc51e)

NOTE: AFAIK this was never implemented

GlassesDelayPlus (0x701fc5b4)

NOTE: Believed to no longer work in recent drivers

GlassesDelayMinus (0x70b8a743)

NOTE: Believed to no longer work in recent drivers

Unidentified Settings

These setting names were found in the driver, but their purpose or whether they are even functional is unknown:

Date_Rel (0x705fafec) - text

May contain the release date in the form YYYY-MM-DD 00:00:00

API (0x70b5603f) - text

Usually contains "D3D" or sometimes gibberish (decoding issue?)