15.3 BETA drivers now out

Crossfire seems ok with the games I have. I don't own the games that you're all having issues with.

The OpenCL 2.0 driver is still messed up for GCN 1.0 cards like my 7970's. FAH TPF is down 40% guess it's just optimized for the 2xx series and above just like the 14.12 Omega's were.
Fortunately canceling the installation and replacing the 10 opencl components from the 14.9 beta into the installation files then continuing seems to work as it did with the Omega driver.
I did get the same UAC warning pop up as before.
 
I've only tried hardline with these, but they seem fine so far. Pretty good perf on ultra for me and no stutters or anything.
 
Doing a binary diff on omega & these, 92 out of the 119 files are different.
Looking at the direct3D dlls, they *were* changed, however, they didn't bump the version numbers. :nuts:

That is a horrible practice, and I am surprised it isn't automated to bump the version numbers.
 
I can't wait to see if these still have the same bug as the omegas where my third display never goes into sleep, it just goes black. I bet it does.
 
Qamly said:
Doing a binary diff on omega & these, 92 out of the 119 files are different.
Looking at the direct3D dlls, they *were* changed, however, they didn't bump the version numbers. :nuts:

That is a horrible practice, and I am surprised it isn't automated to bump the version numbers.
Click to expand...

They do that quite often.

doing a binary compare is really the only way to tell.
 
AMD Catalyst (15.200.1012.2 March 11) Win 8.1 Mod - VSR for HD7/R7/R9 & FPS limiter

AMD Catalyst (15.200.1012.2 March 11) Win 8.1 Mod - VSR for HD7/R7/R9 & FPS limiter

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.
Click to expand...
http://forums.guru3d.com/showthread.php?t=397877
 
Yeah, it's working so far for me with my HD 7950. 2560 x 1440 is now an option though I've only tested it a little bit.
 
great quality control AMD, displayport sleep problem still exists. My two DVI displays go to sleep and my DP display does not. I guess I get to go back to 14.11b, For ****s sake AMD, really? Eyefinity such a big selling point with such a stupid bug. cool.

For clarification, DVI monitors 1 and 2 say "No signal detected!" and go to rest. DP monitor (3) say "No signal detected!" and then about 1 second later says "Input: DP" and then sits live but black.
 
Last edited:
_TiTaNiuM said:
great quality control AMD, displayport sleep problem still exists. My two DVI displays go to sleep and my DP display does not. I guess I get to go back to 14.11b, For ****s sake AMD, really? Eyefinity such a big selling point with such a stupid bug. cool.

For clarification, DVI monitors 1 and 2 say "No signal detected!" and go to rest. DP monitor (3) say "No signal detected!" and then about 1 second later says "Input: DP" and then sits live but black.
Click to expand...
I have a similar setup, with two screens attached via DVI and one screen attached via DP. I'm not seeing the same behavior (DP connected monitor sleeps properly). R9 270.

You've confirmed this is a driver / vidcard specific issue? Eliminated cable? Eliminated monitor? Eliminated ...?
 
Lupine said:
I have a similar setup, with two screens attached via DVI and one screen attached via DP. I'm not seeing the same behavior (DP connected monitor sleeps properly). R9 270.

You've confirmed this is a driver / vidcard specific issue? Eliminated cable? Eliminated monitor? Eliminated ...?
Click to expand...

It only happens with 14.12 and 15.3, all older driver revisions do not exhibit this issue.

Windows version? I am on 8.1 64bit, though I have R9 290x's, 270's are the older generation card are they not?

it sleeps fine when grouped in an eyefinity displaygroup but when in single displays it wakes right up.



still loving how they broke win+p switching between eyefinity and extended desktop like 4-5 drivers ago too, that's gotta be my favorite.
 
Last edited:
_TiTaNiuM said:
great quality control AMD, displayport sleep problem still exists. My two DVI displays go to sleep and my DP display does not. I guess I get to go back to 14.11b, For ****s sake AMD, really? Eyefinity such a big selling point with such a stupid bug. cool.

For clarification, DVI monitors 1 and 2 say "No signal detected!" and go to rest. DP monitor (3) say "No signal detected!" and then about 1 second later says "Input: DP" and then sits live but black.
Click to expand...

I have two LCD monitors connected via DVI and one connected via DP->DVI. On my own Windows 7 Pro x64 system, using HD 7970, my monitors all go to sleep fine and wake up fine. I just tested it to be sure. I normally don't use the sleep mode but prefer a screen saver mode.

I do, however, recall posting quite some time ago about a problem getting monitors to come back out of sleep. But, that was at least 2 to 3 years ago and under very different circumstances.
 
Last edited:
using 15.3 beta

I still have issues with screen blanking in eyefinty and eyefinity not being retained after a reboot.

to get around the blank screen, I either alt tab to a full screen game. It may take a few times

Or I right click on the desktop, select screen resolution, change to 3072x768 and then revert back to 5760x1080
Sometimes you might have to use you winkey and arrow left to move the screen resolution dialog to a visible display so you can click on it.

Seems mode changes are where AMD is screwing up.
 
Dyre Straits said:
I have two LCD monitors connected via DVI and one connected via DP->DVI. On my own Windows 7 Pro x64 system, using HD 7970, my monitors all go to sleep fine and wake up fine. I just tested it to be sure. I normally don't use the sleep mode but prefer a screen saver mode.

I do, however, recall posting quite some time ago about a problem getting monitors to come back out of sleep. But, that was at least 2 to 3 years ago and under very different circumstances.
Click to expand...

That's not quite the same configuration, you have your DP adapted to DVI. I am using a straight DP cable.
 
blurter said:
Fair enough but come on........4 month wait for this, pffffffffft! what a joke! This company has egg on it's face right now simple as that. :rolleyes:
Click to expand...

Do you guys ever consider that it could be a problem with the game and it's coding.. Why do people always expect AMD to fix piss poor coded game via drivers?
 
t0adp1p3 said:
Anyone test hardline single player in mantle and see if it now has the same gamma issue as dragon age inquisition. It does on my end, think I'm gonna roll back to the previous drivers until I finish the campaign, then I'll reinstall these and play farcry 4. By then hopefully dying light will have a profile.....also the hardline profile is worse than in the last betas I lose a ton of fps in dx 11 with the new profile.


And WaltC your welcome to your opinion, I am welcome to mine. My opinion is AMD's support for crossfire has been lacking for the past 4 months and this driver is not exactly stellar. I am glad you can play your 10 yr old games on your single card, the issue I am having is with new games on 3 cards.... And I am not crying about having twins going to college or about having a wife, lol. I'm very happy with my life, heck yeah my kids are gonna be out of the house! Gaming is a hobby, and something I do to unwind occasionally.
Click to expand...

You are allowed your opinion, but facts are facts. Game code plays the biggest part in crossfire. There are many games released in the past couple years that do not support crossfire or any multi GPU setup be it NVIDIA or AMD. Yes some of those games can be made to work thru driver manipulation and some can't. There are some cases that it is AMD's fault, but in most cases, it is the games developer's fault, and AMD does it's best to correct it thru driver manipulation. Yet many people believe it is fully in AMD's control which is not the case.
 
You must log in or register to reply here.
Back
Top