Gerwil

I swapped from Store MSFS20 Premium Deluxe to Steam Standard MSFS24 edition. All my purchases transferred across ok as well, including the DeLuxe and Premium Deluxe MSFS20 items.

Quest 3 here. Your story sounds familiar. 5G air link was not a success. The lag in Oculus home was terrible, with broken sound and I could barely click myself out of it with the mouse. No need to try MSFS24 that way. It worked fine on cable though, both Oculus and Steam. I went with Virtual Desktop and it works great wirelessly. Overall, VD makes it easier to connect to the sim, better than it was with the Reverb G2. Also, I have better performance in FS24 than FS20 and it has been very stable so far.

Also, don't put anything in the comm. folder that is not proven 100% compatible with MSFS24. My two flights this morning: 1: BSQ Grand Duke - stutters 2: Default Cessna Caravan - smooth

In WMR (OpenXR) it is possible to open the desktop in VR with the windows key or the lightened X button on the Xbox controller. MSFS must be in windowed mode and made as small a window as possible. You can have BeyondATC or whatever app in the taskbar and open and use it in the window inside the VR environment. Before closing this window just click MSFS so it gets the focus again. This as an aside because OpenKneeboard didn't work for me (apps were visible but no interaction). FsDesktop did work but I find 30$ to much of an investment for what it does.

About the clickspots, part of the iconology seem to have been inverted. As an example turning a rotary knob clockwise there's the right arrow, if it can't rotate any further there is still the right arrow but the stop sign is on the left which should be on the right. This is somewhat confusing.

That must be one of the small (or big) advantages of VR compared to a monitor. In VR I just have to look at the switch once, put my thumb (mouse pointer) on it and can look forward again. The mouse stays where it is, no bezels limiting that. I can then adjust the pitch with the mouse wheel while looking at the vs indicator.

I really enjoy BATC and its ability to make something out of my broken readbacks in (often) any order, but amazingly it always works. Even more so because of my old cracking voice. This morning the controller got a little irritated when I was at the hold short line: "Noo, I need the runway", or something like that, lol.

Ah, now I know why the Duke got delayed 😉

Assuming everything is plugged in well, the power supply and the white light on the cable box is on: If with the previous cable the headset showed the same problem (not recognised as connected) then almost certain it is the headset or the software. If you have the old cables still, just try them again and see if the problem you had with them before shows up again, if so then the new cable is broken. I understand it is not a completely new cable?

I think you just have to wait a little after a flight before shutting down, so it had some time to idle (clear memory or something).

That looks like a graphics card (driver) time-out. I had these frequently in DX12, CTD's or even a complete shutdown of the computer once. Lowering settings could help but I reverted back to DX11 and never experienced this happening again. edit: I had the same MS warning and advice pop-up.

Sounds great 🙂 And with MSX (maritime services X) from Virtuali, a whole new simulation level lol