AJZip2

I think AI is probably a bit out of date. When the Crystal Light was first launched in the back end of 2024, it was such a leap in VR performance of an 'affordable' product, Pimax were swamped with orders. Apart from pure availability, they also had to ramp up the production of the components - including the pretty special lenses. And - I may be mis remembering this - they added additional lens making suppliers...and there were problems. A relatively high proportion of units sent out had distortion in the displays due to poor quality of the lenses. Pimax set up a HUGE (in commercial terms) lens replacement service through their Crystal Light Discord sites and, as such, you could actually see the customers' requests and bug reports...and there were dozens and dozens. BUT - I've just looked at the support section of the Crystal Light Discord site and, going back two or three months cannot see any customer raising this particular problem. So yes - two years ago, it was indeed a big problem. But I'm pretty sure it's old news. (by the way, my own Crystal Light - bought fairly early - did indeed have that issue. New lenses were sent to me very quickly with no question or argument and they are flawless and have served me well ever since.)

Back to the mouse question, @Rob G , I use an old-fashioned wired mouse...I think I've had it around 10 years! The reason is that with all of my wireless mice/roller-ball/etc, there are occasions where I get stutters and delays between moving the mouse and the cursor moving even though the overall MSFS2024 VR experience is smooth and stutter free in all other aspects. I find that the wired mouse is much more consistent...although if I have ALL of my various addons running AND am silly enough to try flying on a 'popular' evening (think Friday Public Holidays, etc) or when there has been a recent rolling update, there still can be the occasional lag - but that is nowhere near as often as with my other wireless mice

New day, new (better) result. Call sign no longer calling my Boeing an Airbus. All seems good again.👍

An internet search throws up a recent Github package called FSCopilot that looks like a new kid on the block - but, as always with this sort of thing, tread carefully and do your research. PS ...and I don't know if it works in VR

Doing a quick search, it looks like VTOL VR also has a multi-crew option. So it must be technically possible. So I will up the hope factor...but I'm still not holding my breath

Yes - I was right - it's Condor 3. Here's what Google AI says: "Yes, Condor 3 supports two players in one cockpit (Multicrew) across two separate PCs, and both can use VR simultaneously" But - and again I can't remember the detail - I think there are difficulties in getting it to work quite as well as we would hope.

VR Multiplayer in one cockpit (2 folks using separate VR set ups but flying in the same aircraft and flight) is definitely in the 'Great Wish List In The Sky' for many players but I think it is a long, long way away even if it is at the stage of a mere twinkle in Microsoft's eye. It's certainly on my own wish list - but I'm not holding my breath. I'm trying to remember - someone came up with something that tried to do something along those lines but not sure it was trying to do the above...and I'm not even sure it was MSFS (delving into past memory - maybe was it Condor Soaring, the glider sim?)

Here too Used BATC for first time in a while yesterday and it added 'Airbus' in front of my otherwise correct call sign...I was flying a Boeing.

I too am a pretty much 100% VR user and use MSFS2024 and MSFS2020 multiplayer / FSHUD ATC with AIG live traffic / FS Realistic / Navigraph/ FSUIPC7 / Stream Deck + or, if it's a A320, the Wingflex FCU Cube: all running at the same time. The VR headset I use is the Pimax Crystal Light which is a pretty heavy hitter. For MSFS2024, I run DLSS Super Res on Quality, have volumetric clouds at ultra, TLOD at 300 , OLOD at 100. And, with tricks of the trade like the nVidia Apps' Smooth Motion, etc it's pin sharp in and out and stutter free. And I have 32Gb Would I like 64Gb to 'future proof'? Yes, of course So am I going to upgrade? No - not at the moment. No need.

...and Aeroplane Heaven have just put out a fix (which was already in the pipeline)

I've sent Aeroplane Heaven a mail with the issue and the easy solution.

Had a look at the camera.cfg file in the SimObjects folder. Yup - they have done the same as they did with the Hawker Nimrod...they have a spurious VR Camera 'Initial xyz' position there that is different to the default Pilot 'Initial xyz' position. I just copied the Pilot coordinates and pasted them into the VR line in the camera.cfg file, saved and now the VR default position is where it should be. I'll let Aeroplane Heaven know - hopefully they'll put out a hasty update...

Although not at the level of detail and switchability (ie, all switches doing something) as, say, Flying Irons aircraft, Aeroplane Heaven are producing some pretty decent WW2 British aircraft (Lancaster; Hurricane and now the DH Mosquito) which generally work very well in VR. But I'm experiencing a VR problem in the new Mosquito that I don't have in the Lancaster and Hurricane...VR pilot position. In 2D it's fine, but switch to, or start from, VR and it basically spawns me directly behind, and nose against, the pilots armour plating. Before I either log an issue with Aeroplane Heaven or tweak the XYZ in the config file, anyone else having the same issue?

Did you spot the discussion and solution above on a setting change?

Well, I was just about to post about my own flight, and declare that it was pilot error (I still think it might be) in that maybe my aircraft configuration (flaps, etc) weren't correct but yes, the result was some quite dramatic climbs and drops, hovering quite close to stalling point at times...but let me do a quick recap, because in all other respects it was a great flight: Route: EBOS Ostende Rwy26 to EGKK London Gatwick Rwy 26L (a short over-water route I use for most of my 'first flights') Flight Procedures: - Started from cold and dark - Successfully got the EFB to accept my Simbrief plan and load up and fuel up - Took off manually, turned on Auto-throttle and Autopilot then switched to NAV and then to VNAV early in the climb - The aircraft then pretty much took hands-off care of the speeds and the altitudes, including non-prompted initiation of descent - It was in the last 10-15 miles, as I was progressively lowering flaps and u/c that it started porpoising either side of the approach height, dropping throttle until it was below approach altitude while idling, to stickshake, to auto full throttle with reestablishment of speed and then overshooting height. BUT, to be honest I was winging it a bit in terms of when to drop the u/c and how much flap I was applying and when. I'm pretty sure that was why it started porpoising. Pretty sure it was pilot error in one of the few places I actually was doing ANY of the piloting - When in ILS approach range, I disabled the autothrottle and clicked APP (then at around 500' killed the A/P too) and it came down calmly and smoothly, following the glide path very well while it was still in A/P I have to say that - in spite of the porpoising issue - it was the best full VNAV flight I think I can personally remember doing.

Just completed a successful flight on my routine 'test' route, EBOS Ostend to EGKK London Gatwick in VR. No surprises - everything worked as expected and I made a successful ILS landing at runway 26L. In general, I would say that I noticed no PC performance issues at all other than, maybe, a little mouse lag when I was programming the MCDU - but I've noticed that on a number of aircraft so I think that is more likely to be my end and not PMDG's. I would say that, while perfectly happy with the discounted purchase (I had the 700 in MSFS2020), I wouldn't have actually known that this was a different model, either in textures or performance, if someone had booted it up for me and handed me the headset and controls. But overall, happy chappy.

So far so good here. I've just completed a short flight in 2D and everything was as smooth as a whistle. Later today I'll try a flight in VR on a route I recently did in the 600 version but very happy with it so far.

Yes - I fully endorse that. But if the manuals are not fully up to date (for example, I cannot find a full run through of the new EFB in either the FSS Documentation Hub or any of the many excellent and detailed video run-throughs) then folks can stumble a bit in the dark. And when folks are in the dark, they miss things and trip up over things. But, happily, we have an excellent forum here with folks happy to turn on their torches. But with that proviso, I do indeed fully endorse what you say. 👍

Excellent, @Fiorentoni. Many thanks, found it...and my 'disable lights' is now disabled

That is VERY interesting information. Many thanks...and yes, it does indeed make you do that 👍

The other thing not fixed - certainly for me - is that the flight panel button on/off lights (eg NAV/AP/HDG/ALT etc etc) don't light up. I had already raised this as an issue in the pre-Experimental version. Clearly it's not on their priority list and they have made it clear that no issues can be raised with the Experimental. But on the better, hopeful, please,please,please let this be a good sign, is that the VNAV system appears to be much improved...and I have a surprising example to back this up: SCENARIO - I booted up the E-175 from Cold & Dark - I entered the Simbrief Flight plan from EBOS Ostende to EGKK London Gatwick - I took off and, during initial climb engaged the Autopilot and VNAV - then the downstairs doorbell rang and the interruption lasted 2hours!! EXPECTATION My expectation, when I eventually got back to the PC, was that the aircraft would have crashed. That expectation was fully met. Crashed in a field. SURPRISE - The surprise was when I used the external view Yes - that pair of runways just the other side of the bushes is indeed London Gatwick. And yes - this was the planned direction. I have no doubt that if I'd been around to drop the undercarriage and click the APP button it would have also landed on the runway...other than that, the whole flight totally hands-off!!! So yes - this years and years of early release stuff is HUGELY frustrating. But they do make pretty decent aircraft!

No - I'm afraid not fixed. It is still very time consuming trying to make any entries to, say, the MDCU with the mouse cursor in VR. Aircraft buttons and knobs are broadly OK, but the VR cursor on a cockpit keypad or similar is way out in either eye. The error isn't consistent either. Some letters you have to point the cursor hand around 3/4 toward the letter above and to the left or right...and then other letters or numbers are different. I have to clear and try again around 40% of every letter or number tried and so - immersion killing or not - I do as much of the MCDU programming in 2D. It breaks your immersion - but not as much as trying the same thing in VR breaks your spirit!

Thanks! There's maybe even more satisfaction to have been blocked by an issue for sometime and to finally suss the problem (with a little help from my forum friends 👍) than it all going smoothly first time! Maybe

Yes - absolutely. All of my pictures are stills captured from a VR flight video I did using the Pimax Crystal Light. The aircraft is superb in VR. The only tweak I had to make was to add a 90 degree turn command that I assigned to a spare HOTAS button so that I could use the usual L/R & Fwd/Back position commands to get easily to the Engineers position and facing the correct way (ie, face on to the panel with an easy seat turn to turn on the APU, which is on a panel at the back, facing the opposite direction to the pilots' instrument panel).

I haven't tried them, but two on/off command pairs seem worth a try: Toggle Engine 1 (etc) Fuel Valve Set Engine 1 (etc) Fuel Valve In your settings, just type in Search 'Fuel' and you should see all of the options