TheFamilyMan

Wow, I am really looking forward to this. I live a few miles from Moffett Field, and for many years KPAO has been my MSFS home field. To have those hangers in MSFS 2024 is dream I've been hoping to have realized for years now, THANKS!!!! Nice touch that you've included the Ames wind tunnel (seen in the background of your 4th update picture)! Dang....can't wait!

Seems you missed reading the post I made recently. Nothing is permanently fixed by moving the ipd slider.

Had really bad artifacting stuff happen with my G2 a few months ago. This fix completely took take of it. Edit: Before doing this fix, fiddling with the IPD slider fixed it (that is until the next time I started it up).

Just making sure here. There is a pairing button that's under the battery cover of the G2 controller that has to be pressed when Bluetooth pairing the controllers to Windows. Also, when you get your controllers paired, all you need to do is rerun the Steam Oasis app and set up the driver to use the controllers. Happy Contrails...

My two cents: Pay close attention to the details of setting up the Oasis driver. Be sure to Bluetooth connect the G2's controllers to Windows before setting up the Oasis driver. Having to run its Steam app, i.e. set up the driver, more than once isn't a problem. Run the G2 at 90 htz and limit FPS to 45 using MSFS 2024 or an external tool such as riva tuner statistics server. This gives smooth head motion while providing headroom for higher graphics settings, but with an occasional, as in seldom, stutter outside the aircraft. No need to reduce resolution of anything with your high-end hardware. Make sure you have the IPD adjustment set for your eyes' IPD, and experiment with your facial fit to get your eyes in your G2's sweet spot. This can be tricky but when you find it all looks fantastic, i.e. sharp and clear, but it's a rather small area. To look around your VR world you'll need to move your head for the clarity of the visuals drop off considerably when your eyes look outside of the sweet spot. Get used to this limitation, yes it sucks but worth it overall IMO.

No. IMO what you are experiencing is the ideal situation for running VR flightsim. The graphics power needed for driving a Crystal Light is intense. When I run VR with my G2, I've tuned my MSFS graphics settings to get the GPU/CPU performance you are experiencing. I do this because I want the best possible image quality for my G2, thus I want my 5090 "pushed to the wall" performance-wise to deliver that eye candy. This is the only reason why I bought it...I WANT MORE! If you have Windows HAGS enabled, disabling it may achieve this goal but probably not in a manner that'd make a big difference. Basically, you are fine! But I'm assuming you are happy with how your CL is performing. It's easy to reduce graphics use: turn down MSFS graphics settings and/or reduce the resolution you use for your CL. But IMO doing stuff like this basically nixes why anyone would want a high end GPU. Don't worry about driving your GPU at 90% utilization (less it's constantly temperature and/or power throttling), and enjoy the glorious performance it's delivering for you. If you are having problems with your GPU temperature and/or power throttling, you most likely have a problem with case airflow or maybe your GPU's heatsink is having problems such as a bad install, failing fans, or incorrect driver settings.

Is it just me, but dang, this place is now heavily spammed with ads. Pretty much I have reached my wits end dealing with it, both on my computer and cell phone. Did I miss the memo on getting a reoccurring paid subscription to have them stripped off? Whatever...

The limited fov of VR is an easy thing to complain about. I remember grumbling about it when I was a VR neophyte years ago. But I now gladly ignore that deficiency, and fully embrace the beauty and joy inside my 5090 enabled virtual cockpit's fully 3D view with it amazing detail everywhere. Dang, IMO it is miraculous the technical feats that VR HMDs and software have conquered. Sure, the more fov the better, but I'm not going to pine about it anymore.

The experience I had with a prototype Dream Air showed constant judder running DCS. Judder is the effect that all motion, including moving your head to view a different part of the cockpit, looks as if the animation consists of a very quick succession of still frames, thus there really isn't any smooth motion unless you remain perfectly still (hence no motion other than the distant scenery outside the cockpit). fakeoptimism (or any other Pimax HMD user), does this describe the experience with the Dream Air if MSFS can't sustain it's native frequency?

If "it" is a VR app, e.g. MSFS, "it" is actually pushing about 1.5x the pixels listed above. This supersampling pixel overhead is necessary to compensate for the barrel distortion of the HMD's optics.

It's disgraceful to say the least...and an excellent job of "grinding the axe" by the reviewer. The reviewer mentioned that he's told Pimax about his mod, and considering his online prestige concerning VR and FS, I (hopefully) can imagine the chaos that his mod is stirring up at Pimax.

Lately I've also been getting an occasional 1-2 second black screen in MSFS 2024 with my G2. Sometimes none at all during a flight, other times 3 or more. What is concerning is that my realtime GPU load plot doesn't show a dropout when one occurs. A friend of mine has lately seen this as well.

That OXRTK mod (now at 1.3.5) solely consists of replacing a dll in the OXRTK's directory. Its download doesn't provide anything but that dll. I have no use for the mod, but for those that do, enjoy.

I assume you tried reinstalling it to no avail, bummer that you lost its use. The OpenXR toolkit's author, mbucchia, has taken down both its documentation and download link from github. Obviously he's serious about no one should use it anymore, though I currently still use the OXRTK with MSFS 2024 but solely for its super convenient FPS display in VR with my G2.

My 2020 install was moved to an ancient 500GB sata SSD to free up my MSFS dedicated M.2 for my first ever 2024 install, about six months ago. I think I've run 2020 maybe 2-3 times since them. 2020 will go when I get around to futzing with Linux again, which was the previous sole occupant of that sata SSD on my prior build. Thanks for reading.

The Dream Air they had for their San Jose, CA demo had a kludged, uncomfortable head strap that was nothing like the final strap. Other than the DA's very excellent 8K panels, the lack of eye tracking along with pretty much everything else I was hoping to see was very disappointing. I have a DA SE preordered, though I'm seriously thinking of either dropping the order or upgrading to the full DA. I can live with the G2's marginal sweet spot and washed out blacks and colors, but it's smoothness is very good running at 45 fps with the Oasis driver. When running the DA at 45 fps, if every head motion results in a judderfest, even with its vastly superior visuals, I'll probably pass on it completely. BTW, I did pay extra for their return for any reason with free shipping option.

I've yet to give this a try, but IFAIK the Reverb G2 (even with its Oasis driver) automatically runs depth reprojection to generate interpolated frames to fill in the 90 hz refresh rate frames for the ones that the host doesn't generate. Note that this is not the same as motion projection, but it's very similar and completely automatic as mentioned. To get judder free VR motion with a G2, it's best to frame limit it to 45 fps, so the interpolated frame rate is consistent with the host's generation of new frames. A question I've asked a few places that never has been really answered: does Pimax software do this automatic depth reprojection? I know that Pimax has "Smart Smoothing" which I read is either not available, not working, or is dreadful when it does. I'd guess it's a form of motion reprojection, which BTW can still be enabled for the G2 with the OpenXR toolkit. Bottom line here is if Pimax only implements reprojection via its SS, I can see Nvidia's Smooth Motion, i.e. a depth reprojection workaround, of great value to Pimax users. I demoed the Pimax Dream Air several weeks ago. Judder was constant and painfully obvious. I was hoping that is was a side effect of the prototype environment, and not the way things are with Pimax HMDs when they aren't driven with refresh rate fps by the app driving it.

I wonder that too. In VR with my 5090, DLAA gives me the best image quality for the aircraft I sim fly, but with with the new driver and DLSS 4.5 FPS was noticeably less. After giving DLSS Quality a try, it was at best a wash compared to pre-update DLAA. Ended up reverting back, for MSFS isn't the only thing I run.

I tried DLSS 4.5 with the 591.74 driver. There are improvements there, but none that I really need for my VR flying. In fact I got somewhat lower FPS so I reverted back to 580.88 and DLSS 4 and got the FPS back. Every driver I've tried since 580.88 has been like this with my computer, see my sig. Hoping that it'd be different this time, oh well. Now back to sim flying.

One behavior of VR that gets overlooked is that the resolution actually rendered by the app, e.g. MSFS, is usually about 1.4-1.5 times the HMD's resolution. This is for the supersampling that's necessary to correct the barrel distortion inherent in VR optics. I agree that foveated rendering really makes a significant performance improvement with very little cost to the visuals. Been using it with my G2 for years, first with the OpenXR toolkit and now with MSFS 2024's implementation. IMO not using it is leaving FPS "on the table".

I fly exclusively GA. Pre MSFS, I used fly planning software to create VFR plans with 1-2 days of 4-6 hour flight with "nightly" layovers. I'd fly the plan over about a RL week or so, depending on the time I had to spare for sim flying on any given day (.5 to 2+ hours). All this came crashing down with MSFS and its essentially non-existent "save flight". I never really got over it, so I do far more goofing off flights now (and no way would I go back to FSX).

I sim fly using a HOTAS controller with 3 hat buttons. One hat is dedicated to moving the drone camera, and a separate button to toggle it. Clockwise motion it's up, left, down, and right translations. Alt clockwise motion it's pitch down, yaw left, pitch up, and yaw right. With this I can get the exact external view I want somewhat quickly, though it took a bit of practice to learn. Being on my HOTAS it's always right there, and great in VR to get a quick outside view to admire the beauty of it all for a moment or two.

20 years ago, this is what was being said about TrackIR. At least its cost of entry was only $150, a bargain compared to VR, but obviously not a fair comparison. BTW, been a VR convert since 2021...no looking back! Got a Pimax Dream Air SE on preorder.

Nice to read your story. I've seen too many Q3 owners go over the top on "its superiority" due to its lenses. Not to be too judgemental here, but there is a saying in data and video processing: GIGO (garbage in, garbage out). BTW, I'm not calling the Q3 garbage here, just that its limitations can't be overcome by its optics.

I had this problem too and found that the above fixed it, via reinstalling the Oasis driver. Even had the same updated driver install trigger. I posted this problem and solution the Stream Oasis driver forum. I've yet to install a new driver since then.