Sirraj

This was fixed in 1.0.9 and now works perfectly with Beyond ATC. Framerates are better, during descent it hit all the speed and altitude restriction. Really great release, thank you!

Your wife's comment made me laugh.

To use the QUICK PREFLIGHT command: Settings -> Controls Select your keyboard or mouse In the "search by input" box type: QUICK PREFLIGHT Assign it to a key or button

This happens every time I disconnect the autopilot when on final approach. (MSFS 2024 SU2 - v.1.07). I assigned MASTER CAUTION OFF to the same button as AUTOPILOT OFF. So after I get the master caution alarm, I press the button again. Seems to work.

There is a new command you can bind to a key combination called QUICK PREFLIGHT, it removes the engine covers and pitot covers.

I solved the problem by removing an add-on called WALKAROUND MANAGER MSFS24. I uninstalled it and the engines start normally.

MSFS24, the A350 engines suddenly won't start. GPU and chalks were removed. APU running and APU bleed on. The fuel pumps are on. I serviced the engines (20qts of oil), I deleted the WASM files. I uninstalled and reinstalled the aircraft, nothing helps. Any other suggestions?

I came here to ask exactly the same thing you asked. Is there a procedure or tutorial that explains the correct order when using GSX with the A350? I found that if I start fueling with GSX before clicking on 'Set ZFW' and 'Set Fuel' buttons, the performance calculation page on the EFB gives me an error and won't calculate the V-speeds.

I'm seeing exactly the same problem. I reinstalled the A350 and GSX, ran live update nothing helped. Fenix A320 works fine with GSX.

I had the same problem until I removed every control surface key binding assigned to my keyboard.

Try using the thum b wheel just below the keyboard.

I noticed the same thing. It's really confusing when I switch to other aircraft and have to think about which way to turn the mouse wheel.

I have the same problem on the right side. I have removed every spoiler and aileron binding from my joystick and keyboard. This only appears on final approach. This only happens in MSFS 2024, 2020 works fine.

I just completed a complete flight using v1.0.3 with TCAS set to TA/RA and TRAF enabled. No problems at all. Thank You!

A little more information. I completed two flights without any problems at all. I had both TRAF and ID disabled transponder in standby.