The AMD Driver Thread

LtMatt · 21 Mar 2015 at 09:54

eyetrip said:
Matt, this is the entirety of the problem - Communication.

You didn't announce this, but it was in a driver of some kind that someone found, so without any communication from AMD, it was easy to make an assumption.

We can only make assumptions, because nothing is ever communicated to us.

We were told you were holding off this driver because AMD wanted it "just right" or something along those lines.

And yet, they are still missing profiles for a number of games, there doesn't seem to be any performance improvements to speak of (or am sure they would have been mentioned in notes), the list issues is longer than the fixes... and if I am reading right, no updates to VSR?

So, we can only come to the conclusion that almost all development was stopped to get freesync working, which will benefit far fewer people.

I know you are not responsible, but maybe you have enough clout with someone, somewhere, to let them know that their approach to all this has been shoddy.

And if we had had some communication, it would have managed peoples expectations far better.

Yes it came via a Windows 10 driver unexpectedly, sometimes these things happen - things get leaked. We'll announce the feature and release it in a future driver.

We're also still working on further improvements to VSR and we'll publish these when they are ready. You may find that funny, i see your sig but that's what's going to happen.

Superpatsy said:
Reading through several threads on this forum and the likes of Reddit and the such.

I'm now onto my fourth reinstall using DDU to see if it'll do anything and it won't.

Okay, but we've never announced it would be coming to the 7xxx series. If you don't hear it from us officially, then I'd always tread with caution.

Superpatsy · 21 Mar 2015 at 10:02

AMDMatt said:
Yes it came via a Windows 10 driver unexpectedly, sometimes these things happen - things get leaked. We'll announce the feature and release it in a future driver.

We're also still working on further improvements to VSR and we'll publish these when they are ready. You may find that funny, i see your sig but that's what's going to happen.

Okay, but we've never announced it would be coming to the 7xxx series. If you don't hear it from us officially, then I'd always tread with caution.

I am aware that it isn't coming to the 7xxx series which doesn't concern me considering I have the 280X's for now.

Still can't get CCC to open though...

LtMatt · 21 Mar 2015 at 10:04

Superpatsy said:
I am aware that it isn't coming to the 7xxx series which doesn't concern me considering I have the 280X's for now.

Still can't get CCC to open though...

Okay, well we're working to explore additional options to bring VSR to your gpu. Thracks set a timeline of JAN/FEB i know, so our bad on that front as we didn't make that, but we are working on it. We've never suggested VSR will be coming to the 7xxx series.

Superpatsy · 21 Mar 2015 at 10:36

AMDMatt said:
Okay, well we're working to explore additional options to bring VSR to your gpu. Thracks set a timeline of JAN/FEB i know, so our bad on that front as we didn't make that, but we are working on it. We've never suggested VSR will be coming to the 7xxx series.

I hope I don't come across as cheeky but why do you keep mentioning that it isn't coming to the 7xxx series when I was asking with regards to my two 280X's?

LtMatt · 21 Mar 2015 at 10:39

Superpatsy said:
I hope I don't come across as cheeky but why do you keep mentioning that it isn't coming to the 7xxx series when I was asking with regards to my two 280X's?

Not cheeky at all. It's important the distinction is made, just setting expectations accordingly.

bennj · 21 Mar 2015 at 10:50

So 2 months after the release of Dying Light, still no crossfire profile...

I know why i came back to NVidia. I was not happy to do it but THIS is unacceptable

dbmzk1 · 21 Mar 2015 at 10:50

AMD release first driver in months and it... does absolutely nothing what so ever. Utter fail, no wonder their market share is falling fast.

Might sell my 290X and get a 970/980

LtMatt · 21 Mar 2015 at 10:57

bennj said:
So 2 months after the release of Dying Light, still no crossfire profile...

I know why i came back to NVidia. I was not happy to do it but THIS is unacceptable

We have a Crossfire profile included in the drivers. Unfortunately the game has an issue where Crossfire is not working as intended.

If you think back to our release notes in the 14.1.2 driver when Farcry 4 launched, it's a similar story.

We're hopeful that a future game patch is going to fix the issue, at which we point we can enable our existing Crossfire profile.

Some things are out of our hands I'm afraid.

Ayahuasca · 21 Mar 2015 at 10:58

Any idea why it is then that your competitor don't have these multi GPU issues with those games and AMD do?

tommybhoy · 21 Mar 2015 at 11:03

GW's are in the titles that are causing problems/delays, from it's inception it was highlighted/rubbished that it would/wouldn't give Nvidia the upper hand.

LtMatt · 21 Mar 2015 at 11:05

Ayahuasca said:
Any idea why it is then that your competitor don't have these multi GPU issues with those games and AMD do?

Not my place to comment on competitor issues.

tommybhoy said:
GW's are in the titles that are causing problems/delays, from it's inception it was highlighted/rubbished that it would/wouldn't give Nvidia the upper hand.

We certainly do recommend disabling GW's features and yes both of those titles are GW titles.

Ayahuasca · 21 Mar 2015 at 11:11

It's not a competitor issue, it works fine for them.

I'm asking why it is multi AMD card setups seem to have conflicts with a few titles or game engines.

LtMatt · 21 Mar 2015 at 11:17

Ayahuasca said:
It's not a competitor issue, it works fine for them.

I'm asking why it is multi AMD card setups seem to have conflicts with a few titles or game engines.

As i said, don't keep track of what works and what doesn't with our competitors.

Multi gpu is quite complicated and it comes down to many more factors than simply having a profile to enable it in the drivers.

shankly1985 · 21 Mar 2015 at 11:20

Two nvidia titles not working correctly on AMD shocker..
One from a developer known for its wide range of pc issues "ubisoft" even on nvidia yet amd is to blame? Lol

Man I don't know everything about driver profiles, but some you guys act like amd built the games and can bend fixes.

Most performance tweaks crossfire or frame rate issues are down to the development of the game this is not always an issue with driver amd/nvidia

Dying light another develop game from past games known for its pc issues, didn't dead island have issues with keyboards making game stutter forcing you to use a controller..

Superpatsy · 21 Mar 2015 at 11:24

** Please don't hotlink images **

tommybhoy · 21 Mar 2015 at 11:27

^
Lol, this,

and because sponsored titles usually have specific mgpu code written to support the sponsored cards generally from the off, with the competitor usually needing dev support to implement mgpu code which usually comes after release.

Common practice with endorsed titles, it was the same when the raft of GE titles released last year, nvidia had to play catch up too, short memories in the world of gpu's.

Final8y · 21 Mar 2015 at 11:33

tommybhoy said:
^
Lol, this,

and because sponsored titles usually have specific mgpu code written to support the sponsored cards generally from the off, with the competitor usually needing dev support to implement mgpu code which usually comes after release.

Common practice with endorsed titles, it was the same when the raft of GE titles released last year, nvidia had to play catch up too, short memories in the world of gpu's.

Indeed.

Gregster · 21 Mar 2015 at 11:39

This might get a few backs up but I have been biting my tongue for too long but why is every single problem everyone else's fault but not AMD's. Freesync monitors released too early and monitor manufacturers fault. GameWorks titles and never AMDs fault that they don't have crossfire profiles, even when they have been working with the devs. 144Hz not working on the swift because Asus didn't use an industry standard scaler. Christ, even AMD sponsored games like Alien and it was the devs fault for crossfire not working.

Rant over!!!

Final8y · 21 Mar 2015 at 11:41

@AMDMatt

Seeing as Freesync gives the option of Vsync On or Off outside of the Async range, there is less reason to not have the Vsync option available for DX in general for users as the Forced Vsync MS guidelines are already being broken

.

Just put the suggestion upstairs thanks.

Martini1991 · 21 Mar 2015 at 11:42

Gregster said:
This might get a few backs up but I have been biting my tongue for too long but why is every single problem everyone else's fault but not AMD's. Freesync monitors released too early and monitor manufacturers fault. GameWorks titles and never AMDs fault that they don't have crossfire profiles, even when they have been working with the devs. 144Hz not working on the swift because Asus didn't use an industry standard scaler. Christ, even AMD sponsored games like Alien and it was the devs fault for crossfire not working.

Rant over!!!

They didn't *really* release early though.