Help with VR Performance using 4080 and i7-14700

I’ve searched long and wide on this topic on this forum and across the net, but most threads point to poor VR performance because of older computers (CPUs and/or GPUs). The recommendations in those threads were to turn down graphics settings or get better hardware.

I just got a new build with a 4080, i7-14700KF, 32GB of DDR5 6000mhz memory, and a fast Samsung SSD. I dusted off my old Rift S as I hadn’t used it in a couple years. My old computer was a i7-6700 and 1070 and performance just wasn’t good enough to use a VR headset, even at the Rift S resolution.

Booting up MSFS, I changed all VR settings to the lowest possible, but am getting poor FPS (pegged at around 40FPS) with jumpy head movement. The FPS counter says the limit is due to the Mainthread. That doesn’t make sense to me with an i7-14700 and ALL traffic and graphics settings turned to off or the lowest possible levels. I’m using DX11, DLSS, native resolution, and 100 on render scale.

Specifically, I tried the PMDG 737-700 in a rural environment.

I after the 40FPS limit, I tried various combinations of BIOS settings (i.e. HT off and on, many others) as recommended across the net, but no difference.

Further searching recommended I turn off ASW in Oculus Debug tool. Doing so, I still get 40FPS in the PMDG 737 while in the cockpit, but 80FPS while panning around in the exterior view.

Additionally, when I put down the headset and the headset automatically turns off, my FPS jumps to above 100FPS while inside the cockpit, but the moment I put the headset back on, it drops back to 40FPS.

With ASW turned off, I get 80FPS in other aircraft such as the Bf 109G6, the SR22T, and the modded DA-40NG, but still 40FPS inside the 737.

Again, ALL graphics settings are turned off or are set to the lowest possible setting.

I’m getting frustrated here. This is a new build system, newest drivers for everything on the system (I checked), HGS turned on.

What am I overlooking? Is the PMGD 737 just that problematic in VR? Yes, I don’t have a 4090, but with a Rift S, I’d still expect non-jumpy VR head movement and performance not limited by the mainthread with all settings turned down to the lowest levels.

Have you got Frame Generation turned on in the PC graphic settings? (You can still go to the PC side of settings, as opposed to VR settings, by using the left/right arrows at the top). If so, turn it off and try that.

EDIT: oh I see you are using DX11 so that can’t be it. Try DX12?

Are you entering VR before or after you start your flight from the World map?

What happens if you try the C152 in the same rural environment?

I’ve tried both ways to enter VR before and after.

Also, I’ve tried using both SteamXR and OculusXR.

@BearsAreCool510 a solid 80FPS at the exact same location in the exact same WX conditions.

@Baracus250 I also previously tried DX12 with no difference.

Try the openxr Toolkit and openXR drivers.
Quickstart | OpenXR Toolkit.

OK, so sounds like that tubeliner is 100% causing the CPU bottleneck then. Can’t help with that unfortunately.

Have you checked your VRAM utilization? It is near or over the 16GB VRAM available on your GPU (RTX 4080)?

Thanks. I installed OpenXR and the sim is now using that. I’m still at 40FPS inside the jet, although now I’m getting momentary spikes up to 50FPS that last a fraction of a second. When that happens, the display states “GPU limited”. The task manager is showing my GPU is running at 35% and my CPU is at 13%.

@OneMoreBulleit my VRAM is showing at less than 4GB/14.938GB (I have all my graphics settings as low as possible).

Old post I know. I have the exact same hardware and getting 60fps in High resolution running max res VR in a Pimax Crystal Light. 80~90% CPU, 100% GPU usage.

Sounds to me like you have a frame rate limiter somewhere. You will soon know if you tried settings at MEDIUM or HIGH and get the same FPS but higher system usage - bingo, frame rate limiter somewhere.

35% GPU & 13% CPU is very low usage. Your system is dawdling along.

p.s. if you have a frame rate limiter on, it will show as “GPU limited”. This happens when I use OpenXR’s frame rate limiter in VR or V-Sync enabled when flying in 2-D.

Thanks for the info. Apparently, my motherboard has components that are failing and I’m being sent out a replacement motherboard soon. Perhaps that could be causing the problem?

Argh, hardware failure is the worst to figure out.

You have to risk buying a whole new component in the hopes that one is the issue.

Well, motherboard failing will certainly not help. Bext of luck. Fingers crossed !