New to MSFS2024 help with VR please

Fully agree that it could still be much better optimized, no disagreement there :grinning_face:

But (IMHO) basing your opinion on this matter on just the fact that one core/thread is sometimes maxed out is not very precise at all.

And supersampling will do nothing to change that, obviously. I think you don’t quite understand some of the mechanics at work here, and the opinion goes against the overall consensus that has existed on these forums since FS2024 launched. If you are seeing something else, you are most likely running a very unusual (and suboptimal) settings config.

But you are right, let’s agree to disagree and have fun. Happy new year :tada:

1 Like

Ultra should be disabled in VR by default pretty much. Same story here, 9800X3D / 5070 Ti OC and running Medium preset with Glass Cockpit bumped up to High.

I tried a new test today. Set my Index to 500% (4508x5008 per eye). Set the Refresh to 144hz. TAA 100%. Turned on Foveated Rendering at 36%. OMG. Performed like a champ.

2 Likes

Good to see someone still using an old (+6yo) SteamVR Native headset like the Index with MSFS 2024. I have a +5yo Vive Pro1 with amoled screens, Etsy lens mod, 2x2.0 Base Stations, and Index controllers. The VP1 was the last true native SteamVR headset ever produced. It was also the last time Valve and HTC Vive ever worked together on anything, lol! I still love using my VP1 once in a while, esp. for night flying, since those amoled screens produce such nice blacks and beautiful colors contrast. Still has a bit too much SDE, but thanks to my 9800x3d/rtx5090 ability to super sample (I don’t see any benefits above 350% btw), it still looks pretty good. The VP1 and Index have the same screen resolution (1600x1400), but I think that the Index has a little better pixel layout and a bit higher FOV, thanks to its canted screens. I get ~115deg FOV with my VP1 using a thin facepad and pretty well no binocular overlap. Also, no glare or murra btw.

The beauty of the Index is that it has multiple refresh rate options (80/90/120/144Hz). My VP1 only has a fixed 90Hz refresh rate. SteamVR still has the very best Reprojection in the business imho. This is why there’s no benefit using RP in the MFSF2020/2024 settings. It will automatically display at multiples (1/2 or 1/3rd) if your fps cannot achieve your selected refresh rate. In my case (9800x3d/rtx5090/64Gb 6000 ram) this then projects at 45fps. In your case it is projecting at 48fps (1/3rd of 144hz). I don’t really know for sure, but I doubt that there is any benefit using 144Hz with MSFS2020/2024. If I had an Index, I would probably try using 80Hz in order to get a more stable RP at 40fps.

Foveated Rendering does work ok now with msfs2024 SU4 but I still don’t like the pixelated outer part of the display and find that this hurts my overall immersion. It also seems to cause a bit more frametime instability.

Rather than using the fairly complex msfs2024 fps output option, like you’ve shown, I like to temporarily use the Steam VR performance graph in headset option (SteamVR settings/developer/display performance graph in headset). I think that this provides more useful, basic information to help fine tune things. The beauty of SteamVR settings is that you can switch back to 2d, make a few changes, then go right back to VR and see how things compare. If you change your refresh rate, you’ll probably need to restart SteamVR though.

With my VP1 I’ve found I get the best overall results with SteamVR visuals set manually (not auto) to 100% with advanced super sample filtering = off (makes distant objects too blurry). Then I adjust the in-app settings to whatever works best. With all my games/sims, including msfs2020/2024, I’ve found 350% works best and I don’t see any visual improvements going any higher, just a little higher latency. Also, while TAA works fine, I’m finding the latest dlss4.5 overrides with 591.74 preset M and dlss/balanced still gives very good, TAA-like cockpit clarity, together with less light shimmering while night flying and a bit better/smoother performance. I mainly fly heli’s dusk-to-dawn in complex cities like LA, Tokyo, and Osaka, with lots of roof top takeoffs/landings. This really taxes my PC to its limits, lol! Once I’ve gotten good results in those areas, the rest of the world is a piece of cake.

Anyway, like I said, it’s nice to see others still getting good results with older SteamVR Native headsets like the Index. Thanks for sharing your experience mate and best cheers from Australia for 2026!

PSA: Please use extreme caution when attempting to upgrade a girlfriend to a 5090. Ha ha!!!

14700k | 5080 | PCL

I am not even close to CPU limited. I am completely GPU limited. GPU maxed out 98% and 90%-100% VRAM usage.

If task manager is to be believed, all my cores are running pretty evenly and I definitely do not have any cores near maxing out. Highest overall CPU usage average I have seen is 40%. It is usually between 30%-40%. My CPU running cool in msfs24 vs when becnhmarking also backs my findings up.

CPU running 5.5ghz all cores.

GPU OC +2500 mem and +350 core clock rock solid stable for a month now. Not a single crash.

I think that if you use better CPU monitoring software like CPU-Z or HWInfo, while flying in msfs2020/2024 you’ll def see one or two cores/threads maxing out, and thereby limiting your overall CPU reported usage. Although 2024 multi-threading has improved over 2020, it is still far from multi-thread optimized imho.

Overclocking your CPU and GPU isn’t something I’d recommend, and I don’t do any of that with my 9800x3d/rtx5090. If you actually see significant improvements with overclocking, and everything’s running cool and stable, that’s great, I guess. Cheers.

Thanks for the reply. I am off now for the next 4 days, so plan on doing some flying and tweaking settings tomorrow morning. I will definitely fire up cpu-z or hwinfo and see what it says my cores are doing. I am interested to see what the results are.

To clarify, I am not OC’ing my CPU. It is set to performance in the BIOS. It runs all cores at turbo, but does not OC the cpu. I am not pushing past the rated turbo and the BIOS setting is not an OC. I hope that makes sense.

For the GPU I almost never OC, but I wanted to get every ounce of power for my PCL and to try and make up for the lack of vram on the 5080. It realy irks me that nvidia used 16gb of vram vs 20-24. It would have made all the difference at bigger airports. Oh well. I am very thankful and blessed to have the gear I have.

I will post the results tomorrow along with my temps.

1 Like

Started up at kbos third party with batc injecting traffic. vr running, pcl, native res 1.

The 16gb vram is the only thing holding my settings back. I was holding out for a 5080 Super as I knew 16gb was going to be a “problem”, but anyone paying attention to memory, gpu’s, AI knows what’s up.

I decided to just get the 5080 at Christmas before I couldn’t get one and/or prices started climbing. 50 series supers delayed and possibly cancelled.