The AMD Driver Thread

shankly1985 · 29 Jan 2016 at 14:24

thebennyboy said:
10 minutes into Rise of the Tomb Raider and i get a driver crash.

Played over one hour last night no issues too report..
Any overclocking on the GPU? If so maybe tomb raider is pushing the GPU much harder, it is a very demanding game.

thebennyboy · 29 Jan 2016 at 14:29

shankly1985 said:
Played over one hour last night no issues too report..
Any overclocking on the GPU? If so maybe tomb raider is pushing the GPU much harder, it is a very demanding game.

There is yes, however this overclock is stable in EVERY other game i've played. I've just given it some more voltage and it's still crashing at the exact same cutscene.

TheRealDeal · 29 Jan 2016 at 14:29

If those techpower benchmarks are giving the proper performance then all those other sites giving out fake results should update with the proper release build.

Dave2150 · 29 Jan 2016 at 14:47

thebennyboy said:
There is yes, however this overclock is stable in EVERY other game i've played. I've just given it some more voltage and it's still crashing at the exact same cutscene.

Obviously try it at stock before reporting problems. It might be the only game that taxes your GPU in a certain way to make it crash, due to your overclock.

fs123 · 29 Jan 2016 at 14:57

AMDMatt said:
Nice, that must be on 16.1.

Update on the next driver.

The TPU results seem about right. Hopefully the drivers will give a boost like they did with Fallout 4. Any chance of crossfire for Fallout 4 btw?

Dygaza · 29 Jan 2016 at 15:01

nashathedog said:
I've got the overclocked Fury tri-x which has a box clock of 1040mhz. I run the card at 1050mhz via Afterburner to try and avoid downclocking and according to gpu-z my Fury runs Rise of the Tomb Raider at a consistent 1050mhz. I did a 45 minute play and it didn't budge. But performance is poor. I'm running at 1440 via vsr on a 1080p screen, I have a stock clock 4790k with it yet with lots of setting turned down or off it still rarely hits 60 and often sits in the high 30's, low 40's.

It's very disappointing especially seeing as it was implied we would get a driver update which we would obviously expect to solve any such problems.

What was the gpu usage. 1050MHz @ 50% equals 525MHz @ 100% (well almost atleast, as you truly can't tell how much shaders are used/unused)

TheRealDeal · 29 Jan 2016 at 15:08

nashathedog said:
I've got the overclocked Fury tri-x which has a box clock of 1040mhz. I run the card at 1050mhz via Afterburner to try and avoid downclocking and according to gpu-z my Fury runs Rise of the Tomb Raider at a consistent 1050mhz. I did a 45 minute play and it didn't budge. But performance is poor. I'm running at 1440 via vsr on a 1080p screen, I have a stock clock 4790k with it yet with lots of setting turned down or off it still rarely hits 60 and often sits in the high 30's, low 40's.

It's very disappointing especially seeing as it was implied we would get a driver update which we would obviously expect to solve any such problems.

Run it at 1080p as 1440p performance all around does not look to be great. Check out those tpu results and they are not running it maxed either. I assume it's the 16.1 hotfix drivers you are using.

BluD · 29 Jan 2016 at 15:40

AMDMatt said:
Nice, that must be on 16.1.

Update on the next driver.

Cool, gonna hang on till its out, game looks great on one 290 but if the hotfix allows for further cranking then may aswell wait.

Spook187 · 29 Jan 2016 at 15:49

jamiehard1989 said:
Still working on the driver.

One of the biggest games of the year and they messed up yet again, reps know nothing posting the links we already had.

TheRealDeal · 29 Jan 2016 at 15:54

Spook187 said:
One of the biggest games of the year and they messed up yet again, reps know nothing posting the links we already had.

Well if Tpu results are to be believed performance is fine on the release build comparing to Nvidia's. The new driver might just fix a few bugs as the performance is just about in line with what would be expected.

It does nothing for there rep though. They should have just released 16.1 as 16.1.1 game ready driver and everyone would have been happy. They then could have released 16.2 in a few days and said there was more fixes for tomb raider and everything would have been Rosy. Might have even received a pat on the back for the deceit

.

Confused Stu · 29 Jan 2016 at 15:55

Spook187 said:
One of the biggest games of the year and they messed up yet again, reps know nothing posting the links we already had.

Who are you defining as "they"? Are we squarely blaming AMD when we have no clue what's happened behind the scenes? I remember previous game launches where AMD could not get hold of the game until they actually bought a copy like a normal person, and others where last minute changes by the developer pre-launch broke all the work AMD had done beforehand. We have no idea if AMD have dropped the ball and could have had this driver done days ago, or if they've been kept in the dark by others and have only just been able to start work on it, or what's happened.

Whatever the reason, I think it's unacceptable that massive companies cannot communicate successfully to produce a seamless experience for the player on game releases, but I'm not happy laying the blame at anyone's feet until we know what's happened and who actually is to blame.

meldarthx · 29 Jan 2016 at 16:01

Confused Stu said:
Who are you defining as "they"? Are we squarely blaming AMD when we have no clue what's happened behind the scenes? I remember previous game launches where AMD could not get hold of the game until they actually bought a copy like a normal person, and others where last minute changes by the developer pre-launch broke all the work AMD had done beforehand. We have no idea if AMD have dropped the ball and could have had this driver done days ago, or if they've been kept in the dark by others and have only just been able to start work on it, or what's happened.

Whatever the reason, I think it's unacceptable that massive companies cannot communicate successfully to produce a seamless experience for the player on game releases, but I'm not happy laying the blame at anyone's feet until we know what's happened and who actually is to blame.

This.....

Also I've played 45 minutes - 15.11.1s or 12.1s with catalist over crimson as some reason crimson doesn't like my system. Everything smooth; I've got 30 minute video I'll post soon. I'll get fps up on next one.

I don't use afterburner anymore as it was causing too many crashes in games.

LoadsaMoney · 29 Jan 2016 at 16:14

jamiehard1989 said:
Still working on the driver.

Been updated, will also include Xfire support.

ICDP · 29 Jan 2016 at 17:11

Confused Stu said:
Who are you defining as "they"? Are we squarely blaming AMD when we have no clue what's happened behind the scenes? I remember previous game launches where AMD could not get hold of the game until they actually bought a copy like a normal person, and others where last minute changes by the developer pre-launch broke all the work AMD had done beforehand. We have no idea if AMD have dropped the ball and could have had this driver done days ago, or if they've been kept in the dark by others and have only just been able to start work on it, or what's happened.

Whatever the reason, I think it's unacceptable that massive companies cannot communicate successfully to produce a seamless experience for the player on game releases, but I'm not happy laying the blame at anyone's feet until we know what's happened and who actually is to blame.

Then AMD should tell us this rather than implying through winky icons that a driver will be ready on release day.

Confused Stu · 29 Jan 2016 at 17:27

ICDP said:
Then AMD should tell us this rather than implying through winky icons that a driver will be ready on release day.

Agreed - I'm definitely also in favour of more communication (even if plans later change) than less.

nashathedog · 29 Jan 2016 at 17:49

thebennyboy said:
There is yes, however this overclock is stable in EVERY other game i've played. I've just given it some more voltage and it's still crashing at the exact same cutscene.

I've experienced 3 cut scene crashes so far.

nashathedog · 29 Jan 2016 at 17:53

Confused Stu said:
Who are you defining as "they"? Are we squarely blaming AMD when we have no clue what's happened behind the scenes? I remember previous game launches where AMD could not get hold of the game until they actually bought a copy like a normal person, and others where last minute changes by the developer pre-launch broke all the work AMD had done beforehand. We have no idea if AMD have dropped the ball and could have had this driver done days ago, or if they've been kept in the dark by others and have only just been able to start work on it, or what's happened.

Whatever the reason, I think it's unacceptable that massive companies cannot communicate successfully to produce a seamless experience for the player on game releases, but I'm not happy laying the blame at anyone's feet until we know what's happened and who actually is to blame.

Maybe so but if we are not kept in the loop so speak and do not know why we lack the support we should be getting there is one obvious target for peoples anger.

After all AMD had plenty of involvement in the game and should have ensured that the pc version wouldn't be taken out of there hands and busterdized like it appears to have been with major changes like removing async and whatever else has been changed.

ltron · 29 Jan 2016 at 18:05

nashathedog said:
Maybe so but if we are not kept in the loop so speak and do not know why we lack the support we should be getting there is one obvious target for peoples anger.

After all AMD had plenty of involvement in the game and should have ensured that the pc version wouldn't be taken out of there hands and busterdized like it appears to have been with major changes like removing async and whatever else has been changed.

I agree with everything you just said. I think that given what we know about AMD and DX12/Vulkan, that it's not unreasonable to conclude that DX12 and Async Compute would speed up this game massively on AMD GPUs.

Square Enix/Nixxes' statement about how they couldn't get DX12 to run faster than DX11 seems to only hold true in Nvidia's case (from past benchmarks such as Ashes of the Singularity) and is the same sort of thing the ARK:Survival Evolved(Another Nvidia game) developers said regarding their DX12 patch that never materialised. Even if Nvidia did get a slight benefit from DX12, AMD could get a much greater benefit and Nvidia obviously don't want that.

To me, it seems very likely the situation is as I've described. I am disappointed that AMD have not been more proactive in countering this. I just hope Hitman and Deus Ex:Mankind Divided do not meet a similar fate.

nashathedog · 29 Jan 2016 at 19:01

ltron said:
I am disappointed that AMD have not been more proactive in countering this. I just hope Hitman and Deus Ex:Mankind Divided do not meet a similar fate.

It is disappointing but it is also understandable in a way cause at the end of the day money talks and Nvidia are currently in a position to shout the loudest.

It's a sad situation and even those who do not recognise that now will do eventually. Over the long term it'll be bad for everyone not just AMD users.

ltron · 29 Jan 2016 at 19:43

This might help fellow AMD users with Rise of the Tomb Raider:
I've just been testing this game with my R9 390X and I noticed something very unusual. Reducing Anisotropic filtering from 16x to 2x gave me 10-15 FPS extra in both the snow level and Syria, no other setting gives me anywhere near the same increase. Can anyone else confirm?