so it may be referring to the optimal core instead of the first one you see or might expect.
HKR, UserModeDriverName, %REG_MULTI_SZ%, umd.dll, umd.dll, umd.IMPORTANT NOTE using ryzenmaster and checking your CCX and individual cores some cores are golden sample sorta 'go a bit faster than other cores maybe'. The following example shows how support for the version 11 DDI is enabled if the version 11 DDI is contained in Umd.dll (that is, a shared implementation of Direct3D version 9, 10 and 11 drivers): HKR, InstalledDisplayDrivers, %REG_MULTI_SZ%, umd9, umd10, umd11 HKR, UserModeDriverName, %REG_MULTI_SZ%, umd9.dll, umd10.dll, umd11.dll The following example shows how support for the version 11 DDI is enabled if the version 11 DDI is contained in Umd11.dll (that is, a separate DLL from the version 9 and 10 DDIs): In fact, the design of the Direct3D version 10 and version 11 DDIs strongly supports a shared implementation of Direct3D version 10 and Direct3D version 11 drivers. You can use the same user-mode display driver DLL name in multiple locations to unify your driver implementation.
To also enable support for the Direct3D version 11 DDI, you must specify the name of the DLL that contains the version 11 DDI as the third entry in the list of user-mode display driver names even if the version 11 DDI exists in the same DLL as the version 9 and 10 DDIs. The Installation Requirements for Display Miniport and User-Mode Display Drivers section describes how a user-mode display driver is installed and used according to the Windows Vista display driver model. To enable support for a user-mode display driver DLL's version 11 DDI, the INF file that installs the display drivers for a graphics device must list the name of the DLL regardless of whether the Direct3D version 11 DDI exists in the same DLL as the Direct3D version 9 DDI and Direct3D version 10 DDI or in a separate DLL. This section applies only to Windows 7 and later, and Windows Server 2008 R2 and later versions of Windows operating system.
0 kommentar(er)
