Drivers for AMD and NVIDIA graphics cards with DirectX 12 support
Microsoft recently released a set of logic and software tools for developing drivers for the new Windows 10. Both companies immediately took advantage of this and released beta versions of drivers for Windows 10 with support for DirectX 12AMD (for Windows 10) - https://mega.co .nz / #! MV9WRayA! pfcYLXSD7sUOyxXLpBueFf6r02kIOXldsnayxlyyPEg
AMD (modified for Windows 8.1) - https://mega.co.nz/#!dlEXRTBB!GdYiZjp2SIXk10
. windowsupdate.com/d/msdownload/update/driver/drvs/2015/03/200005382_2ff4b469bb291b2a34ce8c25c789f0a72264e276.cab
Driver installation is possible only from the test mode or with the function of mandatory driver signature verification disabled !!!
Most interesting is the modified AMD driver for Windows 8.1. It is based on a driver for Windows 10 with an unlocked VSR (Virtual Super Resolution)
screen
that AMD has for some unknown reason locked on the R9 285, R9 290, R9 290X and R9 295X. This feature allows you to run games at a higher resolution than your monitor is capable of, i.e. in FullHD, UltraHD, 2K, 4K and even 5K.
I have already installed this driver for myself and it works - my resolution is 1680x1050. I launched Shadow of Mordor at VSR 150% 2520x1575 and VSR 200% 3360x2100, with fps dropping from 60 frames to 38 frames and 23, respectively. Test Drive Unlimited 2 and Spec Ops do not support 2K or more, but they quietly launched in 1920x1200, i.e. in FullHD. Ryse Son of Rome also launched in 1920x1200.
the only caveat - for those whose R9 280X system will show not the R9 200 Series, but the HD 7900 Series, but this can be fixed:
- boot the OS in safe mode
- follow the path C: /Widows/Inf/oem6.inf
- look for by ID (for example, my card with ID 6798) the line AMD6798.1 = "AMD Radeon HD 7900 Series" and change to AMD6798.1 = "AMD Radeon R9 200 Series"
- reboot and enjoy the driver with unlocked functions and DirectX 12 support
this is only for the R series, so I have an HD 7600m and problems with CCC, it does not show all the windows and I can not configure anything. This is after the transition from 7 to 10. Reinstalled from scratch.
Does not download the modified for Win 8.1 and in oem6.inf I have neither 7900 nor AMD6798.1
smile437
Well, probably the person wanted to quickly help people and in a hurry gave a user link, not the main page. Not to mention the fact that some computers simply do not see what others can see due to security concerns.
There is
no main page for Mitsu Rju , the link to the FO was uploaded by the one who assembled this driver.
if they do not work, then the author deleted them, or did not renew them due to the new driver version.
starting with Catalyst 15.7, the driver has implemented extended support for VSR - in addition to the top 290, 390 and Fury, AMD also added medium cards 285, 380 (maybe some 270, for example, I don’t know).
NVIDIA has a similar situation - in the new 355.xx drivers, DSR is available for a large number of video cards.
all these drivers support DirectX 12 for versions under Windows 10.
so there is no need for those mods anymore.
tesla707
As for the link, I'm just for example, since I've already met this when users come in as registered and then drop the link of their page.
And about VSR and directive 12, for example, the company threw off the Omega-14.12 driver for me, there is a similar combination, I don’t know, maybe only for me, because I tried to find a similar one. I didn’t find it!
My install is 330mb. and the site offers two hundred something for everyone.
Now it costs 14.7.1. not complaining.
Has anyone tried to play around with dirext 10 vidyashki? and try to run 12 on them?
kolders wrote: has
anyone tried to play around with dirext 10 vidyashki? and try to run 12 on them?
it's impossible.
function in DirectX 10.1 - D3D10CreateDevice1 adopts the following hardware levels
typedef enum {D3D10_FEATURE_LEVEL1
D3D10_FEATURE_LEVEL_10_1 = 0xa100,
D3D10_FEATURE_LEVEL_10_0 = 0xa000,
D3D10_FEATURE_LEVEL_9_3 = 0x9300
D3D10_FEATURE_LEVEL_9_2 = 0x9200,
D3D10_FEATURE_LEVEL_9_1 = 0x9100,
} D3D10_FEATURE_LEVEL1;
function in DirectX 11 - D3D11CreateDevice accepts the following hardware levels
typedef enum D3D_FEATURE_LEVEL {
D3D_FEATURE_LEVEL_11_0 = 0xb000,
D3D_FEATURE_LEVEL_10_1 = 0xa100,
D3D_FEATURE_LEVEL_10_0 = 0xa000,
D3D_FEATURE_LEVEL_9_3 = 0x9300,
D3D_FEATURE_LEVEL_9_2 = 0x9200,
D3D_FEATURE_LEVEL_9_1 = 0x9100,
} D3D_FEATURE_LEVEL;
function in DirectX 12 - D3D12CreateDevice adopts the following hardware levels
typedef enum {D3D_FEATURE_LEVEL
D3D_FEATURE_LEVEL_12_1 = 0xc100,
D3D_FEATURE_LEVEL_12_0 = 0xc000,
D3D_FEATURE_LEVEL_11_1 = 0xb100,
D3D_FEATURE_LEVEL_11_0 = 0xb000,
} D3D_FEATURE_LEVEL;
As you can see from the specifications, it is not possible to run hardware levels from Dx10 on Dx12, due to their absence in the API itself.
video cards with a hardware level D3D_FEATURE_LEVEL_11_0 = 0xb000 and higher can work with Dx12.
the maximum that is possible is to run the Dx11 application on a Dx10 video card (this is exactly what was done in the game The Witness).
tesla707
hmm ... sadly,
in general, they threw the developed video cards on dx10,
but oh well,
modified drivers for amd are removed from the links,
but did someone try to register drivers for old video cards on drx10 to change them at the software level for reading dx11?
the method with the SDK is useless because the percent is brutally loaded
hmm ... it's sad,
in general, they threw the developed video cards on dx10,
but oh well,
modified drivers for amd are removed, they are not available on the links,
but did anyone try to register drivers for old video cards on drx10 to change them at the software level for reading dx11?
the method with the SDK is useless because the percent is brutally loaded