Discussion in 'Videocards - AMD Radeon Drivers Section' started by mtrai, Oct 5, 2016.
They used 16.9.2 though.
Yeah this one is more accurate (The 16.10.1 drivers are good for GoW4)
I think all GPUs performs very good in here
Wow, GTX 980Ti Hybrid is on the same perf. level with GTX 1080 Hybrid?
That test is a joke
It can be, at 1080p running the game at 155 FPS CPU limit is pretty much "achievable" so the 980 Ti/1080 will be limited. The game's benchmark also reports CPU FPS and the percentage of GPU bound. The PCWorld benchmark shows that even an Intel i7-5960X is capable to output "only" 156 FPS at 1080p (more likely the game still can't use all the available threads effectively): http://www.pcworld.com/article/3128346/software-games/tested-gears-of-wars-4-pc-benchmarks-yield-glorious-graphics-options-galore.html
The only issues I have are some 2D flickering in Kodi, when I use the (hacked) MadVR player with it. No crashes there. The idle bug is more and more rare, I haven't triggered it the last week (I think). The only issue is with some older DX9.0 games or injectors like ENB, and that's mainly a WDDM 2.1 problem, as far as I understand. If your system crashes under load, you have hardware issues.
PRMinisterGR, you're wasting time on preaching to a guy who spent tons of money on a HD 7970 by replacing the stock fan and thermal pads with a GTX 970 fan that works at a higher RPM and copper shims, respectively so he could achieve 1100 MHz on the core without throttling but apparently has never heard of PowerTune, or the simple fact that all chips can't OC like hell and finally found peace after switching over to a GTX 970 that performs eons better than his previously owned HD 7970. Does this all mean something? :infinity:
And some people confuse a failing hardware with a software issue. Maybe their cards got a fixed bios issued by the manufacturer or something but instead of trying to see if that exists they look for ways to blame AMD because it's the easier of the two. I admit the drivers are far from flawless, but some people just can't seem to grasp that the issue could be something else other than the drivers itself.
Link to rant: forums.guru3d.com/showpost.php?p=5319086&postcount=29
No crossfire profile for Fifa 17?
Well tomorrow will be a good day for me. Will download this driver first thing in the morning before I grab my Mafia 3 pre order. I'm sure a lot of us will be stuck deep in this game by this time tomorrow.
Doom is using 1.0.26 Vulcan SDK in this driver. Game runs amazing :
FYI the gamer nexus test is bogus and it is being re-done
Somehow I missed this post of yours. As I have said, you don't understand how this industry works. I have said this in my local forums, and I'm saying it again, *********** is biased and unreliable. But hey, the numbers he posted very well be true for your rig though. AMD sucks because your tiny APU can't feed it fast enough, right? You really should sell off your 390 and get a GTX 970 like the other guy who failed to overclock his HD 7970 to 1100 MHz did.
Edit: Roflmao apparently that site's name gets filtered in this forum. Just goes to show...
It always does with Vulcan
No more crashes!!
Here it is very stable, but I do not play Rainbow Six Siege...
Now the madVR crash is fixed.
With this driver Photoshop "Select and Mask" does not crash anymore...
You're losing your breath, I have a feeling.
I'm waiting for Cookieboyeli's reply.
I hope if Vulkan does pick up steam it gets released like Doom, its amazing how good it is.
additionally... this: Test issues GOW 4
shamed be he who thinks evil of it...
I hope it's a good news been testing these ones on Windows 7 today and so far no bugs at all, even idle bug seems to be resolved...will see tomorrow in Windows 10. I didn't used DDU, just AMD uninstall all went just fine. I can just hope that is not same thing like with 16.9s they worked 1 day fine next day crap. Will report...
If you refer at clocks not going to ULPS after use of DXVA, then I wont bother to download new drivers and its not just idle clock. In my case, boost clock doesnt work either and on top of that, whole clock control is bugged and doesnt work at all.
You can restart driver to fix it, or in my case (and friends case with 280x tahiti) 16.7.2 driver.
By completely ignoring this issue (not even mentioning in known issues) they wont sell new cards to pitcairn/tahiti users for sure (probably whole 1st GCN gen)