Make sure to use AX WiFi and not AC, apparently there’s a bug in Q3 causing latency issues/stutters with AC. Also, switch to VDXR when it is released.
I am using a 3rd USB party cable I used with the Q2 before and it charges quite well while I’m using VD to run the VR. Just had a session of well over an hour and battery still showed 74%.
2 Likes
I also used the inbuilt VD performance overlay to see my wifi speeds in VR I also had the inbuilt openxr frame rate display. The openxr frame rate was showng 30fps but the VD frame rate overlay was showing 60 fps anyone know why this is the case?
ok thanks as FS is a seated experience I will probably just hook up the usb c cable to keep it charged.
ok can’t do AX as my router is 5 ghz
IEEE 802.11ax is available for 5GHz as WiFi6. Only WiFi6E uses 6GHz. Double-check that your router really doesn’t support IEEE 802.11ax. If not, you could wait and see if a Q3 firmware update will fix this or do what I did, which was to just add a $89 AX 5GHz router to one of the ports of my non-AX router. This way I have a separate 5GHz AX, apart from my main WiFi, that is only used by the Q3. I’ve plugged my MSFS machine into the AX router as well.
Side note: I believe I saw something on the VD Discord about Q3 having issues with several 6GHz routers. Mentioning just in case you want to go that route. I consciously didn’t and have no issues with 5GHz AX and the Q3.
Thanks I just checked the manual on my router (which is over 10 years old) and it states
Wireless access
The built-in 2.4 GHz IEEE802.11n and 5 GHz IEEE802.11ac wireless interfaces provide wireless access to your wireless clients.
I’ve spent several hours now with the Q3 and MSFS. Overall it is an improvement over the Q2 for sure, but I am still frustrated that I cannot get both the amazing sharpness and smoothness at the same time.
Here is a rundown of my setup:
13900K
4090
1gig ethernet speeds
Asus AXE-7800 completely dedicated access point on my desk, 6E
Virtual desktop, connecting on 6E at 2401mbps
I also downloaded mbucchia’s Virtual Desktop-OpenXR software and got it running (it helped)
Not relevant but I also use the Honeycomb alpha yoke, Thrustmaster TPR pedals, and a throttle quadrant.
Here are my observations:
-
At first using the settings I was using on my Q2, it was unplayable. Stutters, shimmering, blurriness. Three things fixed this: switching to Open XR, disabling the spacewarp function in VD, and switching from DLSS to TAA.
-
When I crank everything to the max (TLOD and OLOD, everything on ultra) with TAA at 100%, the picture is amazing, full field of view, can read all the tiny writing in the cockpit, etc. I mean it’s fantastic. The problem of course is that this creates a large amount of latency (mid 60s-70s) and drops my FPS to 38-45 (this is in the Piper Warrior in a rural area). I switched into the F18 over San Francisco and it was unflyable at those settings, latency over 90 and mid 20s FPS.
-
In virtual desktop there are a number of settings. I have tried Godlike, Ultra, and High graphics settings with the Snapdragon function both on and off, and while I do notice a difference in the graphics, the performance improvement by downgrading them was barely noticeable. So I have kept it at Godlike. I have also kept the bitrate at 200, because once again although dropping it to as low as 50 improves the latency somewhat, the tradeoff in graphics decline is not worth it IMO.
-
The most impactful change in settings that improves performance for me is adjusting the TAA percentage. If I drop it to 60, I am flying at 72FPS and it’s very smooth. However the drop in graphics quality is certainly noticeable. At 100, I can see the framerate when I look out the side of the plane, but looking straight ahead is fine. I have settled on 75 as a compromise. I figure this is the easiest thing to adjust in the game if I run into busy areas by dropping it or open areas where I can crank it up. It does not require a restart which VD makes you do when changing major settings.
-
In VD, I have tried all the FPS settings and I don’t see a difference because I can’t get above 72 anyway I think.
-
I’ve run into several CTDs, I have no idea what is doing it. Some were in game, some when I launch the program. I am running the latest NVIDA driver (537.58).
-
I tried the OpenXR toolkit, but it introduces an artificial sharpening/shimmer (not sure what else to call it) that is off putting. I haven’t seen a major improvement in FPS using it, but I spent very little time with it so far. If anyone has any suggestions for OpenXR toolkit with my setup, please let me know. I do like the ability to adjust the contrast and wear sunglasses etc, I wish that was part of the native game.
-
Yes the strap sucks, it’s better than the original Q2 strap, but I am waiting to be able to order the BOBOVR M2-M3 conversion kit, since I love that strap for my Q2 but don’t want to buy a brand new one.
Maybe my expectations are too high. I wish it would run at 72FPS at the max graphics settings. I mean I can’t get any better gear. The main test I do is sit in the cockpit, turn my head about 30 degrees, and look at the line on the VOR indicator. Then I sit forward in the cockpit. I clearly see a series of lines. The other test is flying at 1000AGL and looking out the side of the aircraft. With the settings turned up, it’s certainly blurry and periodic.
At this point I don’t think the link cable (never tried it) will help but I am considering buying one to test and I can use this extra 6E router as a coaster or something. Until then I will just keep tweaking settings until a new graphics card and CPU come out:/
2 Likes
Try the cable. For me, using the cable and Quest Link was also like night&day compared to AirLink/VD. Of course I also tweaked the settings via Oculus Debug Tool (setting bitrate).
GPU (4090) seems not to be the problem for me, exept cranking up the TAA… more limited by the CPU (7800x3d). I do not seek for 72fps or another rate - I just want to have a smooth experience.
2 Likes
I just want it smooth. I don’t know if it’s FPS or latency that’s causing the problem.
I’ll get the link cable and try. But before that someone told me to turn off AI vehicles and stuff like that, I’m pretty sure I have all that stuff up to 100.
For me via Wifi it was every few seconds a lag, or if I turn my head to fast in the cockpit. Virtual Desktop showed me in the Overlay tool a) somtimes spikes in network latency and b) sometimes spikes in Encoding. From reddit Encoding is up the GPU - but I have a 4090 and I cannot see any issues (Powerlimit or something) in GPU-Z, so don’t know how to get rid of it. Also with cable I don not have issues. Wireless Network… that is tricky to investigate as I already have a dedicated 5GHz network with only the quest connected. I could now try to have a sperate AccessPoint with only 1 device connected and so on… searching if something in windows is disturbing or so.
So I decided to give it a try with the cable… and I’m happy so far. For FlightSim I’m sitting in the chair, so cable is ok 
To be honest I have AI Traffic via FSLTL, I have Road Vehicles at 80 or so (love to see the cars driving when flying low). Of course you can disable all that stuff, try it and if it is smooth - step by step cranking up to see what is possible. I usally go the other way round, everything maxed out and then lowering the stuff until NYC in 1200 feet is smooth enough 
1 Like
More tests today both with link cable and VD with openxr beta tool.
Save you some time reading, all that with 4090 and 12900k, I had to push resolution scale a lot to get picture I like after using g2 and keep acceptable performance. q3 is way over demanding in my opinion.
Gotta say it’s still not perfect but I got it to a point where I went back to compare to my g2 setup and couldn’t use it anymore. Got used to that edge to edge clarity lenses quick. So q3 it is till something new comes out.
You can see my settings on pictures below and that’s quick recap:
-Virtual desktop with VirtualDesktop-OpenXR (beta) with wifi6 router and AV1-10 bit codec
-In VD godlike mode, 80hz, 0,72 gamma, SSW off.
-OpenXR Toolkit Companion app (see pictures for my settings but it’s mostly for render scale)
The scale I’ve set there is just a number that worked for me, can go either way depend on what you looking for. NIS setting is also personal and can be anything else.
-DLSS quality what makes it all work smoothly and rest of setting on Ultra with clouds and shadows on high and TLOD 200, Objects 150
*TAA setting - I tried it other way around and just use lower render scale with taa, with about the same picture as dlss I was losing 10-15 fps, so didn’t work in my case.
That gave me stable 40+ fps over photogrammetry city at low altitudes.
I also did some test with link official cable. Same settings in OpenXRtoolkit, oculus app 80 hz and 1.0 render scale, OculusDebugTool see picture below for settings.
Overall I liked picture better with link but performance was not that stable and I was getting random visual glitches in different sessions, might’ve been asw fault, didn’t try without it. Also oculus pc app crashed couple times.
Wireless set up and relatively easy connection through VD is really nice addition after g2 heavy cable. Love that double tap on a side of q3 switches you to passthrough and you can see hardware or whatever needed without removing whole thing every time.
Q3 is very nice VR headset but I don’t think it’s a good pcvr for the price. Big thanks to guys who made VD and @mbucchia for his amazing tools for pcvr. Meta didn’t even manage to update it’s PC app with new codec for q3.
2 Likes
I thought VDXR 0.6.0 was broken with Link ^^
Are you building the latest code yourself 
?
1 Like
I cant seem unable to copy/paste 940 into the encode bitrate in oculus debugger, you obviouly managed it, any help please.
Haha, way above my skills). I’ve switched back to oculus runtime for that, forgot to mention. Would be amazing to go around it though
@ Tussalwater85
That’s odd, like you said I just ctrl c, ctrl v the number from a text file. I’m not sure it does anything to be honest cause you still limited by h.264 codec.
Alpen, when you activate OXR toolkit, do you not see artificial sharpening and shimmering on everything? I gave up playing with it because of that effect.
Right now I’ve just been adjusting the TAA scale because when I turn on DLSS I feel like I’m on acid, trails behind everything and artifacts. Maybe I need to try DLSS plus the toolkit. I haven’t messed with the resolution override setting at all.
More trial and error I guess tonight.
Yes, on the very first q3 start up I had exactly same experience. Not sure what fixed it though cause I kinda gave up on VD after that and went into link tests and reset all settings.
I had very outdated toolkit version, completely forgot I use it so that got updated. I think it’s mostly resolution scale that worked out, native VD godmode res was same as you’re saying in dlss and I had to go to 110-115 taa for somewhat better result with meh performance.
Couple other things I did which might have helped. In VD sharpening to zero, as well as msfs amd fsr 0.
And I’ve used NIS 20% sharpness instead.
Also in nvidia panel I forced anisotropic filtering to 16x. Didn’t touch anything else there.
Hope some of that will be useful. Haven’t had to mess with so many settings and tools since my very first msfs vr attemt. You would think almost 2024 should be easier I guess still not there yet.
ps I almost wonder if it’s just msfs fault cause native apps look amazing in q3, Alyx is great, want to try DCS now, never used it, if anyone wanna point me in right place for that, pm me, I’ll appreciate.
What type of latency are you getting in VD?
I am wondering if that is the main issue I am having, not FPS. I am consistently getting into 80+ for latency, and at 40 FPS (which should be pretty smooth) I look down at the ground and it feels like I am seeing individual frames run by.
The only thing I can do to reduce it is to turn TAA way down, or put on DLSS. But that kills the graphics. But then it is smooth with latency in the 50s. I think that is still higher than I had with the Q2.
No other settings seemed to make a difference. I had all the ground traffic up to 100 and turned them all off and no difference whatsoever. I tried taking TAA down to 50 and then using OXRT to override back to full res but that didn’t work. I’ve dropped to ultra and high in VD and all it does is make it look like my Q2.
I am connected using a 6E router and am getting 2401 mbps (although this target moves up and down which my Q2 at 1200 never did).
I would seriously pay a consultant to come to my house and dial this thing in, for the amount of time I have spent in the headset not actually flying anywhere. It is worse than when I first got the Q2 set up because I didn’t know what was good and what wasn’t:(
1 Like
~60-70. I went back to wired link though, better picture overall for me.
First my simrig is a 13700K CPU with and RTX 4080. I used to fly VR with the Reverb G2 and liked it despite the visuals limitation.
Last week I bought the Quest 3 with the link cable and the improved head strap. I have no regrets and the G2 has already been sold. (For me the headstrap upgrade is a must)
Setup in the beginning was a little tricky with mixed results but the tips and hints from this website and others were very helpful.
My preferred setup is Oculus Airlink connected via Wifi to a dedicated Wifi router on the desk (not Wifi 6 btW) connected in turn to the internet modem and the PC hardwired. The graphics are set to ultra and I get a solid 40FPS in the game, very nice graphics clear to the edges, smooth without stutter. I get very similar results with the link cable to the headset but it is so nice to have no cable to the headset.
I also connected my PC directly to the internet router and then the Q3 to the PC via the link cable and the results are the same.
Tried the Virtual Desktop with Steam VR and results are not bad but not as clear and occasional stutter.
Conclusions so far: A dedicated Wifi router on the desk is needed for Airlink. Connecting the Q3 and PC via Wifi to a modem even in the same room 20 feet away just does not work unless the graphics are turned way down. Virtual Desktop gave me poorer performance, could be a setup problem.
4 Likes