Systems

The last post was tagged with solved. But it is still a bug. That INIT-B is not avail after engine start is correct. But indication of NOT ALLOWED is just wrong! While at INIT-A pressing <- or -> with engine running, should call the FUEL PRED page automatically and not display NOT ALLOWED.

I have a dual WinWing MCDU setup. Capt & Fo. With both MCDUs active none of my WinWing products will work. Disabling/unplugging one MCDU and ops normal. I contacted WinWing support about this. This is the answer I got from WinWing support in regard to dual MCDU support for the A340: Dear customer, currently due to issues of the Inibuild A340 plane model, we can only support MCDU of Captain side. Please wait for the plane model manufacturer to update the plane.

Hi, if I pop out e.g. the PFD with AltGr+left mouse click I get not the PFD only, but more screens in summery (please see sceenshot in the attachment). I think it's strange. Normally I know it, that I was able to pop out each instrument with AltGr+left mouse separately in order to shift it to my 10'' monitor. Maybe I overlooked something.

We finally got 1.09 in the Marketplace, and I would like to say how much I appreciate this module. This is my favourite Airbus on the market now. I noticed that on descent with my altitude set to 3000ft, I still receive a warning tone at 10000ft. This is when hand flying the aircraft without autopilot. Thanks so much!

Just imported my first route from Simbrief and it drew in this crazy curvy manner. Is this a setting I need to change or something?

I have the problem that i cant start the plane any more since the last update. It makes no difference whether I Spawn at the gate or on the runway, the landing gear is always bugged and I always have the red displays. The EFB always shows 1.0.7 even though I've uninstalled and reinstalled everything 5 times, deleted the WASM and every other official folder, I can no longer use the aircraft! i checked twice, i deleted every possible folder and installed the 1.0.9 and nothing changed ... the pictures are the state after that all... still 1.0.7 btw. i tryd to use no liverieys as well and the EIS1 or 2 ...always the same state. And know i tried the A320 by ini, even ath…

when choosing different map overlays they all look the same. am i doing something wrong? (sorry for bad photo, hdr)

Can someone point me to instructions on how to update the FMS navigation data? Or does it use the built-in msfs2024 data?

I'm not understanding the difference between these version? inibuilds published a screenshot showing them side by side but they look the exact same to me.

Hi all Just a little thing I recognized today: LFLX ETAM8K out of rwy21, waypoint LX282 is a flyover waypoint and marked as such in the flightplan. But the plane then draws and flies a flyby procedure. after removing the flyover sign in the FP manually LX282 is marked as flyby but processed correctly as flyover... Just a little thing... Fred

When I read the 1.09 changelog I found: "FIXED Format and calculation issues on INIT B and FUEL PRED pages" First I thought, hey finally they fixed the pages...but then I loaded the sim and ...disappointed...again. Why...left current/right expected ENGINES OFF / EMPTY FMS: - "/" for the dashed EXTRA TIME and ALTN TIME has to be large font - FINAL TIME value is missing - dashed TRIP WIND is fine, because ref photo was with already entered city/pair - dashes for ALTN TIME, FINAL TIME, EXTRA TIME and TRIP WIND have to be drawn in large font - with engines off, the most from line 2 to 6 has to be dashed ! - FF+FQ is only for the A320 family…

Pretty self explanatory. Bought the A340 today, loaded in - EFB is black, no clickable spots. Doesnt matter if i spawn at gate and power up or powered up on RWY spawn. Restarted the SIM and changed liverys (from inimanager) to no avail.

Entering Waypoint in my flight plan, and using LSK1L results in ENTRY OUT OF RANGE warning. Also INIT-A page does not update CRZ FL/TEMP when a higher altitude is selected in the FCU (Is this propper A340 logic)

In A340 VIP cabin in cruise I "took a walk in the cabin" and decide to "sit" in a chair. I was going to press Shift+Q. But I pressed only "Q" and then trouble started. Q is connected to the rudder. I heard the autopilot disengaged. I moved to the cockpit and experienced that I could not engage the Autopilot. I tried to fly manually but then thrust started to vanish. The throttle is right on the instruments, but aircraft thrust disappearing. The aircraft stalled.

Hi, I have a problem : I cannot disenagage the parking brakes. They are configured on my Honeycomb Alphan I can here a noise when i press on the button, but no effect. How could I do to release parking brakes and fly??? Thank's Yves from ELLX

From 5 flights I have done I had 3 wasm crashes,so I cannot fly in Vatsim shat a pity !!!

I think I have found the reason for the wasm problem ,it is the way I load the flightplan,when I load straight from INIT page of the FMC I have the wasm problem ,when I load the same flightplan from the menu page/atsu/aoc/ FLT the plane behaves absolutely perfect,so I made today 9hour KJFKLGAV flight without any problem.

So what you can see is a severe bug in the fmc after entering a "next waypoint". My other files are too large so this one has to do but essentially you can see an empty fmc and it was continously showing and hiding the flightplan in the fmc. There was no more way to control it, clear the waypoint out etc. A few seconds later it was all over as i received a shiny read wasm crash which resulted in me not being able to complete my lhvirtual flight... again Latest version 1.0.8

Hi, Departed VTSP with almost max weight. Performace was okay and in limits. After takeoff climb was slow which was expected. Initial was FL300. But (no Derate) the Aircraft made a level off at around FL245. After almost 6 hrs the aircraft is unable to keep the speed and the level. Thrust is at Max Climb (even MCT or TOGA didnt help a lot). So flying around at FL305 6 hrs after Takeoff and speed is around .765 and it cant get faster or higher. After trying to reach normal speed with toga, aispeed decreases. MSFS 24SU4 V.1.0.5 VTSP-LSZH Block 101500kg ZFW 157900 TOW 259,4 at GW 200t max FL300-303 Speed is hanging around at .76 I know climbin…

WSSS airport simbrief WSSSLGAV Flightplan,navigraph airac 2601 aircraft A340 EIS 1 Passenger version 1.07 Simulator FS2024 specs 11700K,RAM 32GB,AMD 6900XT

ECAM is showing the eng oil quantity even with fadec gnd pwr off when the plane is shut down. I think this is not supposed to happen, I just wanted to report this for you to have a look at it

1st flight in the A340-300 version 1.0.7 using the Hi Fly livery and I forgot to input the info on INIT page B before pushback (not sure if that makes a difference) anyway when I try to access page B on the Init A page by pressing left arrow or right arrow I get an FMS message "Not allowed"

Reporting a WASM crash on the iniBuilds A340 when inputting the arrival into the FMS. Steps to reproduce -Load plane at gate, power on, turn on APU -Load flight plan in tablet then via FMS -Enter Departure and Arrival procedure While putting in the arrival procedure, select the runway, approach, arrival and arrival transition. WASM crash occurred when I clicked on "NO VIAS" in the ILS approach for runway 27C at KORD. Aircraft: A340 EIS 1 Passenger Simulator: FS2024 Version: 1.0.7 Inimanager Navdata Method: Navigraph Specs: AMD Ryzen 7 7800X3D, 64 GB Ram, RTX 4070 Ti SUPER 16GB The Autosave file was not available in the fol…

when boarding is done via GSX, the weights are reset to empty. It's skipping refueling and cattering as well