AaronL

I've just experienced the same issue of the display freeze and plane banking to the right. I could not select anything on the MCDU or FCU. Could not disengage autopilot. Had to end session. I'm on the latest version and prior to flight today I cleared my WASM folder. Remind me again - Should we be clearing the WASM folder before we update the A350?

Just had the same condition in cruise. Plane was banking to the right, significantly off course. Also lost aircraft control of MCDU, FCU. Could not disengage autopilot. It's like the systems were frozen and I couldn't control the plane at all. Ended the flight.

I have the same issue and folder structure. No A350 WASM folder. I WAS in the SU1 beta. I left the beta today but no other impacts.

Press the master warning to silence the alarm. It doesn’t illuminate, just press it.

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?

Yes, use FlightAware and when you find a routing, click the flight number to see the ATC cleared routing which you can manually enter into the A300s FMS.