After exactly one year of flying in only 2020 I am considered no giving up
Thanks to some very knowledgeable and professional people on here who gave advice I just wonder to myself if I 1) I am not fully understanding the guts of my machine to make VR work without blurriness and poor graphics 2) expecting too much 3) overloading my processors
Here’s why - I only fly in VR. DLASS and not TAA. In monitor mode I get clean, crisp and unrivaled performance. Comparing that with VR it can be very much one day incredible and the next day a ‘whoa hang on’ a moment situation - I 90% fly the PMDG 737 800 and I must say the close up is crystal clear of the cockpit - I am on DLSS ‘K’ but still have ghosting - GA is pretty good but prefer airliners
I use VD only and have the following rig/component’s
You need to use OpenXR & open composite runtime switcher. With your system, you should be able to get good graphics & performance. I run a 1070ti & a Ryzen7 & I can get 36fps, my graphics isn’t perfect but I can deal with it plus my eyes aren’t that great in the real world anyway but I do get reasonably smooth flights. The best way to get better performance is to google & youtube as much info as possible & work from there! There’s a wealth of knowledge out there on what tweaks & addons to use as well as a multitude of sim, nvidia & other PC settings that all help to get the best bang for buck out of any system.
My PC is a potato compared to your spec & I can’t complain at all about VR, I love it…
Try enabling ASW and forcing 45 fps (which actually halves your native refresh rate - if you set 75hz in the Open Runtime app it produces a constant 36fps which is as smooth as
Butter).
Asynchronous SpaceWarp (ASW) is a frame-rate smoothing technique that almost halves the CPU/GPU time required to produce nearly the same output from the same content.
Asynchronous SpaceWarp is a tool for improving framerate on PCVR headsets (like Rift), and should not be confused with Application SpaceWarp (AppSW), which is a tool for improving framerate on mobile headsets (like Quest).
So I done some further tweaking. It’s all I seem to do and as a result of a YouTuber ‘Caribbean Captain’ I made some changes on both in sim and NVIDIA. As a result I saw some improvement and frame rate increase- I landed in an airport at early evening and saw some improvement
Ah, yeah ok! I am using the quest 3 version on my set-up… It makes things pretty smooth on my sim, I get the odd stutter but not often…
I was always learning new settings & tweaking them when I first got into VR, not as much now but I still pick up new stuff & give it a try.
VR flight sim guy on you tube has some good tips & settings but every now & then another video pops up with another setting or trick to get more out of a PC system, even NVIDIA settings HAGS, game mode plus there’s even a couple of internet/wifi settings that can all help.
Hey, I’ve also owned the Quest 3 for about a year now.
In MSFS2020 I had some amazingly smooth experiences with the Quest 3 on Quest Link, but this required some extensive tuning of the meta software, oculus debug tool, and openXR toolkit.
Now in trying to get MSFS2024 to work the same way, I’ve been going down a similar rabbit hole to get that high definition and smooth as butter experience (where you can actually believe for a second you are in an aircraft), but I’ve still had not gotten it to work with Quest Link.
Either my meta install is messed up, or Quest Link software itself has degraded, because with Quest Link I have still NEVER gotten rid of this new slight jitter (or judder) that happens when rotating the plane, looking at the ground, or even rotating your own head. I thought I would load up MSFS2020 to see if it was just a 2024 problem but actually it was happening there as well!
Regardless, now I have finally found a setup that is as good as my experience I used to have with 2020.
My solution:
My PC motherboard supports hot spotting, and a new Windows 11 update allows you to hotspot on the 5GHz band. What I did was use Virtual Desktop on the Quest headset, connect to my PCs hotspot, and then stream to the headset with VD.
It’s finally smooth again! I took the Citation X out with VDs settings on godlike preset (max resolution),72 Hz, ASW on, with TAA antialiasing. I couldn’t believe I had finally got a smooth experience back.
You want to be GPU bound. I have my Valve Index at 300% resolution (3492x3880) with no Motion Smoothing. I have my settings at Medium or lower with TAA 100%. Nvidia control panel at defaults. No OXRTK or any other outside tools. No Nvidia Reflex. I get around 20ms GPU frames and 10ms CPU frames. OpenXR keeps me steady at 40fps.
I recommend upgrading to a 16GB GPU, as this method consumes more VRAM.
Ghosting will always be there unless you can achieve FPS that matches your refresh rate. This is just not possible with today’s hardware, so don’t go looking for it. I keep my vision ahead, and I don’t look out at 90 degrees when I’m flying down the runway.
I also have inconsistencies with no changes to settings. On day perfect flights, no stutters, good FPS, next day stuttering mess, low FPS, or it all starts ok, and then FPS drops to 6 for no good reason.
Last night flight was a short hop in the 737-800 from EICK to EGGP and it’s the best and most stable flight of the week. Graphically better although still shimmering but no stutters and a great improvement
Did you turn off ASW in the oculus debug tool? When I turn it off, I get best results, or you can try to lock frame rates with ASW off.. But my system likes it off, no judders with plane on outside view, messed up asphalt etc on ground, no wisping black lines above…
I just wish it would stay off, I set the debug tool in my taskbar, and launch it after I have the headset linked, every time I turn on computer.
First of all the Trick with Quest 3 is to use Virtual Desktop with a good wifi setup instead of Meta Link.
Whatever you set in the oculus debug tool will not affect Virtual desktop btw.
Second of all you should make extensive use of SSW. For flight sim, ideally put it to always enabled.
I don´t know the PMDG but the complex aircraft generally have a huge CPU impact due to poor coding. Try the ICON A5 for a test ride and see if it´s smooth. If it is, at least you know it´s just a matter of tinkering with your settings. Start with disabling ANY traffic / multiplayer. They have huge CPU impact.
For reference my settings on a 7800X3D and RTX4090 are fs2020 ultra preset with DLSS (preset K, very important for clarity), no traffic except roads and VD maxed out at godlike res 120hz SSW always on AND most important for smooth framepacing: use SteamVR as openxr runtime. The VDXR implementation has a slight stutter to it. No idea why but it´s been confirmed several times. If you absolutely have to use VDXR for whatever reason make sure to enable turbo mode.
I still get the very best results with both my Q3 and QPro/rtx4090 using the official link cable connected to my z790mb usb3.2 gen2 type-c port using 900mbps max dynamic bitrate (usually settles in at 750-800mbps). If you leave all other oculus debug tool (ODT) link settings to defaults/zeros and just enable dynamic bitrates and set the max to 900, you can also use the exact same ODT for Air Link as well since ODT defaults automatically sets the correct codec and slice encoding options (h.265 and slice encoding disabled for Air Link and h.264 with slice encoding enabled for Link).
Also, with debug tool I set to forced 45fps with asw = off. Since I set my meta-link device graphics settings to 80hz refresh rate (and res slider full right) this gives me a very smooth, stutter-free 40fps. I also set pixel density (super sampling) to = 1.30 because this results in TAA-like cockpit clarity using dlss/balanced.
It’s a bit of a pain that ODT always returns ASW to Auto after restarts but you can use the Oculus Tray Tool game profiles to set these. Alternatively, you can use simple keyboard commands to set these on the fly.
Ctrl+num1 (numeric keyboard 1, not top row 1) = asw = off, Ctrl+num2 = forced 45fps (actually 1/2 your refresh rate) with asw = off, ctrl+3 = forced 45fps with asw = on, and ctrl+4 = asw= auto (default). It’s nice to be able to try all these asw setttings in the fly to see which one works best for you. You cannot use these with Virtual Desktop since it doesn’t have the official oculus runtimes, just their unofficial version of these.
just got quest 3 after my vr set occulas rift s went pop what a difference between rift and quest 3 my system intel 1300 k msi 790 mpg carbon wifi msi 4070 ti 64gb ddr5 xpg ram still trying to tweak in setting s for pmdg 737 800 foun that asw in oculas debug set to force fps45 disabled works well
