Sirraj

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.

I had two more WASM crashes today. I had both TRAF and ID disabled, but transponder on with TA/RA enabled. Both times happened shortly after take off. A350-900 FS2020 NAVIGRAPH Ryzen 7 7800x3D, AMD 7900XT, 32GB RAM Here are the errors from the second WASM crash: WASM: Error getting memory in module noolaero-vdgs-klax_generic.wasm. WASM: Error getting memory in module noolaero-vdgs-kphl_generic.wasm. [Coherent GT] Failed to locate file vfs:///html_UI/Pages/VCockpit/Core/WasmGaugeLiveView_0 [Coherent GT] Failed to locate file vfs:///html_UI/Pages/VCockpit/Core/WasmGaugeLiveView_1 WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Thank You

I tried a flight from cold and dark and I did not enable TRAF or ID mode on the EFIS (TCAS/XPDR - on). I completed the entire flight without any problems at all. Leaving TRAF/ID off seemed to solve the WASM crashing problem for me. Thank you!

Thank you for the response. I always have TRAF mode enabled on the EFIS, I'll try leaving it off. By the way, I love flying your A350, I fly FLYBYWIRE, IFLY, PMDG and FENIX airliners but the A350 is by far my favorite. The WASM freezes are frustrating, I'm looking forward to the fixes. Thank You, Sirraj

This has happened multiple times: at the gate, taxing and in the air. This started happening after I updated to v1.0.2. This time I had just started the engines and was preparing to taxi. I pressed the checklist button and controls froze. This was the error: WASM: Exception c0000005 in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm A350-900 FS2020 NAVIGRAPH Ryzen 7 7800x3D, AMD 7900XT, 32GB RAM

I'm having exactly the same problem since installing v1.0.2. Everything stops responding. Very frustrating. Is there any way to go back to v1.0.1?

The same thing has happened to me, three flights in a row. Deleted the WASM folder, reinstalled but still freezing. It happened once while programming the FMS, once on the runway and once in flight.

I'm really happy to hear that you have already fixed it. I'm looking forward to getting that version.

The only setting I didn't have set as you suggested was "AI Radio Communications (ATC), it was set to OFF. When I turned it on, I received my ATC clearance immediately even before I power on the aircraft. Otherwise, nothing else has changed. This only happens with the A310, ATC works correctly when flying the PMDG 737 and the Fly-By-Wire A320. Your A310 is really great but without ATC it is unusable for me, I will go back to flying those other airliners and hope you can fix this in the future. Thank you for your quick response, Sirraj

I'm really enjoying flying the inibulids A310, it's a great addition to MS Flight Sim. However, I'm having a lot of trouble with sounds related to ATC. ATC messages are often incomplete or truncated. I can't hear my responses to ATC. ATC can usually be heard but occasionally quits speaking part way through a flight. The ATIS stutters or repeats the first few words over and over. Ryzen 7 7700x, Radeon RX 6800XT, 32 GB RAM. Microsoft Store version 1.29.30.0. Thank you, Sirraj