Quest 3 Jitter

Hi, I’m new to VR (QUEST 3) so bare with me if I don’t understand your suggestions and have to ask for clarification.
Ive spent the last week trying to go through a process of eliminations to refine the experience as best I can, the game now looks to an acceptable level based on this process. I connect to the PC via 3rd party link cable + charging as it seems to have the edge over Virtual Desktop however I am open to revisit VD if there are pointed suggestions.

The Problems

There are still jitters when scanning inside the cockpit, they are particularly noticeable when scanning past cockpit frames and sometimes steam gauges, and any rapid head movements. This is the biggest issue that i cant seem to solve and it makes my flights very short because of fatigue.

A secondary issue is the hitching that seems to occur when AI or other players are present or when doing a manoeuvrer such as a 180deg turn on the ground. Also when viewing AI but especially players their aircraft jitter as they pass by. Its bad enough that i cant tell what aircraft they are in at times so now i just look away to avoid nausea.

Any advice or help to resolve this would be greatly appreciated.

All changes to settings below were tested after a default baseline established. Then only 1 setting at a time.

PC Specs :

  • AMD 9950X3D
  • Gigabyte X670E Aorus Pro X
  • 64 Gb GSkill 6000Mhz
  • Asus RTX 4090
  • Windows 11 Pro + FS2024 on separate NVMe drives

Nvidia App Settings

  • Power Management - Prefer maximum performance
  • Vertical Sync - Off

Nvidia App DLSS Override - Model Presets

  • Frame Generation - Recommended
  • Super Resolution - Preset M
  • Ray Reconstruction - Use 3D app setting (Default)

Oculus Debug Tool (Default except Listed Below)

  • (PC) Asynchronous Spacewarp - Disabled
  • Distortion Curvature - Low
  • Encode Resolution Width - 3664
  • Encode Bitrate (Mbps) - 500
  • Link Sharpening - Normal
  • Local Dimming - Enabled

Meta Horizon PC App (Default except Listed Below)

  • Unknown Sources - Enabled
  • Open XR Runtime - Meta Horizon Link set as active
  • Link Transfer Rate - 2.1 Gb
  • Refresh rate - 72 Hz
  • Rendering resolution - 4480 x 2400

Flight Simulator 2024 VR Settings

  • Exposure Compensation EV - -0.5
  • Anti-Aliasing - Nvidia DLSS Super Resolution
  • Nvidia DLSS Super Resolution - DLAA
  • Foveated Rendering - Disabled
  • AMD FidelityFX Sharpening - 100
  • Max Frame Rate - Disabled
  • Reprojection Mode - Off
  • World Scale - 100
  • Dynamic Settings - Disabled

Flight Simulator 2024 Global Rendering Quality (High Preset except Listed Below)

  • Terrain Level Of Detail - 100
  • Off Screen Terrain Pre-Caching - Medium
  • Displacement Mapping - Off
  • Buildings - Medium
  • Trees - Medium
  • Plants - Medium
  • Rocks - Medium
  • Grass - Medium
  • Objects Level Of Detail - 100
  • Volumetric Clouds - High
  • Texture Resolution - High
  • Anisotropic Filtering - 8x
  • Water Waves - High
  • Raytraced Shadows - Disabled
  • Shadow Maps - 1536
  • Terrain Shadows - 512
  • Contact Shadows - Off
  • Windshield Effects - High
  • Ambient Occlusion - Medium
  • Cubemap Reflections - 256
  • Raymarched Reflections - Medium
  • Light Shafts - Medium
  • Visual Effects Particles quality - High
  • Cockpit Glass Refresh Rate - Medium
  • Characters Quantity - Low
  • Characters Variety - Medium
  • Characters Quality - Medium
  • Airport Services Quantity - Low
  • Airport Services Variety - Medium
  • Parked Aircraft Quantity - Low
  • Parked Aircraft Variety - Medium
  • Air Traffic Quantity - Low
  • Air Traffic Variety - Medium
  • Road Traffic - Low
  • Sea Traffic - Low
  • Fauna Density - Low

I personally gave up on fighting the cables with my Quest 3 and switched to Virtual Destop. Runs amazingly well - smooth, good resolution and high TLOD/OLD.

That being said I also needed to buy a 6E router to use as an access point (very easy to do) just for my headset. But has been smooth sailing ever since.

Also new to the Quest 3, have tried both Virtual desktop and the Link cable, I can’t decide what’s better at this point.

do the Flight Simulator 2024 Global Rendering Quality affect VR or do we only need to change the Flight Simulator 2024 VR Settings ?

I would say the main things that stand out to me from your current settings are:

  • 3664 resolution
  • Spacewarp is currently OFF
  • DLAA (this is the red flag)

That is a really demanding recipe.

I only run a 4080 and have only found VD to work well for me, but honestly even with your 4090, I would try:

  • Spacewarp FORCED ON (the quality of this function is really much improved in VD - according also to friends that have tried both ways!).
  • Set refresh rate to 72Hz (this way you need a stable 36fps which should be achievable). You could try 80Hz later.
  • Lower the per eye resolution (around 2500).
  • Use DLSS Super Resolution, balanced (not DLAA! That is really demanding). Or quality if you find balanced always smooth.
  • Limit the frame rate in MSFS settings to half your headset refresh rate (36, or 40 if you use 80Hz).
  • Ideally try VD again, with the quality on Ultra (not Godlike).

As mentioned above, to get the best from VD you need a dedicated and close by 6E router set as an Access Point only.

These settings are in VD? I know the DLSS and frame rate is in FS.

I have set resolution width as 2500 in Oculus Debug tool.

I should limit FPS in the SIM as well as force spacewarp? I thought spacewarp did this already but i’ll try these settings now.

As I’m not familiar with VD as much can you list any settings I should change from default please?

Regarding the router I willing to spend but I need to see some kind of inclination that it is going to give me gains first so hopefully testing this will do that.

I have a 5ghz router that I’m next to (Virgin hub) so I’d have to set that into modem mode and connect any new one to it that way. Not sure how I would set access only but I can cross that bridge later if I need to.

Try turning off hardware accelerated GPU scheduling in Windows. This causes flickering / shimmering for me using the Quest 3 and link cable.

The other visual artefacts I see are usually caused by ASW, but you have that turned off already.

Well, that’s how I have mine with VD but reckon it’s similar theory for cable link too.

It does, but having the GAME lock it means the ‘clock’ is more in synch with what the game is delivering as only the game knows about when frames are ready. IMO :slight_smile:

For sure. Can you buy on Amazon? That way you can return it before 30 days if it doesn’t work good for you. I got this TP-Link one which is on the suggested devices list at the VD Discord and got it at a really good price late last year (I had a regular 6 before, and the E definitely made things smoother).

https://amzn.eu/d/04gQHBuF

You would just need a Ethernet cable between this router and your incoming Hub, and another from it to your PC.

It’s just an option within the router config page accessed via a browser when you set it up.

Yeah, this can have some weird effects but, A: The trade off is worth it for me and B: Actually if you CAN run 80Hz, it helps reduce some of the weird lines and stuff that can appear. Again, for me, YMMV with anything “VR”! :smiley:

I forgot to reply on this. Best thing would be I send you my settings screenshot next time I’m on the PC (Wednesday). Use AV1 codec to start with though. Try 120 bitrate (I don’t see any visual difference higher than that, just more latency).

Also highly recommend using foveated rendering set at 50 to improve performance. Also try set DLSS to at least Quality to free up some more performance.

You can turn on the performance overlay in the Oculus Debug Tool to monitor performance to check framerates and render times.

So I just tried the recommendation settings as per the original post and I was definitely doing something wrong originally as this felt really nice and smooth with less jitter than the link cable. It like it swaps out edge jitter for edge blur which I can definitely live with.

I’ll play around with the settings and apply any other recommendations you suggest, others have made a few since posted too so I’ll experiment with those suggestions too.

One question though should I close oculus debug once I’ve set it or should I open it for each time I use the pc for VR? I ask as I noticed the settings randomly revert, to counter this I set it as administrator but when it isn’t active it’ll change again I think.

Thank you to everyone who is helping me with this, it’s very much appreciated.

One discovery I can share is turn OFF live or All Players and set Group only because multiplayer hitches everything.

When looking at the VD on-screen display under the WiFi tab my game displays yellow (game sending more data than the quest 3 is decoding?)

Latency is also yellow around 65-75, although it doesn’t appear to have much effect from what I can tell.

Below are screen shots of Oculus Debug Tool, VD PC settings, I don’t actually know how to screenshot my quest 3 screen to give VD App settings :see_no_evil_monkey:

Good progress!

Yeah there is definitely some ghosting but Model K on DLSS is a lot better for me (with Balanced or Quality setting). Have you installed the latest DLSS file version (using DLSS Swapper or in the NV App?). From memory its on 310.6.2 or something! The one that MSFS ships with is really old.

Can’t answer that - I don’t use the Oculus tool.

Try setting the Multiplayer Models (in “Online” settings) to Simplified (not High Fidelity). You lose the weak attempt at model matching that MSFS trips up on, but at least you do now get quite appropriate looking aircraft in return.

That’s not too bad. Depends a lot on heaviness of the current situation you’re flying in.

You can take screenshots with the Meta Quest button (right controller) + Right trigger and it saves on the device but you can choose a location on your PC to save them in instead (“desktop” or whatever) using a setting in the menu somewhere. Media I think.

I have not read the whole thread and perhaps someone just mentioned it.

My way:

I use VD.
I reserve the whole Wi-Fi frequency 5Ghz bandwidth (up to 2,5 Gbit/s) of my FritzBox Cable 6600 for the MetaQuest 3. The router is < 1m located to the MetaQuest 3
The 2.4 Ghz frequency is fast enough for all the hardware (a lot) in our house who needs an internet-access.
The PC is connected to the router with cable. (Internet-speed = 500 MBit/s)
I don’t allow the MetaQuest 3 to connect to the Internet.
I don’t have started any MetaQuest 3 software on the pc, only VD. Have a look with autoruns.exe.
So I don’t have any interferences with other wlan-users or the MetaQuest doing other things than taking care for the Flightsimulator.
From time to time, I enable internet access to download any potential updates for the MetaQuest 3 firmware or VD updates.

Result: Smooth VR
VD Resolution: Godlike 72Hz.
4070 (overclocked without changing voltage) / I7-14900 watercooled, bios optimized (undervoltage).

By the way: a lot of other little hacks, you have to find out which are the best for your system.

Indeed. It’s endless!! So many options everywhere.

In fact, @PlagueDoctor815 you don’t mention yet anything about your BIOS configuration?

Are you using ReBAR and Above 4G Decoding?

Have you disabled onboard GPU, WiFI, Sound (if you don’t need to use those things)?

Which XMP Profile are you using?

Have you done anything with Curves for the processors (undervolting)?

How are you managing core priorities with your 9950?

Oh, one more “probably important” thing. On the Access Point, if WiFi Transmit Power is on High (usually is by default) that can and should be set to Medium. If the router is close to your headset for VD Wireless connection.

To adjust TP-Link router’s signal strength (transmit power): Log into the web interface, go to Wireless > Wireless Settings > Transmit Power and select High, Middle, or Low

Having it on High is better for long distance and going through walls but basically if you are close anyway, it’s just like shouting and can have noise on the signal that you don’t need. Medium is more stable.

Good idea. Will have a look for my case, if it is possible to adjust seperately for the frequences.

edit: Chat GPT says: not possible.

  • but 2,4Ghz will be strong enough with 50% signal-strength.
  • in Germany, where I live, the lower radio-channals only use 200mW instead of 1000mW

Interesting, I will test it.

Yes rebar is enabled. XMP level 2. Above 4g coding is enabled.

I have a stable undervolt overclock that is noticeable for better temps and a slight performance uplift.

I also have a slight GPU overclock through MSI afterburner but it was switched off while I tinkered with these settings.

I ordered my new router it comes today. I didn’t order the one you recommended but ordered an GL.iNet GL-BE9300 as there’s some extra features I want to try out on it unrelated to FS so once that’s set up that’s a little more performance from VD too.

Reference the DLSS model I’m using M set through the Nvidia app and I’m on balanced in FS as it seems to look perfectly nice.

Oh yes referencing the router access point etc I will be sure to look into those once the new router is in place so thank you for the tip here

Worth a try with ReBAR and 4G disabled. To be honest I need to try with them on again but in the past having those 2 enabled causes all sorts of freezes and hitches. Was much better for me without but things may have changed. Still worth a quick try in both ways to see if it makes a difference for you.

Can try it yeah just gotta make a list of what to change and try etc so I’m not causing confusion.

Yesterday it was very smooth and stable and now the beta 6 released it feels like key presses are getting lost. I might leave the beta maybe.

I’d suggest uninstalling everything related to Meta/Oculus/Link if you’re using Virtual Desktop. It’s not needed and will just confuse matters by presenting you with yet more settings that probably aren’t even relevant.

For myself, I run Virtual Desktop over my normal 5Ghz Wifi (no dedicated router but I have decent Ubiquiti access points), using a step down from Godlike (really can’t tell the difference) and 72FPS with ASW enabled and 36 set as the max in game. While it’s no longer recommended, I also still have the XR Toolkit installed, and use that to reduce my field of view by about 10% on a few axis, but you can achieve the same with VD now anyway. Fov rendering is set to 45 in game.

In-game settings are a mixture of Medium-High, with some external assistance for dynamic LODs. The latter is probably what really makes the difference for performance, and I can maintain a steady 36fps 99% of the time. Just have the occasional drop in very heavy areas or when running BeyondATC. 9800X3D with a 9070XT 16G. I use TAA but might experiment a bit more with FSR now that 4.1 is supported.

I’d love a higher resolution headset, but a) could my PC cope, and b) none of them seem to do colour passthrough as well as the Quest 3. I couldn’t live without my Virtual Desktop hand-tracking passthrough windows. Anywhere my hands go, I see the real world around them, but with a selectable level of transparency so I still see the VR cockpit too. Perfect.