Quest 3 and MSFS - please make reports here

User Support Hub Virtual Reality (VR)
61

Like several of you, I was a Q2 user, and now a Q3. I have a 9700 K at 5 GHz plus a 3080 TI so quite a bit less of a system than you 4090 folks. I too am interested in clarity, but I fly low and like to see out the side window so I typically use either ASW or SSW with VD. We all have different flying focus issues.
A couple of Tips:
I’m old enough to have gotten cataract surgery this year and my vision is really quite clear close in so I didn’t imagine that I would need my glasses at all for the Q3, However, I found that using my new glasses that still improve my far vision help the clarity of the Q3. Therefore, I suggest that you make sure about your own personal vision quality by getting a current eye prescription for whatever focal length the Q3 has, which I imagine is, something like one and a half to 2 m. I’m going to get the Q3 prescription lenses available from zenni.com at $49 especially since that will protect the Q3 lenses from scratching.

Second tip to possibly try out DCS World(free) with your hardware as I do especially since it now supports openXR and VDOXR on their multi threaded version. I switch back-and-forth between MSFS and DCS. DCS has a lot faster frame time since it has fewer calculations per frame so it’s actually possible to get to 72 or 80 frames per second and see what that looks like in comparison to MSFS. Unfortunately DCS does not have good antialiasing but I learn comparing the two sims. With Link cable, I can get amazing crisp images as well as fluid sideviews.

1 Like
62

Hi - I’m running a 4070 and 5800X3D on the Q3 , and really like it. It replaced a Rift S.

I’m running Oculus Link (cable). Image is clear running mostly medium settings and 1.1 render scale in the Oculus app, with DLSS. Reported frame rate in debug tool performance overlay hovers around 72. Very smooth. I know I can tweak visuals higher and fix the frame rate to be a bit lower, but I’m tired of tuning for the moment :slight_smile:

One question - I actually don’t understand the performance PROS/CONS between running Oculus Link, Oculus Airlink, Virtual Desktop (with or without STEAM), OpenXR, etc…. I’m fine being cabled for MSFS, so I presume Oculus Link is best for me.

I see a lot of posts on Virtual Desktop. I don’t even have that installed, and not sure I will. Am I’m missing something?

Thanks!

1 Like
63

Just a quick update from my current round of testing and tinkering.

Currently having some pretty nice performance and clarity using (cable) Link speed 960mbs in ODT, 72hz and 1.0 render resolution in the Oculus desktop app, Turbo mode and oversampling to 2850x??? in OXToolKit, DLSS Quality, 150 TLOD and 115 LOD - DX12.

Performance is a little less butter smooth than I was getting with the Quest 2 so I still need to play around, but overall I’m very impressed with the visuals in the Quest 3.

The annoying thing is that even when experiencing a few frame drops, neither my CPU load (on any thread - 13700K) or GPU load is maxed - GPU seems to run at no more than 60% usage (4090) but scaling up the image just causes further frame drops so I guess it just be something to do with the stream compression / decompression.

I’ve tested lower connection speeds (250, 300, 350, 400, 450 and 500) but I personally find 960 to be the smoothest which seems counterintuitive - I also seen to be lucky in that I haven’t seemed to suffer audio issues like some of the other users on here.

I’m also aware that I’m using a mix of upscaling and DLSS to get back to a resolution! I just don’t find performance with DLAA or TAA to be as good strangely. Again, I still need to tinker.

64

It boggles me how anyone can live with the insane loss of detail with DLSS, even at quality.

2 Likes
65

It depends on what your requirements and tolerances are I suppose. I’m personally finding not much difference between what I’m currently running and TAA or DLAA, I actually prefer the slightly smoothed out effect over TAA or DLAA as it seems more realistic to me - but then, my eye sight isn’t 20/20 so my view of the real world isn’t razer sharp anyway :face_with_hand_over_mouth:

1 Like
66

Here are my specs and settings I am very happy with:

Intel(R) Core™ i7-10700KF CPU @ 3.80GHz, 32 GB RAM
Bios: XMP on, Resizeable Bar on
Windows 11 Pro 22H2
Core Isolation, Game Mode & HAGS: Off
DLSS 3.5.10.0 (DLSS Swapper)
WIFI: 5 GHZ (80 Hz)

NVIDIA RTX 3080 (12 GB)
Driver Version: 546.17
Shader Cache: Deactivated
Anisotropic filtering: 16x
Antialiasing Gamma Correction: On
Power management mode: Normal
Low latency mode: Ultra
Texture Filtering - Negative LoD Bias: Clamp
Texture Filtering - Quality: High performance
Texture Filtering - Trilinear Optimization: On
Threaded Optimization: On
Vertical sync: Fast
Pre-rendered VR frames: 1

Virtual Desktop 1.29.10
VR Graphics Quality: Ultra
VR Frame Rate: 72 fps
VR Bitrate: Max
Sharpening: 100%
SSW: Disabled
Snapdragon, Video buffering, Increase color vibrance, Increase video nominal range: On

Virtual Desktop Streamer 1.29.10
Prefered Codec: HEVC
OpenXR Runtime: VDXR
Automaticly adjust bitrate

OpenXR Toolkit:
Upscaling/Sharpening: Off
Fixed foveated rendering: Preset
Mode: Quality
Pattern: Wide
Turbo Mode: On
Display resolution (per eye): 3320x3439

MSFS2020:
DirectX-Version: DX11
VR:
DLSS: Quality
Reprojection Mode: Off
T-LOD + O-LOD: 105
Off Screen Terrain Pre-Caching: Ultra
Terrain Vector Data, Trees, Grass and Bushes, Volumetric Clouds, Windshield Effects, Light Shafts: Medium
Buldings, Texture Resolution, Texture Synthesis, Water Waves: High
Anisotropic Filtering, Ambient Occlusion, Raymarched Reflections, Bloom: Off
Texture Supersampling: 2x2
NVIDIA Low Reflex Latency: On
Contact Shadows, Glass Cockpit Refresh Rate: Low
Shadow Maps: 768
Terrain Shadows: 512
Cubemap Reflections: 256

MSFS2020 SU14 (1.35.21.0)

Maybe it helps somebody.

14 Likes
67

Well that’s an odd one :slight_smile:

2 Likes
68

Yes… after comparing with 100% sharpening in VDXR I didn‘t notice a big difference and used that… maybe I should give it another try when I got. more time. Thanks!

1 Like
69

Thanks for posting this Ebi Devil. I have a very similar rig and have to ask how latency performance is for you while in the cockpit looking around. Mine is dreadful with the Q3 and just haven’t yet found a solution. My latency consistently averages between 200ms and 120ms. Can’t seem to get it under 100ms. Any thoughts or suggestions would be appreciated.

1 Like
70

Use the performance overlay of VD to see what causes your latency (it’s in the streaming section of the VR app). But it probably is your WIFI connection. At least a Wifi 6 router with a direct line of sight to your headset is recommended. You can also use a dedicated router for VR, connected by cable to your other router. I also think there is the possibility to use a dongle for in your PC. But there are people around here that can better help you with that I’m sure.

71

Best result with msfs for me with my i913900k/rts4090 and Q3 is to use Air Link with 200mbps dynamic bitrate, plaus 5mbps dynamic bitrate offset with ODT (seems to smooth out things). Also, with oculus desktop app device stettings 80Hz refresh rate and the res slider full right.

I’ve also found that adding 1.4 x SS with ODT, or OTT improves dlss/balanced to better than I
cans get with TAA.

Like everything VR, it;s up to you to find out what worls best for you imho.

4 Likes
72

Hello everyone, I know that coffee doesn’t exist for everyone, but today after almost 2 years with the Meta Quest 2 and 4 days with the Meta Quest 3, I have done something that I had never considered. I start by describing my equipment and my first impressions with my new Quest 3.
I have a computer with an Asus Z790 Hero board, with an i9-13900KS with DDR5 7600 Mhz 32 Gb memory and in bios only the XMP1 profile with a 2 Tb M2 WD Black SN 850 X SSD and all this with an Asus RTX4090 graphics card , I have had the equipment since January of this year and with the idea of dedicating it almost exclusively to MSFS with the Quest 2.
Well, for me the new VR was a little disappointing, well half and half, on the one hand there are positive points and on the other hand negative points, until a few hours ago at the airport I had distortions in rapid movements and sometimes instability, but in flight everything improves and arrives to normal. Also comment that I had slight but annoying sound interruptions. Thinking about all this, I come to the conclusion that at the airport the loading of processes can alter the stability of the viewer image, disappearing in flight.
I decided to do something that I had never tried before, I am going to make the sound not go through PC-Oculus, but rather the PC sound card and Surprise everything improved, before I used Directx11 and I tried 12, I increased the resolution of the Quest 3 at 72 Hz and at maximum 1.3 5408x2896 with an ULTRA configuration in 5 or 6 parameters, Buildings Clouds, etc. comment that in ODT I do not use the ASW (I will try) the Nvidia control panel, I disable everything I can (I will try) and in MSFS I do use DLSS with DSLA and although I have not thoroughly tested all this, there has been a change in the stability of the 3D image. I think that eliminating the sound process in PC-Oculus may have made there less load for this program.
In another order of things and I have only seen that a few have mentioned it, it is what consumes these glasses, it is as if there were no tomorrow, the USB A port is not capable of stopping the consumption, I doubt that 3 hours of I fly without the battery running out. For this I think I have found the solution, a cable for VR Glasses with a Hub, I don’t know if it is called that with a USB C parallel connector.
I would like at least one person to find this post useful.
Thank you

3 Likes
73

Dear, reviewing my PC audio settings, I discovered that I had activated certain sound enhancement functions such as EQ and sound boost, which may be the causes, I will try and comment. Thank you

1 Like
74

Latency is mostly under 80ms with this settings. Wifi-Router at 80Hz only 2m away.

75

I’m getting the same flashes if white that I got with the Q2, especially when moving the view a lot. Is this dropped frames, or something else? I’m getting decent fps and latencies.

Where do I start looking?

76

Thanks! this works great with my Rig 12700K 3080TI quest3 :smiley:

77

Try disabling bloom to get rid of white light flashes

78

I got my Quest 3 today and using link cable with 90hz, 1.5x on oculus slider(max). I am getting the same performance which i do get with Quest 2. Very smooth, no stutters and much much crisper image. Using TAA only.

7800x3d
3090ti

2 Likes
79

Just a sugestion; try dropping your oculus desktop device graphics setting Refresh Rate to 80Hz, with res slider still full right (at 80Hz it will then show 1.4x but that doesn’t really mean much). This should give you a bit more headroom and may even run smoother and/or let you increase a few msfs settings. like a tad more TAA res.

Another tip you may want to try is to increase your ODT pixel density to say 1.30 (default = 0) and instead of TAA, try dlss/balanced. Adding some super sampling beforehand improves the clarity using dlss (which can be a bit blurry). This may run even smoother and you should notice a lot less shimmering with distant objects, including approaching runways.

These are just suggestions, if you are happy with it as is then stick with it imho.

3 Likes
80

I’ve just traded up from an original HTC VIve to the Quest 3. Apart from not having the hassle of setting up lighthouses, I was really impressed with the performance. I’m using a link cable, and simply installed the Oculus app and OpenXR toolkit, started MSFS and I was all good. Big visual improvement from the Vive, smooth and the detail at the MSFS default VR settings was fine. My rig is an i9 13900KF with a RTX4080, 64Gb RAM. I didn’t measure precise frame rates, my feeling was ‘pretty good’. No artifacts or screen tearing, no black edges when turning my head, it all just worked. I’m quite impressed with the Quest 3.

3 Likes