AaronL

Will do the same if it happens again. It's honestly the first one that I've experienced with the A350.

I just experienced the same issue with the 350 on a long-haul flight last night and wasn't sure what the issue was. Finding this thread I'll monitor but park the A350 in the hanger for now as well. PMDG do indeed use WASM. I agree that I haven't seen the issue with the 777 but they recently released a statement regarding their exploration of continuing troubles with WASM in their 737 line. I've absolutely experienced WASM crashes in that product. They also have offered no guarantee of fixes, just continuing troubleshooting, so I understand the INI devs appear to be on a similar path. This is a difficult issue to track down, it seems and I'm interested by what the INI Dev stated earlier in this thread - that Simconnect may be involved in some manner. I believe this is interesting because the A350 operates within the "sandbox" of WASM, where Simconnect can as well but it also can operate outside this environment and affect the host machine directly - Something not allowed through WASM. I get WASM is required at this point to offer cross-platform compatibility with XBox, but I wonder if it is creating a bigger challenge for developers on PC that we suspect?

They are still offered in the ini app with a "check" for MSFS 2024. Not sure if that is still intentional or if they should be removed since they are not compatible.

RESOLVED: rebooted MSFS and re-loaded aircraft and all is back to normal.

Update: This is happening when not in VR also. May be something off with how the aircraft loaded into the sim, perhaps.

I have the latest A300 build, using an HP Reverb G2 VR headset. I notice that I can manipulate all controls in VR using the standard mouse input but when I try to manipulate an FCU knob - altitude for example, I can see the knob spinning but the altitude display digits do not change. It's as if the input is being ignored. Has anyone experienced this or is this some setup issue on my end?