Driver AMD 16.5.2.1(shader very nice)causes heavy stuttering

[HaagseSmurf]

After updating my old AMD videodriver 16.3.2 with a clean-install to the newest AMD driver 16.5.2 i got lots of heavy stuttering in game and huge fps-drop. It reminded me of the issue we had before after updating to WIN-10 Extreme lag in Windows 10 [BUG]
The same fps-drop and heavy stuttering appeared.
So i would advice people to be aware of that issue with the newest AMD driver !

I went back to my previous driver (clean installed as well) and the stuttering was gone.

My specs are:
CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
GPU: AMD R9 290 (4gb ddr5)
MEM: 16gb ddr3
OS: Windows 10

[TMarc]

Hej Haagse,

did you delete your Defaul.SystemConfig.Gbx file to let the game create it again?
I suspect this file contains some "links" to video driver stuff, and having an outdated config file, not matching to the drivers, might cause such issues as well.

[HaagseSmurf]

I think thats irrelevant, otherwise i had this issue before at each update. And thats not the case. As you could see i had the 15.7.1 in that other topic and there were several other updates since that version. So imo its related to the AMD update and not to any other "conflicting" file.

Greetz

[HaagseSmurf]

Today AMD released a 16.5.2.1 hotfix version which i will test tonight.
https://www2.ati.com/drivers/beta/non-w ... -may16.exe

Greetz,

[undef.de]

Just installed the 16.5.2.1 and tried MP in Stadium and Canyon: All fine for me... but my Specs are a little bit different.

[HaagseSmurf]

Okay here the complete test
Compared the AMD 16.3.2 and the 16.5.2.1 (still bugged for me) in the same shootmaniamap (MX 2986)
The Windows 10 BUG was mainly caused for me in the shader-settings: see also:Extreme lag in Windows 10 [BUG]
So i tried to compare both drivers with the shader-settings nice and very nice in that same SM-map.

16.3.2 Shadersetting Very nice: avg 120 FPS
16.3.2 Shadersetting Nice: avg 140 FPS

16.5.2.1 Shadersettings Very nice: avg 60 FPS (heavy FPS-drops and stuttering)
16.5.2.1 Shadersettings Nice: avg 140 FPS

I also compared the DX9-callbacks from the debugged version (as mentioned by Willa in the Win10 topic before)
16.5.2.1 Shadersettings Nice

Code: Select all

Line 1050: [Dx9] We've computed 1 269Mb alloc, 2 837Mb free, 1 813Mb gpu free.
Line 1051: [Dx9] 386 Textures wanting 1 224Mb, 0 Surfaces using 0Mb, 1 224Mb actually allocated.
Line 1052: [Dx9] Vertexs+Indexs used: 19Mb (77% of vertexs, 747 vBuffs + 1 300 iBuffs)
Line 1053: [Dx9] Vertexs_Packed : 0Mb (0%)
Line 1054: [Dx9] Vertexs_Sprites: 1Mb (3%)
Line 1055: [Dx9] 98 Overlay Textures using 110Mb.

16.5.2.1 Shadersettings Very Nice

Code: Select all

Line 1214: [Dx9] We've computed 1 648Mb alloc, 2 458Mb free, 1 434Mb gpu free.
Line 1215: [Dx9] 433 Textures wanting 1 601Mb, 0 Surfaces using 0Mb, 1 601Mb actually allocated.
Line 1216: [Dx9] Vertexs+Indexs used: 21Mb (79% of vertexs, 766 vBuffs + 1 301 iBuffs)
Line 1217: [Dx9] Vertexs_Packed : 0Mb (0%)
Line 1218: [Dx9] Vertexs_Sprites: 1Mb (3%)
Line 1219: [Dx9] 102 Overlay Textures using 110Mb.

My other specs are:
CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
GPU: AMD R9 290 (4gb ddr5)
MEM: 16gb ddr3
OS: Windows 10

[TheBigG.]

just as tip, never use shader settings different than fast, else you can't enable antialiasing.

[jinxy587]

As you know i have exactly the same problem with both of the 2 recent AMD drivers, have you tried as said deleting that
file.j

[HaagseSmurf]

As you know i have exactly the same problem with both of the 2 recent AMD drivers, have you tried as said deleting that
file.j

I tried, but as expected, it didnt work . Its still something with AMD and Win10 related to DX9 which causes this issue imo.
Perhaps an interesting topic about the performance of AMD for DX9 in WIN 10:
https://community.amd.com/message/27200 ... nt-2720043

Greetz,