• 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

So, any news on Elite Dangerous CrossFire driver Matt/Joe?

This is beyond embarrassing at this point one must point out.
 
So, any news on Elite Dangerous CrossFire driver Matt/Joe?

This is beyond embarrassing at this point one must point out.

It's clearly by now something out of AMD's hands.. If I was you and rest amd users better start pointing the finger at the devs.

It's so easy to point at drivers. Drivers isn't everything they is far more that happens outside of AMD's control.
 
It's clearly by now something out of AMD's hands.. If I was you and rest amd users better start pointing the finger at the devs.

It's so easy to point at drivers. Drivers isn't everything they is far more that happens outside of AMD's control.

Pretty sure I recall that it was and AMD issue as it was meant to be looked into. I don't recall Matt ever saying this was not an AMD issue, otherwise all those months ago, well a year ago maybe eyetrip would have been pestering the devs, not AMDMatt. lol
 
Anyone else having problems in Crossfire in Windows 10 where even with ULSP disabled, the second card still turns off?

I am, afterburner even froze my computer on launch. I knew I should have waited a bit longer before upgrading to windows 10. Waited a few weeks, but should have waited until January or something.
 
Pretty sure I recall that it was and AMD issue as it was meant to be looked into. I don't recall Matt ever saying this was not an AMD issue, otherwise all those months ago, well a year ago maybe eyetrip would have been pestering the devs, not AMDMatt. lol

Am just giving my advice here. I firmly believe this crossfire profile is something else not just drivers.
Just because it's been looked into doesn't mean it's a driver issue.
 
Am just giving my advice here. I firmly believe this crossfire profile is something else not just drivers.
Just because it's been looked into doesn't mean it's a driver issue.

I understand that. Thank you for advice. But how long does it take to be "looked into"? They should either fix it, or say it is a issue with the devs, not keep customers in the dark for a year...

These are tough times for AMD, they need to be taking care of their loyal customers I would say. It is because of stuff like this people get pushed to nvidia in my opinion.

I want to see AMD succeed and win market share back, but way things are going, unless they do very well with DX12, they will lose even more market share, which is very sad. I do not want to pay £1000 for a £400 worth GPU like some don't mind doing :(
 
I am, afterburner even froze my computer on launch. I knew I should have waited a bit longer before upgrading to windows 10. Waited a few weeks, but should have waited until January or something.

Even with it disabled in Trixx, it still turns off, even tried doing it in the Registry and still turns off, which makes me think it's a Windows 10 issue
 
I understand that. Thank you for advice. But how long does it take to be "looked into"? They should either fix it, or say it is a issue with the devs, not keep customers in the dark for a year...

These are tough times for AMD, they need to be taking care of their loyal customers I would say. It is because of stuff like this people get pushed to nvidia in my opinion.

I want to see AMD succeed and win market share back, but way things are going, unless they do very well with DX12, they will lose even more market share, which is very sad. I do not want to pay £1000 for a £400 worth GPU like some don't mind doing :(

I do agree with you on been kept in the dark and it's something I have said I wish was better from amd communication is key at times.

I have posted on AMDs support forum see if I can find anything out.
 
I do agree with you on been kept in the dark and it's something I have said I wish was better from amd communication is key at times.

I have posted on AMDs support forum see if I can find anything out.

Thanks dude.

I also hope to hear back from Matt/Joe on this too when they read this.
 
Even with it disabled in Trixx, it still turns off, even tried doing it in the Registry and still turns off, which makes me think it's a Windows 10 issue

I am just going to leave it alone for now. As long as my games working fine, no need to disable it. But need to try my games to find that out.
 
I do agree with you on been kept in the dark and it's something I have said I wish was better from amd communication is key at times.

I have posted on AMDs support forum see if I can find anything out.

I recall Matt saying that this game had 'got by them,' or words to that effect, some time ago; but he would do what he could to push for a profile. So I'm not convinced this lies with the game devs...nvidia SLI works fine apparently.

I suspect its simply not been a priority, and keeps getting de-prioritised when it gets towards the top of Amd's driver queue. Of course, if there is some technical reason why Amd hardware specifically has trouble with crossfire in Elite then I'll happily take that back. But after nearly a year of silence, what are we supposed to think?

Not a dig at Matt btw, I'm sure he's made the right requests.
 
Another AMD noob question here - isn't there a default Crossfire mode that just works in some generic way when there is no specific game profile defined? IIRC nV uses something like this for SLI right?

I've never used either, so don't know how this stuff works :D
 
Another AMD noob question here - isn't there a default Crossfire mode that just works in some generic way when there is no specific game profile defined? IIRC nV uses something like this for SLI right?

I've never used either, so don't know how this stuff works :D

Yes.
 
Back
Top Bottom