Weird behavior of MSFS VR with quest 3 (link cable with sufficient bandwidth)

Every now and then a VR flight looks ugly. One eye has a clear view while the other one is ‘torn’ or broken a little bit like a mirror (the parts don’t fit perfectly) - esp. when I move my head. My workaround is to use Oculus Debug Tool and set the parameter ‘(PC) Async. Spacewarp’ to another value. The value itself seems to be unimportant as long as I change it! This seems completely senseless to me (but it works).
Does anybody have an idea what’s going on there and perhaps a more elegant way :wink: to solve the problem?
My equipment:
AMD Ryzen 7 5800x3D, 32 GB RAM, Nvidia RTX 4070, Win 11 - all drivers etc. current version

Hard to say for sure but it sounds like ODT has asw set to auto (= default, so pretty usual). I normally use 45fps forced with asw = off. I use the Oculus Tray Tool game profiles to automatically set this.

You can also use keyboard commands to set and change asw modes on the fly. Ctrl+num1 (numeric keyboard 1, not top row one) = asw off, ctrl+num2 = forced 45fps, asw off (actually 1/2 your refresh rate. I use 80Hz refresh rate so this ends up forcing 40fps), ctrll+num3 = Forced 45fps asw on, and ctrl+num4 = asw auto (default).

You need to find out yourself which asw mode works best for you. Since you can do these on the fly, you may find it easiest to just start off using a keyboard command before starting your flight.

While your Link cable may have lots of bandwidth/speed potential (usually at least 5Gbps with usb3) you should also try to disconnect any unnecessary usb devices so you don’t run out of your pc’s overall usb bandwidth to begin with. You can also pickup some usb interference from some nearby Bluetooth devices, like BT speakers.

Hope this helps mate and cheers.

1 Like

Thanks for the reply so far. One very strange thing is still unanswered:
My experience with ODT is that the ASW parameter can help whenever I run into that VR graphics problem. But - and this is really weird - it doesn’t make any difference which setting I choose as long as I change it!
It might even happen with the next flight that the problems are back (after they’ve been solved before as described) and I can cure this by returning to the old parameter value!?!?!
I don’t believe in witchcraft :wink: Does anybody have a clue by chance?

Sorry mate I can’t explain why you see this happens except that the normal asw default in ODT = Auto and often causes issues for some. Maybe just try using the keyboard commands, on the fly (like whenever you like), I’ve listed and see if this helps.

Again, you can use these keyboard commands when using Link or Air Link on the fly so just try using them and see how you go. BTW, you cannot use these commands (or OTT and ODT) with the Virtual Desktop app because it does not use the official Oculus runtime, just their version of it.

In any case, it sounds like you’ve found a workaround, so I wouldn’t worry yourself silly about all this imho.

Thanks again, esp. for the key commands. I’ll check them out. Sounds easier than my former workaround indeed.
When I found that strange behavior I hoped it could possibly unveil some deeper problems and help to solve them - VR is still far away from perfection IMHO…

I feel like I have the EXACT same issue with an oculus 3 (link cable) and 7800x3d/4070ti. It doesn’t happen at first but usually within a couple min into the flight and its usually the left eye that is “torn”. In my case, if I take off my headset and set it on the table for 10 seconds and put it back on it fixes it. Sometimes that fixes it for the rest of the flight and other times only for a short time. Some flights I find myself taking my oculus off and on 4 times to fix it. I was going to try swap different brand cables and perform other test this week… but its driving me nuts. Siohttam, Please keep me updated if you discover anything!! Thanks!!

Couple things that make quest 3 better. 1 virtual desktop with a wifi 6e router. 2 never put your quest to sleep. If you hang your headset while it sleeps, the IMU gets all confused and you’ll have tracking issue. Shut it down and or restart so it calibrates correctly. 3 don’t use asw or ssw or motion reprojection. Tune your sim to run at a multiple of the refresh rate of your quest. 72 80 90 120hz and shoot for settings that give 1/2 of the lower 72 80 or 1\3 of 90-120 hz in fps. The HMD will reproject without these distortions due to bad prediction of motion.