Downclocking during VR with 2018 drivers

[xkm1948]

As titles says I am once again having problems with AMD's driver on VR. On 2D monitor gaming everything is fine. However in VR, especially during game initial loading or application loading the driver will force the GPU down-clock to ~400MHz. This results in horrible jittering whenever I launch a new VR application and it usually won't go away until ~30 seconds later. This results in terrible nausea. It was bad enough that FuryX do not have Async Reprojection. WIth these new drivers I cannot even have some very basic VR experience at all.

Needless to say I have to congrat AMD's driver team on f*cking up VR experience once again. Guess mining is all their focus now. Submitted a ticket last Tuesday and have not heard anything back. Will post on their community forum as well.

Meanwhile I am exploring other options to prevent the down-clocking. Would running the GPU-Z rendering window keep the GPU from downclocking?

edit: Kinda funny that the Crimson drivers around November 2017 had the exact opposite problem. It was locking GPU to full speed even after SteamVR is closed. Guess they did fix that problem, just fixed it too much.

 

[fullinfusion]

As titles says I am once again having problems with AMD's driver on VR. On 2D monitor gaming everything is fine. However in VR, especially during game initial loading or application loading the driver will force the GPU down-clock to ~400MHz. This results in horrible jittering whenever I launch a new VR application and it usually won't go away until ~30 seconds later. This results in terrible nausea. It was bad enough that FuryX do not have Async Reprojection. WIth these new drivers I cannot even have some very basic VR experience at all.

Needless to say I have to congrat AMD's driver team on f*cking up VR experience once again. Guess mining is all their focus now. Submitted a ticket last Tuesday and have not heard anything back. Will post on their community forum as well.

Meanwhile I am exploring other options to prevent the down-clocking. Would running the GPU-Z rendering window keep the GPU from downclocking?

edit: Kinda funny that the Crimson drivers around November 2017 had the exact opposite problem. It was locking GPU to full speed even after SteamVR is closed. Guess they did fix that problem, just fixed it too much.

You know what man!

I and ford try and help you, and you turn around and say AMD Driver Team keep fukn things up... you know that's insulting me and the others from being able to help you out..

We're the ones that fix shit, you do know that right? We spend many hours looking on Reddit and other sites for complaints so we may replicate issues and fix them for the consumer!

I asked you to join Vanguard a few times and you always turn us down... Why?

Anyways... Here I'm posting to Vanguard your posts AGAIN and I was told by fellow Fury X owners to ditch MSI AB as it fuks with clocks...

Join us as I can get you in and then YOU CAN HELP RESOLVE THESE ISSUES...

 

[xkm1948]

See the missed frame, nasuea induction festival.

Also pay attention to the GPU core clock during VR. only sit at 638MHz instead of where it should be: 1050MHz

@fullinfusion I will join! Regular pipeline does not seem to be able to fix these driver problems for me now.

 

[Flyordie]

*snipped pics*

See the missed frame, nasuea induction festival.

Also pay attention to the GPU core clock during VR. only sit at 638MHz instead of where it should be: 1050MHz

@fullinfusion I will join! Regular pipeline does not seem to be able to fix these driver problems for me now.

I've run into a similar issue with my RX Vega64 BUT its not with VR and I don't use external clocking apps. It doesn't affect me though as I can still push 60FPS+ @ 1200-1300Mhz on BF1.

It could be a Radeon Chill thing being wonky or the driver throttles back when load is low?

I have it set to 1762Mhz in Wattman. It'll hold that for F@H, GPU-Z window etc.. but gaming it fluctuates between 1100-1300Mhz. HBM2 jumps around also. 500Mhz then 1000Mhz.. up and down constantly during the game.

(Its only done this since December's updates)

Temporary fix I've found to work for me-

Set Min/Max the same in Wattman. . Clocks hold and it doesn't downclock. (but it does increase power usage considerably if your GPU doesn't need to run at that speed to deliver required performance) It still downclocks when idle however.

 

[xkm1948]

I've run into a similar issue with my RX Vega64 BUT its not with VR and I don't use external clocking apps. It doesn't affect me though as I can still push 60FPS+ @ 1200-1300Mhz on BF1.

It could be a Radeon Chill thing being wonky or the driver throttles back when load is low?

I have it set to 1762Mhz in Wattman. It'll hold that for F@H, GPU-Z window etc.. but gaming it fluctuates between 1100-1300Mhz. HBM2 jumps around also. 500Mhz then 1000Mhz.. up and down constantly during the game.

(Its only done this since December's updates)

Temporary fix I've found to work for me-

Set Min/Max the same in Wattman. . Clocks hold and it doesn't downclock. (but it does increase power usage considerably if your GPU doesn't need to run at that speed to deliver required performance) It still downclocks when idle however.

Does reversing to pre adrenaline driver helps?

 

[Flyordie]

Does reversing to pre adrenaline driver helps?

It didn't happen as much. BUT it could be the progression of the drivers efficiency. My GPU load has dropped as drivers have progressed.

Personally, I'd try setting min/max as P7 and see if that locks it in place.


The biggest issue I wish the driver team would figure out is the BF1 screen tint bug permanently.

 

[xkm1948]

Still not fixed. Submited tickets to AMD twice and no response. Guess they don't give a f*uck about VR any more.

Welp really need to save up to switch to nvidia now.

 

[xkm1948]

AMD tech support told me their driver team replicated my problem. So they are finally actively working on resolving it now. Hopefully it got fixed in the future. Or at least it will appear in the "known issue"

 

[Vya Domus]

It could be a Radeon Chill thing being wonky or the driver throttles back when load is low?

To be honest it most likely has to do with that 8320 you have. AMD drivers are notorious for relying a lot on single thread performance , not a strong point of FX processors. Not to mention you have the fastest AMD card out there , a really unfortunate combination.

 

[Flyordie]

To be honest it most likely has to do with that 8320 you have. AMD drivers are notorious for relying a lot on single thread performance , not a strong point of FX processors. Not to mention you have the fastest AMD card out there , a really unfortunate combination.

On DX11 mode, yes. DX12, BF1 is using all 8 threads to 40-70%. While gaming I crank the clocks up to 5.2Ghz too so its not a real bad bottleneck. The only reason I have an RX Vega is the price was to good to pass up. $525 for an XFX RX Vega64 Liquid card at Best Buy. In September 2017... BNIB, never opened. Yea, I jumped on it. Even came with WolfII and Prey.