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 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-us/discussion/38131/directx-function-error-nvidia-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...

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! 🙂

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

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.

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.

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.

Hmm that makes sense, haven't seen the specs for the Mac Book (Been a lot of discussion recently of what it doesn't have though heh.) but a 470 or maybe the full 480 would probably work without AMD doing a different chip design specifically for that system. Might have added some additional refresh rates too: (Up to 100hz for 3840x2160, still not full 144 for those using such a display or 120 but still a improvement if it was 60 before.) https://www.reddit.com/r/Amd/comments/5803l0/new_driver_added_3840x2160_100hz_to_the_vsr_list/ https://www.reddit.com/r/Amd/comments/53za2z/apparently_amd_has_silently_increased_vsr/ (Added from one of the 16.9.x driver it seems going by when it was first reported.) Not really sure how the whole hardware side of this with VSR works (Scalar or what it was.) but there are updates for the Polaris GPU chip so supporting a higher resolution probably would be achievable unless it turns out it's just some adjustment entirely in the driver software as some have suspect since back when VSR could be modified a bit more easily even for older GPU models. EDIT: Reading the Reddit thread well for Fury and older GPU's AMD doesn't officially list 3840x2160 or 3840x2400 as available for a monitor using 2560x1440 or 2560x1600 (Instead it's 3200x1800 and 3200x2000 I believe.) but it is available or at least I can select 3840x2160 although GPU scaling has to be off in Crimson first (But the monitor already does scaling and can be customized a bit more so that's just a benefit.) (Still not a full 2.00x which would be 5120x2800 / 5120x3200 depending on if it's 16:9 2560x1440 or 16:10 2560x1600 and still no VSR support for ultra-wide 21:9 resolutions from what I've read.) (But 1.5x is still better than 1.25x and well "4K" as it's commonly called even if it's not a full 4096x resolution is certainly demanding enough particularly for newer games. 😀 ) (EDIT: Yeah it seems the "true" res would be 4096x2160)

Confirming that Idle bug still not fixed for GCN 1.0 users. I guess AMD will do one final release for December and fix this crap and say: on your way! It's been 2-3 months at least that this bug is present, we reported it, talk about it, but they don't care. * I just enabled secondary display through DVI and and left it for few minutes, disable it, and the clock of 450/1200MHz stays forever. It's really easy to trigger this bug it's kind of ridiculous.

Does anybody know if the Windows 10 64 bit crash/freeze on reboot/full shutdown bug is finally fixed in this driver with Radeon 7970Ms (and other mobile cards) on Alienware and other laptops or do we still have to use 16.7.2 which was the last driver this hasn't happened with?

Forza Horizon 3 working Very good on this one. I need to check MadMax Steam -> on WDDM 2.1 i have some bug on 16.10.x