This value is manually bumped every time there is a non-breaking Direct3D DDI change. 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. 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). This minor-version value can also be bumped artificially to signify a stronger version change. This minor-version value is bumped every time a Direct3D DDI breaking change is introduced. The least significant 16 bits of the Interface member is the Direct3D DDI minor version. For Direct3D versions 10.0 and 10.1, this number is 10. The most significant 16 bits of the Interface member is the number of the Direct3D DDI major version. 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. Direct3D versions 10.0 and 10.1 supply #defines that the user-mode display driver uses for versioning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |