Radeon Software Crimson Edition 16.3.1

[Headfoot]

The problem with both Crossfire and Eyefinity is that if the game dev didn't care enough to do it on their own, having AMD bug them about it isn't going to make them care any more. And the majority of the problem lies in the game code, especially for eyefinity, but to a great degree for Crossfire too. The reason they dont do it is that there wasn't a good economic rationale in their eyes, and that doesn't change post-release (in fact, they probably care even less post release)

There's just no way to cleanly, after-the-fact in drivers without game dev cooperation, AFR-ify all these popular and good looking new lighting techniques that reuse data from frame to frame. As well as the mass exodus to deferred rendering.

The change to DX12 multi adapter is well overdue.

They seem to be able to sort these issues out in a month after release. Makes you wonder why this process isn't happening in the month just prior to release instead...

 

[Bacon1]

Eyefinity usually works reasonably well on older games, but on something like ffxiv - where it WAS supported and IS stamped with AMD's "Gold" Eyefinity cert (http://support.amd.com/en-us/recommended/eyefinity-software#k=#s=81), and support was pulled without warning and for apparently no reason, even with one card running instead of two....

completely unacceptable.

Likewise crossfire was also supported officially for quite some time. Then that was pulled as well without warning and for apparently no reason.

Both were supported together officially for quite some time as well. Then that was pulled as well without warning and for apparently no reason.

Every think that maybe, just maybe, it was some changes in the game itself that broke it?

Crossfire / SLI are hacked into games at the moment, they force them to render differently which is why they require driver specific changes.

DX12 will bring true multi-adapter (GPU) support but will require the developers do implement it. Stardock is also working on something to help with that, not sure if they released details at GDC.

 

[cbrunny]

Every think that maybe, just maybe, it was some changes in the game itself that broke it?

You say that as if it makes it ok somehow. Frankly I don't care who is "at fault" but given that both SLI and Surround work while CF and Eyefinity worked in the past and now don't.....

 

[Bacon1]

You say that as if it makes it ok somehow. Frankly I don't care who is "at fault" but given that both SLI and Surround work while CF and Eyefinity worked in the past and now don't.....

I never said it was ok either, I'm just saying that blaming AMD won't fix it. Blame the game developers too.

They had a major re-write of their engine which added lots of IQ updates, not sure if thats when it broke or not.

If it stops working between two driver releases then fill out a bug report with AMD. If it just stops working one day with no changes in drivers, its the game.

 

[cbrunny]

I've logged multiple bug reports with AMD and Square Enix. I'll continue to do so but I don't expect anything to change. Pretty sad.

 

[railven]

Not surprisingly, a lot of the issues that rose in FFXIV happened after AMD lost partnership to NV. The reason it had good support for CFX/Eyefinity at the start was most likely due to it being a Gaming Evolved title. However, for whatever reason AMD didn't continue the partnership with the DX11 client, and thus Heavensward, which is around when I started to get issues with my rig. Once Heavensward launched AMD hardware was basically broken.

Sure, we can all identify what was likely the cause, but that doesn't excuse AMD to essentially ignore its users who have been complaining for almost a year now.

I've said it before, AMD continues to ignore a huge PC market - the MMO crowd - and it's most likely a root of their struggling sales. I know now they are working with LOL's new owner, which is a start. They's got a long way to go.

 

[railven]

I've logged multiple bug reports with AMD and Square Enix. I'll continue to do so but I don't expect anything to change. Pretty sad.

This also bugs me about some of the posters around here. Take Karlitos thread - the guy was essentially accused of PEBKAC even though he cited where and when the problems started. Low and behold AMD fixed it, but for a good portion of his thread, he was the issue - not AMD.

 

[cbrunny]

I did actually get FFXIV to acknowledge the Eyefinity problem, which is a HUGE step forward from my efforts: http://forum.square-enix.com/ffxiv/threads/287087-Eyefinity-Unavailable

I think more people will complain about CF than Eyefinity, and since a single 7970 can push pretty well at 5760x1080 on ffxiv (in 2.0, at least) my focus has been on the Eyefinity thing. Lend your support! Post on there as well. They've accepted the bug but I don't know what the odds of it actually getting fixed are.

And fwiw, by acknowledge the problem, I mean they accepted the bug report. lol.

 

[thesmokingman]

Hmm, just updated to 16.3.1 on my son's dual 7970 rig and I notice the power efficiency toggle is there but it is confused. Sometimes it shows on, sometimes off, sometimes it's missing. I figured out that if I click around I can make it show up, off, on, or missing lol. Awesomness.

 

[Rvenger]

Hmm, just updated to 16.3.1 on my son's dual 7970 rig and I notice the power efficiency toggle is there but it is confused. Sometimes it shows on, sometimes off, sometimes it's missing. I figured out that if I click around I can make it show up, off, on, or missing lol. Awesomness.

You'll probably get a BSOD. Its not supposed to be there at all. My Nano doesn't even have a Power efficiency toggle.

 

[Kenmitch]

Latest windows 10 pro build with these drivers show in device manager under unknown tab instead of graphics. Both cards show drivers installed and fully functional. 390's in crossfire.

Anybody else have this issue?

 

[thesmokingman]

You'll probably get a BSOD. Its not supposed to be there at all. My Nano doesn't even have a Power efficiency toggle.

No crashing from what I've seen.

 

[cbrunny]

Latest windows 10 pro build with these drivers show in device manager under unknown tab instead of graphics. Both cards show drivers installed and fully functional. 390's in crossfire.

Anybody else have this issue?

I checked yesterday on my 2 7970s. I did not have this behaviour though.