That was fast

Nothing different with the atiapfxx.blb file in this driver compared to 16.10.2 so yeah new AMD Crimson Settings ("CNext") but that one seems to be on a daily build almost and a slightly newer display driver (October 25th instead of October 17th) with probably some unlisted changes and also this fix for Titanfall 2 and whatever GCN series GPU model it affected (400 series I guess?) useful if you play that game otherwise there's probably nothing too important in these drivers though yeah they do tend to do some unlisted fixing or tweaking too.

Thank you.

Thanks, gonna be trying it later.

Odd timing for not to mention Skyrim SE. I guess volumetric nvidia rays did make things difficult for AMD after all?

no mention of flickering fix for BF1 crossfire. LMAO AMD goes from strength to strength. Can't wait to leave this **** behind and get a big ass Green card that pisses all over AMD

nvidia's latest driver is whql and has all new games AMD HAS NOTHING hahahaha pathetic red disaster

hmm?

I wouldn't go that far. 🙂 Forza Horizon 3, Gears of War 4, Dishonored 2, Titanfall 2, Battlefield 1, Civilization 6, Mafia 3, Call of Duty: Infinite warfare and Obduction are all supported by profiles. It is missing a profile for SkyrimSE still though far as I can tell. EDIT: No profile for Wildlands yet it seems. (For Honor is supported though.) EDIT: Updated with some more recent releases I found profiles for, pretty sure Nvidia also supports most if not all of them too. (And as a single GPU user I can't really say how Crossfire is working or is not working, DX12 seems a bit of a "meh" so far overall but other than that it seems both AMD and Nvidia have their issues in various games.)

Nothing different with the atiapfxx.blb file in this driver compared to 16.10.2 so yeah new AMD Crimson Settings ("CNext") but that one seems to be on a daily build almost and a slightly newer display driver (October 25th instead of October 17th) with probably some unlisted changes and also this fix for Titanfall 2 and whatever GCN series GPU model it affected (400 series I guess?) useful if you play that game otherwise there's probably nothing too important in these drivers though yeah they do tend to do some unlisted fixing or tweaking too.

It's always the undocumented stuff that's the best 😀

Odd timing for not to mention Skyrim SE. I guess volumetric nvidia rays did make things difficult for AMD after all?

Most likely it uses the exact same profile as Fallout 4.

nvidia's latest driver is whql and has all new games AMD HAS NOTHING hahahaha pathetic red disaster

Amazing. That GTX 970 must have really been the better choice back then, what a disaster. (Which is the game that you actually have a problem on?)

It's always the undocumented stuff that's the best 😀 ...

Yeah, Kn00t maintained a very good overview of these profiles but I don't have the skill to dig into the actual .dll files where there's usually newer profiles before they get moved into the profile "blob" archive and there's probably other changes too but that's nothing new for either AMD or Nvidia, release notes are more of a highlight of important fixes and important known issues than a full build log or how to say over every change in said driver. 🙂 (Would probably be a bit too technical anyway to post something like that rather than these summaries of major changes, fixes or improvements.) (For one recent example from AMD they fixed a hardware acceleration graphical issue in Firefox in one of the 16.9.x drivers which was nowhere in the drivers release notes but mentioned on the Firefox bug tracker by a AMD employee confirming it had been found and fixed and then other posts below that confirming said fix working when the driver got released.) EDIT: As for driver issues and game support well short of actual bugs or display issues the main thing is generally multi-GPU support and getting good scaling going, DX12 moving it more to the developers rather than AMD or Nvidia and their drivers seems to have a bit of a mixed result while giving the developers the ability to take advantage of these low-level API functions it is probably a lot more work thus at least for the moment multi-GPU support with DirectX 12 is lagging behind a bit even for bigger releases and some games even planned to have support for DX12 had it implemented post-release instead and then multi-GPU implemented after that which is a unfortunate delay. (Granted DX12 isn't going to replace DX11 just yet but with AMD focusing more on D3D12 and Vulkan the CPU overhead issue with older API's will probably not be resolved.) Guessing once AMD and Nvidia's new GPU models start to appear and a more fully supported feature set for DirectX 12 (And Vulkan?) comes out adaption will speed up a bit further. 🙂 (But it won't replace DX11 anytime soon, both are intended to co-exist at least for now and both are updated.) EDIT: Besides game support there's also any potential issues with a new GPU model release from the Fury and it's display corruption problem to Wattman for AMD's recent 400 series, I don't have a good overview on how it is for Nvidia though. (There's the recent issue with overheating but that's a third-party model error and there's the occasional hardware issue that well a driver can help but it might need a bios update to stabilize it further.) (The black screen problem on some of the 290 GPU models for one example or the recent bios update for some third party 1070 GPU's I think it was using a certain memory chip?) EDIT: Anyways as for 16.10.3 I'm not noticing any issues so far, unsure which exact GCN GPU models that had that Titanfall 2 error but if 16.10.2 worked then 16.10.3 are probably going to be good too with not too much changed aside from this fix. (Nothing AMD found worth noting down in the release notes at least.) (Known issues are also identical to 16.10.2 thouh now with Raptr removed from the driver and AMD moving from supporting it I'm guessing that one is "resolved" of sorts aside from for those actually finding it useful and keeping it.)

It's always the undocumented stuff that's the best 😀 Most likely it uses the exact same profile as Fallout 4. \

Can confirm, Crossfire works with Fallout 4 profile, no noticeable flickering or some other 'bugs'.

It's always the undocumented stuff that's the best 😀

Let me guess, UVD clock bug is still there?!

Give me five hours and I'll report on that. 😛

nvidia's latest driver is whql and has all new games AMD HAS NOTHING hahahaha pathetic red disaster

Didn't I tell you to sell off your 390X and get a GTX 960?

Installed 16.10.3 so far idle bug is no present, but it's early with 16.10.1 happened the next day...and they produced few bsod's. So, so far so good but I will definitely report later.

Bleh, I could trigger the idle UVD bug on first try as always. I'll send another report. It's really driver related, as 16.7.2 doesn't trigger it by doing the same.

I submitted again also. God damn it AMD.

Bleh, I could trigger the idle UVD bug on first try as always. I'll send another report. It's really driver related, as 16.7.2 doesn't trigger it by doing the same.

What exactly is this UVD bug? I've been seeing it mentioned regularly for the last few years but I have yet to see a clear explanation of exactly what it is. My HD7870 and HD7950 both always appeared to function properly. So far, my RX 470 appears to be functioning as expected.

It's circumstance where the card gets locked at UVD clocks, and only uses the lowest UVD in idle (without anything 3D accelerated running), and only its highest UVD clock for higher loads such as 3D (meaning no boost clock for models that have it). It can be triggered for some users while having something running that sets the card in UVD clocks such as a browser and then playing a video with hw accel. After closing everything, the card will be stuck in UVD mode. This probably means idle at 450/1200 on your 7870 and 501/1250 on your HD7950 instead of 300/150 which can mean >30W, and no applied OC via soft (if they are non-boost models, the highest UVD clock will match the stock 3D one).

I just used DDU to uninstall 16.10.2 and install 16.10.3. I still can't crossfire to work with my 2x 290x and Battlefield 1. Anyone else have luck?

Bleh, I could trigger the idle UVD bug on first try as always. I'll send another report. It's really driver related, as 16.7.2 doesn't trigger it by doing the same.

Tell me exactly how you trigger the bug and version of software that you use. And do you have more than one displays connected?