cmorg

Thank you. It's been quite ugly, but my wife and I have been fortunate to have intermittent power and heat. Our longest outage was 11 hours. Some people have gone days. It's awful. I'm looking forward to distracting myself by reading all your reactions to the update!

Will have to wait to download until we have reliable power here in North Texas, but keep updating on how it works out!

Thanks to both of you!

So it has to be done by key bind? Good to know. I knew it was a pitot problem but the switches weren't clickable for me. Thanks for the help, Manny. I'll give it a shot.

I've had three flights in a row now where airspeed bounces between something plausible and a flat 30 knots. No rhyme or reason for it, through all stages of flight. Interestingly, mach and/or groundspeed seem to read out fine. It seems like the probe/pitot heat switches are inop. Any one have any idea what I'm doing wrong?

RR never fails to crack me up.

While this would be a neat feature, I think the vast majority of the tubeliner folks here would disagree with you about it being a limited experience. I, for one, have had some of the most fulfilling simming experiences (and fun) in things like the 727 where the workload is high because it was designed to flown by three flight crew.

I'm interested in this as well. It was my understanding, at least early on, that this was a current limitation of the MSFS flight modeling.

I've yet to test it myself, but I do remember initially being very confused by what seemed like extreme performance impacts on P3D. I can't recall now what I did to fix that, but if I remember I'll drop back in. But it was fixable in P3D, don't see what it wouldn't be in MSFS.

I've done the same thing now that I know that this is information I need for future updates. ORBX doesn't give you that information when you purchase. Having bought through ORBX, I assumed they'd push the updates seamlessly as they have with many other products I've bought through them. Didn't think I'd have to go hunting for a serial key, but alas, here we are. Pretty cumbersome process, in my opinion. I'd rather just be able to update through ORBX. If I had known that this would be the required method, I would have bought directly from REX so the developers didn't have to give up part of their cut to ORBX. @timest, any comment? Did ORBX not push the update or is this a limitation we have to live with when we buy from someone else?

Any one know how to obtain serial number for installing the updated version if purchased through Orbx? Edit: Figured it out. Had to open the profile.xml file to find it. In C:\Users\[yourname]\Documents\REX 6\REX Weather Force

Download the rest from content manager.

I've seen this widely reported (here, reddit, discord) as being the fix for that issue.

While I've not tried it with MSFS yet, I had great luck with a program called OVRToolkit in P3D for bringing in desktop windows into the VR environment, with the ability to move/resize/curve etc. Very active developer. Relatively cheap on Steam. Used it for a lot of things, but mainly charts and vPilot. Some good preview videos on youtube.

Try it with DCS, XP, or P3D, if you've got them. I also find Star Wars Squadrons (a good test for motion sickness) and Hotdogs, Horseshoes, and Handgrenades VR (H3VR) to be fun guilty pleasures.

I'll drop back in with feedback when I get mine. I'm running a Ryzen 7 2700X and 2070 Super (in the 3080 step-up queue--might be a while). I was totally happy with my Rift S in P3D/XP VR, but can't wait for the improved resolution and to ditch the ridiculous facebook account requirement.

I've heard of people's G2 orders shipping within days recently. I pre-ordered rather late, early November, and mine is scheduled to be delivered tomorrow, which is just in time.

[DELETED]

Do you have the proper descent rate set in the top left corner before you file your flight plan? I believe that box changes the TOD distance from final destination. If I recall correctly, you can't directly change the TOD point except by changing descent rate. I've forgotten to set that before and have been fine by requesting descent from ATC.

P2ATC definitely requires FSUIPC7, the free version is fine. Clumsy has a good video detailing the setup. I've had few problems with it, not even frame drops.

The update on the 22nd is a sim update and I believe it's primarily for VR. I believe there will be additional things as well.

Picked up KPHX. Quite pleased with it, looks and performs fantastic in VR, too.

Good to know. I'll have to look up the light sensor fix. I'm new to VR with P3D and am not familiar with that but have read about the white box in the HUD issue, although I've never experienced it personally. I'll also experiment with some other things, I think using OVRToolkit and trying to overlay Navigraph Charts windows may be having an impact as well. I'll also try using different addons that I've not gotten around to installing to 5.1 yet like the QOTSII, FSL busses, and the Dash 8. In general I'm typically seeing spikes of 0.4 gigs of VRAM each entry, and leaving VR doesn't seem to release that VRAM. There was one relatively old post on the P3D forums about it but only one or two responses confirming that other users were seeing the issue too, but no fixes and no acknowledgment from LM. I'm sure it's something that specifically affects only certain users since with the VRAM issues already present in VR and 2D use of P3D, I'd imagine we'd hear a lot more about it if was a widespread issue.

Much appreciated, Pete. I did have an NVIDIA driver update and a couple of Windows updates, testing now. I'm using the NGXu for the most part, seems that every entry to VR mode utilized VRAM that it didn't totally release upon exit, and the cycle continued until CTD (after notification from P3D, giving option to revert to default settings, which I opted for and still CTD). -Chase

Interesting. I'll check for driver/Windows updates. It seems to happen to me when switching between VR and 2d monitor mode through the VR menu (enabling/disabling VR to do things like make changes in FMC or utilize GSX menus, etc.). Thanks for your input!