SteamVR won't run my GPU at full capacity

I have switched to SteamVR from OpenXR recently because it seems a bit more stable. But I have ran into an strange issue. My CPU/GPU only hovering at around 70% - 80%, and won’t go any higher unless I click on another app, i.e. MSFS not the front most app, the effect is very obvious in Nevada Bush Trip, GPU immediately goes up close to 100% and cockpit stuttering almost gone.
Any suggestion is very apprecaited.

You don’t say which headset you have. I can see too possible things here : first, the less certain, in the advanced Parameters of Windows you have the settings “Best Performance” set to background program instead of focused one. See below, it’s in French but you’ll find easily.

Second option : MSFS grab all your CPU resource (and that’s the case for lot of guys around) and SteamVR and/or your headset drivers (WMR, Oculus, etc.) don’t have enough headroom to run smooth, so changing MSFS to run in background free CPU resource. If that’s the case, you can play with the first settings from my screenshot, at least when you fly.

I may have wrong obviously, but worth trying!

1 Like

Thanks for the suggestion, but that option was the first thing I went for, tried both extensively to no avail.

But it’s a moot point now, since I initially found SteamVR runtime more stable than OpenXR, and that’s the reason I want to use SteamVR. But after some experimenting with SteamVR, sending MSFS to background letting CPU and GPU go full blast, I still get approximately the same amount of CTD as OpenXR, so I am switching back to OpenXR.

However, since it’s shown that having CPU and GPU not fully loaded in VR mode is much more stable, I set my refresh rate to 60Hz, forced reprojection to always on, and turned on Preview Version of OpenXR, now my rig is a lot more stable than before. Though I do get lots of “Metrix-glitch” while playing, better than not able to play in VR at all.

If you didn’t do it yet, to better understand what’s going on, perhaps you should display your CPU usage in the task manager (or other monitoring tool) dispatched by core and not the average usage of all cores you listed? On my machine (and lot of users here) one of the physical core handling the Mainframe is maximized and other cores are low so I see an average usage of 40/50% where in fact I’m CPU limited, “Limited by Mainframe” displayed also in the Debug window of MSFS.
Not my picture but this is what lot of persons including me have:

index

Edit : Ok, that’s a pretty tiny picture :wink: but you see last core is full handling the main task of MSFS, and the average is low, seems around 50%.

when i said 70-80% CPU usage, i meant the single core performance, in MSFS’ case, the last core. it wasn’t cpu bound, when i put msfs to the background, both cpu/gpu went up to 100%.

I tried to search for you a similar topic around here without success, that’s weird as this issue ring a bell to me. It was somewhere end of last year from memory, people advised to change to first settings I talked about priorities…

Mmmm so I’m dry, sorry I can’t help anymore :sleepy:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.