TheFamilyMan

Congrats on your upcoming build, hope it comes together smoothly. I built my computer last July, just before the RAM shortage hit. Got my 2x32 kit for $230, and 5090 for $2700 (which was an insane price regardless, but dang no regrets, that card IS Mr. VR). As to why: Perhaps a bit of hyperbole on my part here, but check this out. Sorry if this hijacks the OP.

Pimax is just starting to ship out its Dream Air product line. A friend of mine is schedule to get his Dream Air ($$$$) next week, and I got notice that my preordered Dream Air SE ($$$) is now awaiting customs for international shipping. Hoping to get it in 4 weeks or less. That being said, thanks to AI the future of home high end DIY computing is disintegrating before our eyes. Though these small form factor HMDs with amazing OLED displays and next gen optics are ushering in the next age of VR, in a year or so very few may (or possibly even can) be building the computers needed to drive them. I imagine Pimax is taking note of this, a huge bummer to say the least.

Seems my deep link for the true fix for the crazy huge G2 artifact bands and triangles wasn't deep enough. Here's another go at that link, for all that really want to perform the once and forever done fix for this G2 artifacts problem: https://github.com/mbucchia/Oasis-Driver-for-Windows-Mixed-Reality/wiki/Known-Issues#visual-artifactsblocks-hp-reverb-g2-only-fix-in-preview-branch Got to love its rather Star Trekian problem description (slighted edited):

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.