Radeon Software Crimson Edition 16.11.2 Download & Discussion

What is going on here?

 

Performance Boost Drivers !

Thank you for the heads up HH , it's raining AMD drivers daily . Good drivers , no problems to report so far. 290x @ W10 Pro x64bit. Tested on NFS 2016 , Bioshock Remastered , Bioshock 2 Remasterd and Bioshock Infinite.

I was using old 16.9.2 , with this new set of drivers 16.11.2 i got a bump in performance in the games i play mostly NFS 2016 , i guess they are optimizations for BF1 that uses the same frostbyte engine as NFS 2016 and hence why the nice boost in performance or maybe that larger shader cache is helping a lot. Great performance boost drivers. Highly Recommended :thumbup:

 

The improved shader cache sounds nice, but has anyone encountered this issue?

"Battlefield™1 may experience an intermittent application specific error message popup citing graphics device removal"

 

the dx problems with bf1 are multifacetted.
they are not solely driver problems.

the issue you are talking about is already "investigated" by DICE devs:

https://forums.battlefield.com/en-u...still-no-fix-update-please-4-11-16-14-59-cest

as stated by the ea "community manager" in the thread.


so what's happening is

- you have the problems with VRAM management in dx11.

- you have issues issues occurring because of the totally normal higher VRAM usage in DX12

- you have crashes with the "DXGI_***device_hung...removedreason..." error

- you have a certain type of surface flickering which only occurs in CFX/SLI
(which btw is not completely fixed by the 16.11.1 for amd, will test .2 later)

- you have another type of surface flickering on certain maps (i.e. amiens, BB) independently of the amount of cards you use


yeah and as you know the internet ... all these problems are getting mixed up. fixes for one problem are propagated as fixes for the others... etc...

we still have to wait for DICE, AMD and NV to sort this stuff out.

 

I don't think this issue is regarding the DX problems, though...

 

it is exactly the mentioned/linked issue.

i was just saying that there are multiple issues that shouldnt be mixed up as well!

 

Nice, guessing this makes it so the cache files don't cap at 64 MB anymore, I usually don't see them ever going above 32 (8, 16, 32, 64 I think it goes.) but this might be useful
(128 I'm guessing but perhaps 256 although I don't see a game ever having that much shader data but what do I know, might be more in those caches than just compiled shader code.)

EDIT: Ah no it starts at 64kb and then doubles from there up to 64 MB or well the previous limit was 64, 128 is what I would guess at for the new cap but it could be higher than that.

 

lol. just installed version 16.11.1, okay, now let's try this one.

 

All good on my 480.

 

Madness.
I already installed 16.11.1 and now THIS! Time to update the driver.

GG RTG!

 

new drivers + install ok + all my games ok. (r9 280x)

And I try :

COD MW remastered = perfect, no problem + performance are very good.

COD Infinite War = game crash after 2 minutes, direct back to windows + drivers lost/failed (!!!! last see this message is +10 years old)

Try to play with LOW quality = same problem...
time for waiting new patch/drivers

 

My last driver was 16.10.3 and battlefield 1 works fine with it.
After installing this driver .. i got directx crash error for the FIRST TIME,
and keep getting it every single round.
WTF......

 

for me too with furyx, 16.10.3 rock solid, 16.11.1 disaster (stutter, dxgi error), 16.11.2 less disaster (initial stutter, random dxgi error).

 

Then i will back to 16.10.3 .. till AMD solves this known issue.

 

edit: delete

 

reverted to 16.10.3.. first match... on the loading dxgi error LOL.

restarted the game, i have played for about 1 hour without error or crash... smooth.

 

Will report idle bug when the form's GUI is updated. It only shows 16.11.1 for now.
There might be a chance that the "H.264 content playback(...) note is somehow related.

 

Looks like AMD altered "VSR" for the 400 series a couple of driver releases back so it goes up to 5120x2880 now, still capped at 3840x2160 for the 300 series and Fury though.

 

Interesting. That would fit the theory that the Polaris chip in the new Macbooks that can drive 5k screens, is actually not custom silicon, as a lot of Apple fans wanted to believe.