SteamVR with RTX 5080 stuttering/dropped frames

[Conde Spark]

Hi everybody!
I was one of the luckyest to obtain a 5080 at launch day, but my lucky did not last to long.
Since I changed my GPU from 3070 to 5080, in VR the stuttering/Frame skip/Purple spikes/Dropped Frames are horrendous.
I dont know if is due to the driver version (572.16) and we need to wait, or is the windows 11 version (24H2) or the **** weather affecting my 1200€ card.
All the possible solution I tried are:

• Disabling all RGB software.
  
• Clean install with DDU of the drivers.
  
• Disabling Hardware accelerated graphics scheduling.
  
• Disabling any performance software capturer, like fpsVR, afterburner, nvidia overlay...
  
• Enabling/disabling AMD EXPO, and any posible overclock and undervolt in the MB.
  
• Disabling SteamVR Home.
  
• Uninstalling any Audio driver.

None worked. Any person has the same experience or any information or extra solution??
This is the same post but in reddit with an image of fpsVR capturing the stuttering: Post in Reddit
Thanks!

Ryzen 7 9800X3D
64gb ddr5 6000Mhz
RTX 5080
X870 gaming plus wifi
m2 samsung 990 pro

[2⊛2]

Thanks that you share your informations about new hardware like 5080 but the correct place to get support shouldn´t be the Steam users instead the the manufacture of your Beta-Hardware.
Post to Nvidia or wait for new drivers.
In a review yesterday i did see that the 5080 have much problems with older games.
Like usual on a launch of new hardware espacially grafic-adapter. All manufactures like AMD Intel Nvidia are need time to fix the errata.

And thanks for Beta-Testers like you. Community needs guys like you who spends much money for broken hardware.

[kH]

Originally posted by 2⊛2:

Thanks that you share your informations about new hardware like 5080 but the correct place to get support shouldn´t be the Steam users instead the the manufacture of your Beta-Hardware.
Post to Nvidia or wait for new drivers.
In a review yesterday i did see that the 5080 have much problems with older games.
Like usual on a launch of new hardware espacially grafic-adapter. All manufactures like AMD Intel Nvidia are need time to fix the errata.

And thanks for Beta-Testers like you. Community needs guys like you who spends much money for broken hardware.

bro what

[2⊛2]

Did you ask Nvidia if they could solve your problem ?
5080 is new hardware, why do you guess that anyone knows here a solution ? It is the Steam-Forum, not Nvidia.

[kH]

Originally posted by 2⊛2:

Did you ask Nvidia if they could solve your problem ?
5080 is new hardware, why do you guess that anyone knows here a solution ? It is the Steam-Forum, not Nvidia.

I've never seen someone so mad that someone has a better graphics card than them

[Conde Spark]

Originally posted by 2⊛2:

Thanks that you share your informations about new hardware like 5080 but the correct place to get support shouldn´t be the Steam users instead the the manufacture of your Beta-Hardware.
Post to Nvidia or wait for new drivers.
In a review yesterday i did see that the 5080 have much problems with older games.
Like usual on a launch of new hardware espacially grafic-adapter. All manufactures like AMD Intel Nvidia are need time to fix the errata.

And thanks for Beta-Testers like you. Community needs guys like you who spends much money for broken hardware.

Originally posted by 2⊛2:

Did you ask Nvidia if they could solve your problem ?
5080 is new hardware, why do you guess that anyone knows here a solution ? It is the Steam-Forum, not Nvidia.

Bro thinks he is the main character :O :O

[2⊛2]

Heard that the actual driver for 5080 is broken. Maybe the next driver will fix all.
Early Adopter´s Curse.

[Bob Loblaw]

Your resolution of 2468x2744 should not be a problem for a card of that power, and the GPU frametime (average?) of 2.8ms is quite good. (is that reprojection ratio reported wrong - doesn't look like 31% on the graph). The regularly spaced spikes suggest to me the GPU is tripping over itself when it gets a polling request about something like temp or fan speed. A very common problem on previous GPUs was once-a-second stutters from GPU temp monitoring software. There was even one case of a third-party AIB maker putting a fancy temp readout display on the card, which used the problematic software hooks to get temperature, and conflicted with SteamVR in the same way. There were cases of RGB traffic causing similar issues.

I'd suggest disabling everything that monitors GPU temp or fan speed or anything else, and disabling all RGB on the GPU (if any), and re-test.

Not directly related to your case, but If you want to learn how nvidia is currently being selfish and dumb with their performance monitoring, start at 12:50 in this video:
https://www.youtube.com/watch?v=Nh1FHR9fkJk

Prior confirmed causes of stutter in the forums:
1) Resolution set too high
2) USB congestion from lighting apps like Asus Aura, Corsair iCUE, Gigabyte RGB Fusion, TT RGB Plus

2b) USB congestion from a webcam ( https://steamcommunity.com/app/250820/discussions/0/3723945543089828606/ )

3) GPU monitoring apps like Afterburner, Aorus Edge View (once a second one-frame stutter) ( https://steamcommunity.com/app/250820/discussions/2/3381662461615185982/?tscn=1662951659 ), also SteamVR's GPU monitoring ( https://steamcommunity.com/app/250820/discussions/2/4411920671411791425/?tscn=1719585881 )
3b) disable razer cortex, a gaming "optimization" app ( https://steamcommunity.com/app/250820/discussions/0/5371139102170147464/ )

4) NVMe drive stealing bandwidth from the GPU's PCIE bus (here's an archived link to this deleted thread https://web.archive.org/web/20221129043940/https://steamcommunity.com/discussions/forum/11/1815422173043032484/ )
5) PCI-e 4.0 and USB conflict (also causes intermittent tracking loss) (change BIOS to use PCI-e 3.0 protocol)
6) Rift S + open OVR Advanced Settings ( https://steamcommunity.com/app/250820/discussions/0/3112519935867753855/ )
7) This huge thread on amd cards/drivers/chaperone/motion smoothing, etc, possible causes AMD ReLive for VR (Wireless), High Precision Event Timer, ( https://steamcommunity.com/app/250820/discussions/0/2970650017901586073/ ) It can be your nvidia driver also ( https://steamcommunity.com/app/250820/discussions/2/3781373416983040459/?tscn=1678668390 )
8) minimize game desktop window ( https://steamcommunity.com/app/250820/discussions/2/3058490685012602825/ ) (win 11/4070ti https://steamcommunity.com/app/250820/discussions/0/3781373416979903352/ )
9) Windows 11 wrong window focus (try the game window or SteamVR control panel)
10) Wrong OpenXR runtime setting (SteamVR, Oculus, WMR) (oculus example https://steamcommunity.com/app/250820/discussions/2/6406956248970801032/ )
11) Multiple monitors at different refresh rates (see also #22). Test with just one, at 60. ( https://steamcommunity.com/app/250820/discussions/0/6406956248963113090/ )

12) Windows 11 stop HolographicsShell ( https://steamcommunity.com/app/250820/discussions/0/3396302157195505846/?tscn=1667747866 )

13) Oculus tweaks for laptops ( https://steamcommunity.com/app/250820/discussions/0/2960544821853447875/?tscn=1668915856 )

14) Test on stable releases (steam & steamvr), unless the beta notes specifically address your case and be sure to submit a bug report if the beta was the problem. ( https://steamcommunity.com/app/250820/discussions/0/3601219829885362953/?tscn=1669578882 )

15) Check task manager for mining trojans ( https://steamcommunity.com/app/250820/discussions/2/3720565944177228084/ )

16) disable fTPM in BIOS ( https://steamcommunity.com/app/250820/discussions/0/3717188878648710440/?tscn=1670642848 )

17) disable third-party SteamVR overlays ( https://steamcommunity.com/app/250820/discussions/2/3717188878662474883/?tscn=1670859457 ) ( https://steamcommunity.com/app/250820/discussions/0/6087244427733807036/?tscn=1705191527 )

18) GPU congestion from broadcasting software ( https://steamcommunity.com/app/250820/discussions/2/3781373416983040459/?tscn=1679006745 )

19) Razor synapse conflict with WMR and SteamVR ( https://steamcommunity.com/app/250820/discussions/0/3825286438464577842/ )

20) late start from overclocking, or 3rd party overlays, others ( https://steamcommunity.com/app/250820/discussions/2/3806152724344338509/?tscn=1687779526 )

20b) late starts fixed by increasing laptop ram from 16 to 32GB ( https://steamcommunity.com/app/250820/discussions/0/4036979713107386112/?ctp=2 )

21) under win 11 update 22H2, disable nvidia overlay, or disable HAGS, or disable windows game mode, or disable core isolation ( https://www.youtube.com/watch?v=9PETR3t6StU )

22) Disable Windows' high dpi meddling ( https://steamcommunity.com/app/611660/discussions/0/598514944991853217/ )

[eepy cat]

Hey i also have a 5080 and having the same issue, nvidia acknowledged the issue and will prob get fixed in the upcoming drivers.
What I did to be somewhat able to play any vr stuff is disabling HAGS and VRR in windows settings.
HAGS seems to be the issue, sometimes even without HAGS steamvr will just be completely unusable but restarting my pc will somewhat fix that.

I did however hear from other 5080 users that they do not have these issues, so I have no idea what the actual issue could be, I too have a 7800x3D.
Hopefully it'll get fixed soon

[Prim]

Ive also got a 5080 and been banging my head against a wall trying to figure out why im getting such poor performance on every vr game, even steam home.

Ryzen 7 9800X3D
32gb ddr5 5600Mhz
RTX 5080
b650-plus wifi

[CustomDrummer]

@prim I have exactly the same hardware and exactly the same performance issue. :-/

[philneitz]

It's only happening on directly attached HMD's like the Index, PSVR2, Vive etc...

Since HMD's like the quest are encoding and decoding the video/audio stream, its not a "direct display connection" and therefore it works "different" - so My quest is also working fine without any purple spikes or hickups...

this problem in my experience persists WAY longer than 5000 series... I personally use the 4080 and I have this issues since day 0 - the only way to get around with my index is to use my old desktop 3060 pc and using an ANCIENT driver (446.14)

I also know that there's a whole thread around that in nvidia's forums, but because PCVR is a "small market" nvidia couldn't care less - if VALORANT or BO6 isn't working as it should, you can be sure as hell, that there will be a "hotfix driver" in a few days....

[eepy cat]

Originally posted by philneitz:

It's only happening on directly attached HMD's like the Index, PSVR2, Vive etc...

Since HMD's like the quest are encoding and decoding the video/audio stream, its not a "direct display connection" and therefore it works "different" - so My quest is also working fine without any purple spikes or hickups...

this problem in my experience persists WAY longer than 5000 series... I personally use the 4080 and I have this issues since day 0 - the only way to get around with my index is to use my old desktop 3060 pc and using an ANCIENT driver (446.14)

I also know that there's a whole thread around that in nvidia's forums, but because PCVR is a "small market" nvidia couldn't care less - if VALORANT or BO6 isn't working as it should, you can be sure as hell, that there will be a "hotfix driver" in a few days....

The community manager Manuel that handles the nvidia forum driver thread/ subreddit uses VR and has not had issues on 50s but they have managed to replicate the issue and they are working on it, just needs time i guess.
I know plenty of people with 4080/4090s and never heard of this issue, 50 series is in a bad state for VR rn, I somewhat handle it but I can feel everything not being as smooth.
You are right tho, vr is a small market but I'm sure if they wouldnt care hopefully Steam would push for it.
If not us vr 50 series owners players will have to make noise about it but as of now its being taken care of.
Edit: Heck I even know 5080 owners that have no issues in vr, i believe most of them have Intel CPUs, maybe the AMD x 5080 x VR combo is busted rn who knows

[philneitz]

Originally posted by eepy cat:

Originally posted by philneitz:

It's only happening on directly attached HMD's like the Index, PSVR2, Vive etc...

Since HMD's like the quest are encoding and decoding the video/audio stream, its not a "direct display connection" and therefore it works "different" - so My quest is also working fine without any purple spikes or hickups...

this problem in my experience persists WAY longer than 5000 series... I personally use the 4080 and I have this issues since day 0 - the only way to get around with my index is to use my old desktop 3060 pc and using an ANCIENT driver (446.14)

I also know that there's a whole thread around that in nvidia's forums, but because PCVR is a "small market" nvidia couldn't care less - if VALORANT or BO6 isn't working as it should, you can be sure as hell, that there will be a "hotfix driver" in a few days....

The community manager Manuel that handles the nvidia forum driver thread/ subreddit uses VR and has not had issues on 50s but they have managed to replicate the issue and they are working on it, just needs time i guess.
I know plenty of people with 4080/4090s and never heard of this issue, 50 series is in a bad state for VR rn, I somewhat handle it but I can feel everything not being as smooth.
You are right tho, vr is a small market but I'm sure if they wouldnt care hopefully Steam would push for it.
If not us vr 50 series owners players will have to make noise about it but as of now its being taken care of.
Edit: Heck I even know 5080 owners that have no issues in vr, i believe most of them have Intel CPUs, maybe the AMD x 5080 x VR combo is busted rn who knows

Maybe I am an edge case anyway, since I'm using gaming notebooks since 3 years, but on my old Ryzen 7 + 3070 mobile combo I also got around that issue, with downgrading to that mentioned ancient driver.

Now on my Ryzen 9 7945hx + 4080 especially on BeatSaber its annoying as hell...
I also had a Intel i9 13900hx + 4080 and it felt MUCH more stable to be honest, so you might be onto something

[NeN']

I have an i5-14600kf and RTX 5080 Gigabyte OC and have the stutters in all steamvr games, hope they can fix it soon

[Chris]

Same issue here, Ryzen 7 5800X3D, 32GB RAM, RTX5080 on Windows 10 - looks like nvidia have acknowledged it as a driver bug so just need to play the waiting game I guess!