Sirraj

The stuttering problem with GSX has been completely fixed for me. The A350 is now very smooth throughout the flight and everything is working in MSFS 2024.. Thank you the continuing updates, I couldn't be happier with this aircraft. Sirraj

Thank you for the response, I'm glad to hear it will be fixed. Sirraj

This problem went away for me. But yesterday I uninstalled MSFS 2024 and reinstalled the SU3 beta and the stutters are back. Do we know if this is a problem with the A350 or GSX? I've seen a few similar reports on discord.

The HUD looks great after the last update. The A350 keeps getting better and better. It's my favorite MSFS 2024 aircraft. Thank you for the regular updates, your hard work is very much appreciated.

I am running with navigraph. I haven't changed any hardware in a long time. I have been using the inibuilds a350 since it was released and I've never seen these frame drops before v1.1.0, many people are reporting similar problems on discord.

I did some more testing and found that the A350-900 with no cabin does not have regular framerate drops when loading with GSX. This is on MSFS2024.

Since updating the A350 to version 1.1.0, I see sudden drops in FPS about every 4 seconds while loading the aircraft. This can be seen as pauses or stutters. I think these stutters are related to running GSX Pro. When GSX Pro is disabled, everything smooths out. Other than that, v1.1.0 is really great, thank you for all the great work you are doing on the A350.

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.

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