Q3 with 4080S here. I’ve found that FS24 is acceptable only if the rendering is at native res. that is 2064x… So supersampling + DLSS is the only way for me. 4000x… and Performance preset with profile F. I can keep 45fps stable and perfectly read glass cockpits.
The main upgrade from G2 to Q3 is all due to the much better pancake vs fresnel lenses though. Nearly all other aspects are a downgrade (minimally via resolution and a little bit due to compression).
Having owned Rift S, G2, Pico4, QPro, Aero, briefly Crystal Light and now VR1, I can tell you the step from ca. 2000x (Q3, G2, Pico4) to ca. 2880x is MASSIVE, and the displayport helps a lot to.
People going back to Q3 from any Crystal would most likely be due to one or more following reasons, I would bet money here:
- Prefer the pancake lenses over the aspherics (can’t blame them)
- Crystal lenses had quality control issues (they often do)
- Couldn’t get decent performance in Crystal or not working properly at all
- General jankyness of Pimax build quality and software
- Didn’t like the ridiculous form factor of the Crystal
Both the resolution and QLED panels themselves are a huge step up for the Crystal vs Q3. The image is night and day difference when everything is working as it should.
I just went from 7800x3D to 9800x3d for FS2020 VR and in anticipation of the 5090 and it’s a really noticeable difference in smoothness due to the improved lows. CPU frametimes are lowered by 2-3+ milliseconds and I can run higher terrain LOD.
Beast of a chip! So the jump from the 5800x3D should be amazing.
1 Like
9800x3Ds are still not easily available here in Oz, at least at non-scalper prices. Plus I’m curious to see if higher core count x3D chips will work better with FS2024’s new CPU multi core utilisation, even though AMD’s 3D L3 memory maybe isn’t as efficient as on the 8 core versions. So I await reliable reviews.
The 5090 though, oh yeah. The 4090 was the first time I’ve owned a top tier GPU and I became hopelessly hooked. So once again, a mad rush to hit add to cart and then complete the purchase from fair a priced vendor, before the likes of you beats me to it, lol. Then I’ll sell the 4090 to get back some dosh for upgrading the CPU etc.
I know, we’re all nuts. 
Yeah they’re super scarce here too, I ordered weeks ago and finally got one at just slightly above MSRP.
I was going to wait for the more-core ones too but apparently it’s a bad idea to use both standard CCD and 3D CCD in one game due to increased latency, so I decided to keep it simple. Reviews will be interesting though, to see whether they confirm this effect.
Just to check, when people say to use DLSS Performance preset F and supersample to some high resolution, do you mean on OpenXR Toolkit > System > Override Resolution > Display resolution (per eye) setting?
Yep that’s the best and most granular way to do it.
2 Likes
Q3 + VDXR, 4090, 9800x3d, 64GB Ram, 500mbps fibre, I can hit 38 - 40 fps with TAA over London @ 1800ft, my performance tanks at Heathrow even with the above spec, there is something amiss for sure
1 Like
I have a very strong feeling that something is not right. In VR I can look in different directions and the frame rate changes from 40fps to 20fps, where I can see no real difference in what’s being rendered.
6 Likes
I’ve heard several people report this
2 Likes
Hey guys, new to this thread. I bought MSFS 2024 a week ago but only had chance to try VR last night.
I have 13900K, 4090, 64GB 6000Mhz ram and a Quest Pro.
I have changed no settings so far, default ultra for flatscreen and whatever VR is on standard, albeit I have TAA enabled as I hated DLSS with MSFS 2020.
It looks great, and runs smoothly in the air, but when I get down to about 200 feet it turns into a slide show. Walking around feels like 10 FPS.
Also, in both third person plane mode and first person walking mode, on sunny, cloudless days I get this hugely annoying texture sky flicker emanating from the sun that makes me want to stop playing. Interestingly, I started to get this in late 2023 with MSFS 2020 so it’s a problem that has carried over.
I’m wondering if it’s related to either my Quest Pro and some configuration setting, or my GPU?
Along with the terrible performance below 200 feet and at ground level it makes the sim unplayable for now, although flying around Dartmoor and walking around the tors I was blown away by how good it can look. The sim certainly has potential, but it feels very janky at the moment so definitely looking for a settings guide!
Also, I have terrible pop in. Flora and fauna don’t show until I’m a couple hundred feet from the ground, at which point they begin and the slideshow starts. Animals depict as stationary until that point, and then suddenly start running faster than the cars move back and forth in all directions. I landed in a field with some pygmy sized cows that just glitched round and round in a circle. Is this just me or are these animals broken? I found another creature that looked kind of like a sheep, but not a sheep that actually exists, like a sheep with bear fur rather than wool. Kind of ■■■■■■.
I am running completely default, vanilla so far with no add ons at all just to test.
One big bonus, not a single CTD in six hours of tinkering, MSFS 2020 was never stable for me so that’s a win.
Main issues for me, terrible, appalling performance at ground level and unbearable texture sky flicker issues still not resolved from MSFS 2020 in third person and walking mode.
Any suggestions welcome! Thanks!
Flickering blue sky I too had with Q3 connected via link cable. With VirtualDesktop no such problems.
Animal animations and car animations are truly ridiculous and need to be fixed.
Well my G2 is still working, and the performance is really impressive in FS2024, much smoother than in FS2020. Apart from the obvious bugs, which are annoying, I really enjoy the sim, especially the enhanced lighting, but the thing I am missing most is being able to download my stuff from the Marketplace.
1 Like
Do you use the debug tool?
Same here but sadly Link is smooth, while VD was smooth mostly
with Quest Pro, however I seem to get micro stutters again every second here and there, I check the overlay and FPS decode encode etc remains same when micro stutter happens (can notice it as you watch the ground as you move along in external view) the network MS goes from 5-6 to 0 or turns yellow even its a normal number. I guessed the updates have added some network issue (I have dedicated band on 5ghz and no one shares channel as me) excellent connection strength at 2401 etc. It still happens in either 20/24 even if I choose potato graphics vs my godlike 4090 etc. have not touched settings since it worked fine before on graphics VDXR HD 264+ at 200 bitrate (400 would cause more stutters originally, then 200 eliminated it originally) It is flyable in VD and I will not focus much on it if I am in a cockpit, but if I am playing around with external even on a slow plane, I can see the ground move nice and smooth for a few seconds then shake then back to smooth. It gets more annoying around rocky or mountain areas. I guess either my nvidia driver or VD updates must have made some adjustment. I need ASW always on to really play in either link or VD, if I play with it off it is more stuttery even with a 9800x3d/4090. I never could enjoy FS 20/24 with ASW off regardless of link / air link / VD
I never said native render is panel resolution. Headsets absolutely DO have a set 100% render resolution that is sent to the runtime. That’s how Steam knows what 100% is.
Im using Open XR toolkit. It does a LOT like FFR and upscaling. it also has FPS overlays.
1 Like
I never claimed that you said exactly that, but you said an HMDs native resolution is the panel resolution. Which is true in one sense but wasn’t really relevant in the context.
I guess we have a “native” panel resolution and a “native” (AKA “100%”) render resolution (really just a value chosen by the vendor).
Hopefully we can agree on that.
Agreed, but I definitely know that the panel resolution is not the render resolution.
I never denied that!