Table of contents
Collapse the table of content
Expand the table of content

Version Numbers for Direct3D Version 10.1

Last Updated: 2/14/2017

Direct3D versions 10.0 and 10.1 supply #defines that the user-mode display driver uses for versioning. The user-mode display driver must examine the Interface member of the D3D10DDIARG_OPENADAPTER, D3D10DDIARG_CREATEDEVICE, and D3D10DDIARG_CALCPRIVATEDEVICESIZE structures that the driver receives in calls to the OpenAdapter10, CreateDevice(D3D10), and CalcPrivateDeviceSize functions to determine the version of the Direct3D DDI that the Direct3D runtime supports. The most significant 16 bits of the Interface member is the number of the Direct3D DDI major version. For Direct3D versions 10.0 and 10.1, this number is 10. The least significant 16 bits of the Interface member is the Direct3D DDI minor version. This minor-version value is bumped every time a Direct3D DDI breaking change is introduced. This minor-version value can also be bumped artificially to signify a stronger version change. The following #defines associate a Direct3D DDI minor version with a released version number (that is, D3D10_0 == x, D3D10_1 == y, where y > x).

The user-mode display driver should only examine the most significant 16 bits of the Version member of the D3D10DDIARG_OPENADAPTER, D3D10DDIARG_CREATEDEVICE, and D3D10DDIARG_CALCPRIVATEDEVICESIZE structures to determine when the Direct3D runtime is built. This value is manually bumped every time there is a non-breaking Direct3D DDI change. The driver might come to depend on each non-breaking DDI change over time. Therefore, the driver should ensure that the passed in DDI build version is greater than or equal to the *_BUILD_VERSION of the current driver and fail out if the driver is incompatible (perhaps while also providing a registry workaround). The least significant 16 bits of the Version member is the DDI revision version. The least significant 16 bits of Version is typically used to special case the driver based on bugs that are present in the Direct3D API. The driver must succeed creation for all values. However, the driver can change behavior depending on certain values. You should compare with these values by using >= because the numbers might rise arbitrarily due to runtime fixes. Also, you should not use "> (previous broken version)" (rather than ">= working version") because new revisions might appear that have version numbers between the two known numbers and do not contain the required fixes. The following #defines are for Direct3D DDI versioning:

#define D3D10_DDI_MAJOR_VERSION 10
#define D3D10_0_DDI_MINOR_VERSION 1
#define D3D10_0_DDI_BUILD_VERSION 4
#define D3D10_0_DDI_VERSION_VISTA_GOLD                          ( ( 4 << 16 ) | 6000 )
#define D3D10_0_DDI_VERSION_VISTA_GOLD_WITH_LINKED_ADAPTER_QFE  ( ( 4 << 16 ) | 6008 )

#define D3D10_1_DDI_MINOR_VERSION 2
#define D3D10_1_DDI_BUILD_VERSION 1
// Note: d3d10_1 doesn&#39;t currently ship on vista gold. // This definition is included for completeness in the 
// event that it does at some point in the future:
#define D3D10_1_DDI_VERSION_VISTA_GOLD                          ( ( 1 << 16 ) | 6000 )
#define D3D10_1_DDI_VERSION_VISTA_SP1                           ( ( 1 << 16 ) | 6008 )
#define D3D10_1_DDI_IS_LINKED_ADAPTER_QFE_PRESENT(Version)  (Version >= D3D10_1_DDI_VERSION_VISTA_SP1)

#define D3D10on9_DDI_MINOR_VERSION 0
#define D3D10on9_DDI_BUILD_VERSION 0

Send comments about this topic to Microsoft

© 2017 Microsoft