• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

This is the Windows 10 driver distributed via Windows Update, now modified to work with Win 8.1.

VSR and FPS limiter are enabled (the card must support it) CCC is from 15.3 Beta to avoid issues.
Based on reports in this thread looks like VSR is working for HD7000, R7, R9 280 and possibly more so try for yourself and report back.
On R9 290 Series the resolution is unlocked up to 4K. (3840x2160)

To install and use this driver you must enable the "Test Mode" or disable the driver signature enforcement.
This driver is for advanced users only, if you do not know what you are doing stay away from it.

I thought VSR wasn't coming to HD7000?. Or am I getting mixed up with FreeSync?.
 
Ok so after more time in FC4 it's still running smooth with 3 x 290's and I don't have to do the whole gamerprofile.xml trick. (not sure why I'm lucky?) Either way one problem I AM having though, is randomly crashing to desktop. It's happened twice now (in about 4 hours of gameplay total). No rhyme or reason. Just wondering if anyone else has had this. Seems to be an issue on both sides even since launch, but I never had it before :(
 
Try running on two cards, as that was what i tested on. I will try three next time i fire the game up.

Is there a way to specify number of cards on a per game basis?

Not that matters, going to leave this game a while. See if patches come or maybe try again after next driver.
 
After not using the Oculus Rift for a month or so, and on my new card, I got a BSoD when trying the built in Rift demo in the config utility. I'm using the 14.12 Omega drivers, downloading the newest version now. Is there a fix? My heart stopped when I saw BSoD..
 
Thanks. I knew of that setting, but that is a global setting isn't it?

I was wondering if there were some way to do it for individual games?

Unless I am missing something.

No.

You could make a Preset to do it and Launch the game at the same time but the game would kick off before CF was finished rearranging to 2 GPUs and would likely crash.
 
Last edited:
Tested the Cat 15.3 Betas:

FC4 is burst! Very bad stutter very apparent with V Sync and triple buffering on. GameWorks stuff is all off, same with any level of setting! 60fps reported but not smooth. Also I cannot enable SMAA! In options looks to have saved, but when I go back into check AA is OFF! OK with MSAA.
I have also edited the xml file and disabled LoadingMip0 and GPUMaxBufferedFrames - makes no difference!
Back to the trusty 14.12's and an AFR profile and boom!:
FC4 now buttery smooth with all settings maxed, including GameWorks stuff! MSAA x2. Still however cannot enable SMAA! iirc though, with these drivers it caused ghosting! Would like to get to the root cause however on why it does not work! Any advice?
 
Are we getting a new set of drivers today or are the 15.3 beta the drivers to use for the new 3DMark test releasing this afternoon? (API Overhead feature test for DirectX 12 & Mantle)

In the meantime I need to get windows10 ready for it.
 
Are we getting a new set of drivers today or are the 15.3 beta the drivers to use for the new 3DMark test releasing this afternoon? (API Overhead feature test for DirectX 12 & Mantle)

In the meantime I need to get windows10 ready for it.

We have a DirectX 12 driver already on Windows 10 available Via Windows Update.

For Windows 8.1 (Mantle + DX11) 15.3 is the driver to use.
 
Normal SMAA does not work with multi gpu, so that's to be expected.

I noticed this too, and it's not what happened before the 15.3 drivers. I don't know if its a far cry patch or the driver, but before this update, you used to be able to select SMAA. It was buggy. But now if you select it, it gets disabled.

It's a shame it was disabled rather than being fixed.
 
Back
Top Bottom