Yes, but on the G2 I used Rivatuner, that worked the best. Now on the Aero I use the Varjo Base vertical sync setting, which also locks 45fps to 90hz. Works really well.
This is what just about every VR user that doesn’t like reprojection does, or at least should be doing! 45fps locked at 90hz is much better than 46-87fps at 90hz because then the frames are out of sync with the refresh and it stutters unbearably.
4090 and some wobbling at the top of the mountains.
I use VD, VDXR, SSW, goldlike 90, snapdragon. No OpenXR Toolkit.
No wobbling now with 120 Mbps instead of 200Mbps.
I have a 4090 and 13900K and use VD with the quest 3.
Initially the “wobbling” with SSW on in VD was awful so I turned it off.
Then there was the beta update and it’s much better now but still noticeable.
I am running godlike, TAA 100%, 120 FPS. I turn on SSW when I get any dip in performance but otherwise have it off in the air. I am getting 45 ish FPS with it off. I use everything at ultra and TLOD/OLOD at 400/200.
I am flying small GA aircraft however. I recently tried the F18 out of JFK and these settings were unplayable. I would have to go down on in game settings and switch to DLSS in that case, but since I am using the simulator for real flight training in my local area it hasn’t been a big deal.
Hi. I have the same spec setup as you and am also using vdxr, but my settings have to be much lower than ultra and your lod settings to get 45fps without ssw. If you can find the time at any point, i would love to know your full settings, as in hags, nvidia panel, game, vd and toolkit. I know that’s a big ask, but i would love to be able to replicate your performance. Thank you in advance. I am running with a dedicated Wi-Fi 6 router also, so i should be able to copy your settings exactly, fingers crossed!
Yes it took a while, also keep in mind I am flying in rural Arkansas, but I do fly through the city. If you are at a busier area you may not get 45.
Here is what I can think of that I did:
I use a timer resolution program set to 0.5ms, no idea if this helps.
HAGS is on
Nvidia control panel everything default except maximum performance. I also set that video RTX enhancement to quality level 4 but only did that recently so it’s likely not contributory.
I no longer use steam VR, am just using the VD-OXR for the runtime. I am not using the OXR toolkit, I didn’t see that it helped.
TAA 100%. On my old quest 2 I used DLSS quality but I am getting much clearer images on the Q3 and performance not suffering.
Wi-Fi 6e router on my desk next to me, dedicated and connected by Ethernet, nothing else connected.
All in game settings on max. If I run into little stutters I start by turning the TLOD/OLOD down. If that doesn’t help I put TAA at 90. I set bloom to off because I used to get this annoying white blink and it’s gone when that is off.
Godlike, snapdragon on, and I set it to 120 fps. I have tried SSW and it seems better now but I get some wobble on the horizon. I find when low to the ground I like it but up high I turn it off. Keep in mind if you’re set to 120fps it will be on always.
I also start the VR session after the flight loads and I am in the cockpit in 2D, that seems to help.
I also don’t do much with live traffic and weather but I have all the AI ground traffic on. I turned it off but it didn’t improve performance.
I do get pretty high latency still, up in the 70s most of the time, so it’s not completely buttery when I move my head. It improves when I use DLSS quality though, but like I said TAA for me is much sharper.
Be sure to uninstall any oculus software your PC is running that was giving me CTDs.
My initial experiments with Virtual Desktop were with little knowledge or consideration of the Bitrate settings and this seemed to be messing up the image quality so much, hence the reliance on Link to get at least some sub-optimized stability.
Tweaking Bitrates and following your suggestions on leaving resolution alone in XR Toolkit, Godlike Mode and DLSS Quality indeed makes it a different world. I mistakenly thought “Godlike” was reserved for the 40 Series owners out there.
Probably still need to invest in a new standalone router to get the next performance inprovements but you’ve helped put the sheep back into the Yorkshire Dales for me for now! (Royal Air Force Fast Jet Low Level “Altitude Calculator”: 500 feet AGL = Cows have legs, 250 feet AGL = Sheep have legs).
Hi. I’m thinking about whether I should buy a pico 3 neo link VR headset. What do you think, will this work satisfactorily with my PC: Gigabyte B550 Gaming X V2 Motherboard, Ryzen 5600X CPU, Gigabyte RTX 3070 GPU, Corsair Vengeance 32GB RAM…? Or should i generally forget the idea, using a VR headset with this GPU and CPU? I fly mostly VFR with smaller planes… Thanks!
Don’t know about the Pico. But I had a RTX 3080 and I had to lower my settings in VR. I just went the easy way : a 4090 and a i913900k…because once I tried VR, I could not fly in 2D anymore…
I don’t have any experience with the Pico either, but I was able to run VR successfully on a 2080 card (reduced settings, of course) so I know it can be done. Even at reduced settings VR is superior to 2D in my opinion.
I am about to pick up my Quest 3 later today. Will be building a gaminging PC in a couple of weeks and looking at the components. My plan is to use i5-12400F and RTX 4060 combo mostly due to this new AV1 codec only being supported on RTX 4000 series (and Radeon 7000 series).
But I read different posts saying that 4060 8G is a crap and should be avoided and that even RTX 3070 12G is a better choice.
Can anyone in short explain whats the thing about this AV1 codec and in which configuration/Setup it is used when playing MSFS on Quest 3? Wireles or wired maybe? Do I need AV1 at all?
AV1 is used by Virtual Desktop (wireless), you need to go for the most powerful GPU and COU you can afford because that will decide your visuals and performance before its even sent to your Quest
Then I will start with my AX86U and see if I will need 6E
So the cable variant is using the so called Link cable. I just picked upp my Quest 3. Let the fun begin? Is there a good guide on how to get started and what to intall? In a nutshell ?
Register your Quest.
Then get Virtual Desktop on the Quest store (NOT Steam as it is not for the Quest). Install VD on the Quest and download/install the VD streamer app on your PC.
And you are set…Start VD streamer app on the PC, start VD on the Quest, and start MSFS (do the settings for VR and key binding for switching to VR in MSFS)
Hi @Strubenator4868 just wandered if you found any further improvements with SSW and VD. I’ve stuck with it for a few weeks and I’ve finally relented. It’s not good in MSFS.
Everything is fine in normal level flight, looks good too. The problems start when you pitch or roll (bank) the plane. Assets streaming horizontally past the plane seem fine but whenever there is vertical movement, it ends up a bit of a mess. Complicated geometry is worst, like trees and lines on buildings. You get a distinct fuzzness to the assets which I’ve not seen in a reprojection system before.
I had put this down to a reprojection effect and not VD. However I bought a link cable JSAUX which has data and power and basically removes any battery concerns and the native AWS on the link cable is great in MSFS - not perfect but no show stopping graphical glitches to put off me flying.
From now on, I’m using the link cable and AWS for MSFS, VD is excellent and I’ll continue to use if for PCVR especially with titles I’m standing up, it really shines with that wireless usecase, but I can’t use it for MSFS anymore.
Interesting! I suppose it depends on the PC (and the settings in VD).
On my system (7800X3D UV, 64GB, 4090 OC/UV, WiFi 6E), VD performs much better than the Link cable (orig. Link cable). And SSW does not creates wobbing. I use H264+ at 300Mbps, no snapdragon, no buffering, no dynamic bitrate.
Interesting, you had issues in VD? I had no sound with the link cable using the Quest 3. Manage to fix it though by running the oculus-driver.exe file again and boom, sound was back.
I tried this, it seems slightly better but the shakey fuzziness of the trees and buildings around 500 meters out from the plane is still there using SSW. Thanks for the reply!