Systems

Before 1.0.1, it was EIS1 could not perform autoland but EIS2 is OK (with a very very very long flare). After the upgrade to 1.0.1, none of them could perform autoland. Tested airport RJTT 34R 34L, CYVR 08L 08R. When the aircraft reaches the 200 call-out point, do not touch anything, the aircraft will increase the throttle and pich up,... pich down.., pitch up...pich down just like wave.

I'm using the reversers on axis with SPAD.next and it does not seem to work correctly. Having set idle reverse in the table it does not engage reversers (that seems to happen slightly below reverse idle on the axis). It also looks like only engine 1 engages REV on ECAM but it does it for all engines (even without their reversers being deployed). Using reverse on any other engine triggers the respective reverser but isn't shown on the ECAM. Both issues are shown in the video below https://drive.google.com/file/d/1FNaEkA0rEfGxYRzYbCvaxmRBSZclv5TW/view?usp=sharing

The autopilot disconnected several times during the flight from SBGR to EDDF.

Don't know why AP1 does not work, it disconnects after about a minute and keeps doing so even after a fresh install. AP2 is fine?

Says downloaded but install does nothing. EDIT: Wow. Fast service. 30 seconds after posting this, plane installs. Go figure! EDIT2: With v 1.0.1 installed WW MCDU now works. Works just like the Fenix planes, FCU/EFIS MCDU with latest SimApp Pro (.67j) Thanks -A

Nothing happens when I press install. Has anyone updated to 1.0.1? How did you do it? Of course, I didn't ask the streamer who updated a week ago.

Just like you broke the reverse thrust in the latest A350 update, i cant engage them in the A340 either. And no, F1 doesn't work either

Where folks?

I just taxied to the runway with normal use of brakes. Here is the result after take-off... no issue with other aircrafts.

During mid flight MCDU goes off and in the RDY mode. Anyone experience this ?

After programming I noticed that my CI is gone and the aircraft does not automatically sustain the speed which it should unfortunately I have to manually on the autopilot select a given speed because it does not go over 230 kts and am at FL310.

Aircraft: A340 EIS 1 Passenger Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: not relevant WASM Error: WASM: Error during Event OnGSXMenuChanged called execution. Error code : 0xc0000005 Specs: Windows 10 Home 64-bit AMD EPYC 7543P 32-Core Processor 28652MB RAM NVIDIA RTX A4500 18984 MB VRAM Autosave File: not available or turned off Happened when I arrived at OJAI and was taxiing like 100m away from the gate (thank god) I chose the gate N14 from the GSX Menu in the EFB and then noticed that the throttles (and other systems) are not responding.

WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005 Stopped short of runway, set parking brake, turned off taxi and turnoff lights, then about 1 minute later released parking brake, turned on turnoff and taxi/TO, strobe, wing, and landing lights-- noticed no lights and realized was WASM crash. A340 EIS 1 Passenger FS2024 Navigraph Navdata OFP attached except was modified to runway 33L TORK1C departure Specs: Ryzen 7 5800XCD, Nvidia RTX4070 Ti Super, 32GB Ram No autosave in the directory for this flight. OERKLKPR_PDF_1760296321.pdf

The biggest A340 problem is the Phoenix A320. Flying the Ini A340 after flying the Phoenix A320 is like trying to sing after Sinatra. The bar is very high. Dropping a product without offset, non-existing acars, no etp, time markers etc. So many things are lacking. Center Mcdu not working. It is a long-haul aircraft. I honestly don't think a single wide body Airbus long haul aircraft has ever been produced without the center MCDU configured and working. Potential indeed, These things are a minimum in the 2025 payware environment. Get the managed descent sorted and above items added. Then you are singing.

Hello there. Just did my first Flight from FIMP to FACT. That is an 6 Houer flight so when I was on 38.000 feet I turned on 2x Compression. I had no Problems in FIMP or FACT with roling on the ground, steering, taking of or what so ever. I also had no Problems with Frame Rate drop in cruise as mentioned here. The whole flight was a pleasure, also the landing in Fact, spoilers deployed as they should, Reversers worked etc. So now two Questions. I could not delete a Discontinuity, there is no DEL Button or what so ever. So how does that work? It did not work with CLR Command. And on sitting at the Safe Doc in Fact the rescue slide deployed. Does that happen, when the …

Hello. I use the Virtualfly Ruddo rudder pedals without any problems. With the A340, the brakes do not work. I have tried to recalibrate all of this many times without success. If I switch to another aircraft, the brakes work. Does anyone have any ideas?

After yesterday's Simapp update, it says it supports the A340, but nothing is displayed on my Winwing MCDU. The buttons are not lighting up. Is it working fine for others?

I just experience the wasm crash on my first flight on the A340 during cruising flight, now I've made my biggest mistake $60 wasted on this product

My first flight after purchasing the A340 on 10/7/25 was from KMDT to KCLT. The aircraft and all it's systems worked perfectly. Since then, I've tried flying out of nearly 200 airports worldwide with the same result: "Inoperable Systems - AP1 & AP2." After taking off, I try to engage the autopilot, and it engages momentarily before disconnecting and crashing the aircraft directly into the ground. Upon restarting the flight, the AP is not available at all. So, I restart the sim, try flying out of KMDT, and the aircraft works perfectly. Why am I only able to fly out of KMDT with a flawless A340 but completely disfunctional everywhere else in the world?

Hi With any new flight, the formerly selected ISIS has to be reselected, although ISIS is still active after loading the Airplane.

Hi Without an active Mode, the FD shows no Bars and Mode. It shows only 1FD2

We need access to MCDU display so to use Mobiflight with Winwing MCDU, or the Winwing app, please inibuild 🙏

Another WASM Crash Report To reproduce 250 NM from TOD, Autostep climb and Pause at TOD enabled ILS14, no STAR, Rilax transition Systems freeze Information Aircraft: A340 EIS2 Passenger Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: https://www.simbrief.com/ofp/flightplans/KSEALSZH_PDF_1760561805.pdf Specs: i9 13900k, RTX 4090 24GB VRAM, 64GB RAM Autosave: Attached latest .BIN file before crash 1760594692.bin WASM: Error during FMGS_gauge_draw execution. Error code : 0xc0000005 Please fix your aircraft. I always seem to get WASM crashes on overnight longhauls when flying to LSZH whilst havi…

Hi! kindly asking if anybody can confirm when on drone view or external view,i can´t see nose wheel turning according to tiller position.The aircraft turns very well on ground but when on external view the nose wheel don´t move... And second one is there any EFB checklist???

Hi in Hold, there is a Bug when you select immediate exit. The Aircraft still following the HDG.