Systems

Hi all, i am using the Inibuilds A340 SAS livery. The Logo lights are not working. Position 1 or 2 is not changing anything. The tail remains dark. What i am missing here? thanks for the support.

I noticed that after a certain weight the clean speed after takeoff is capped at 257 kts. This is not possible as in a video where the plane was at MTOW the clean speed was at 280kts!! I know there are differences in airplane, weather etc. but a difference of 23 knots at the same weight is quite significant.

After pushback with GSX i received a message "landing gear malfunction". After this, the airplance will move only with high thrust (50% N1). I tried replacing the tyres and it did not work....

Hello, i'm having a crash almost all the times i start the a340, sometimes while setting up the FMC on the ground, other times while on flight, where the aircraft just, looses all control, it behaves exactly as a WASM crash is supposed to happen, but no WASM crash reports in the Console. I'll attach a picture of the last error in the Console, buy there was not a single WASM error. Video of the same crash happening yesterday. Haven't been able to complete a single A340 flight in the last days.

Summary: WASM crash occurs when updating approach from ILS 01C to ILS 01R at KIAD via MCDU during active flight. Flight Details: Route: EDDF → KIAD Arrival: HYPER9 Initial Approach: ILS 01C (loaded from departure) Modified Approach: ILS 01R (per ATC instruction) Steps to Reproduce: Set up flight from EDDF to KIAD with HYPER9 arrival and ILS 01C approach Proceed normally until approach phase When instructed by ATC, attempt to change approach to ILS 01R via MCDU WASM crash occurs immediately upon confirming the approach change Expected Behavior: Approach should update from ILS 01C to ILS 01R without issues.

Hi,please don´t forget to include an EFB checklist or any animation with a checklist to open/close visually,for those like me who like to fly like "real deal" as per real life but not using a printed paper,all TOP airbuses addons have a REAL airbus standard Checklist included on EFB... Second question,wipers are not removing any rain drops from light to heavy rain,could you check this because it brokes the inmersion so much....

I'm not sure if this is a bug, but at some point in cruise, I get an alarm about having my AP off. I fly without FD's or AP's, just auto throttle. Apparently, two taps of the AP disconnect clears the alarm.

Hi Changing the CI during cruise does not have any effect on either the cruise speed, ETA or EFOB. Additionally, there was a SPD LIM entry in the cruise phase which I believe is not possible.

is fuel jettison implemented? cause the OH switches do nothing and there aren't MCDU's values on the fuel pred page, or am I doing something wrong? thanks

I would expect this to be the reverse.

As title says, when approaching the runway on landing. The Approach mode can still be activated. Could it be a bug or real behaviour? Here is a screenshot: *Note i'm on approach and active page is approach, but can still be activated.

Sytems freeze randomly, could be 30 mins into the flight, or 10 hours. When the issue happens the waypoint diamonds on the ND are frozen but the actual flight path moves as the aircraft continues flying. Additionally, the chrono clock freezes along with most other flight instruments, strangely the DME values are still updating. Aircraft: A340-300 1.0.1 Simulator: FS2024 SU3 Navdata Method: NAVIGRAPH OFP/routing: PDF attached, routing: LIV1C VASUR UZ21 ITROL UQ25 RUDAS UT941 IBRIT UM998 ONRON/N0462F380 UM998 TIDOU/N0454F400 UM998 CSO UM2 CIRTA DCT ETOIL DCT OMEDA DCT TORTU DCT ERTEV DCT CANNE Z651 KELIP KELIP3G Specs: i7-9700K, RTX 2080, 32GB …

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