Systems

This thread will be the new location for all WASM Crashes relating to the Inibuilds A340 v1.0.12 for Microsoft Flight Simulator 2024. Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A340. NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo. All WASM Crashes existing in this thread will be removed following the release of a new update. i.e. Any Crashes identified…

The brightness of the volume knobs cannot be adjusted with the integrated lights knob.

The manual says we need to turn on the FADEC ground power to check the oil levels. The thing is, by that point in the setup process, ground power and the batteries are already running, so the oil quantity level is shown without the FADEC buttons on.

After I had a WASM crash I reloaded my last autosave. When I loaded in, the cabin pressurization was out of control: vertical speed at 13700 feet per minue and the cabin altitude was at my max altitude. Nothing I could do would reset it to normal.

If the player doesn't disconnect the ACU before pushback, it will be dragged along with the plane.

When using the FA panel to adjust the lights, the Cargo Bay Lights always reset to "Medium Dim" if you move away to another screen (for example, Water/Waste) and then back to the Lights screen.

When this button is pressed, it should display any status messages from the previous flight. Instead, nothing changes on ECAM.

On the takeoff performance page, I always receive the "No Data in FMGS" error message, even though I have uploaded the flight plan from Simbrief into the EFB and the MCDU. This includes entering the data on the MDCU Menu and INIT A pages.

For the route and weights below, according to Simbrief I should use about 4000kg more fuel with cost index 400 (compared to the CI 45 I did the original flight plan with). So trip fuel should be about 4-5ts more than on the screenshot. However, neither the fuel predictions nor the actual usage (!) increased during the flight with cost index 400. In other words: I was able to fly with cost index 400 and use about the same amount of fuel compared to cost index 45. EBBR/25L ROUSY2P ROUSY DCT GTQ DCT POGOL DCT LASAT DCT MOROK DCT GILIR DCT GEVEA DCT KOGAS DCT MEDAM DCT VEVAR DCT BARSO DCT KOLON DCT RARQU DCT NESUL DCT ETOIL DCT CIRTA UA605 DJA UB730 DIR UG862 BUN DCT ASEKA …

HI, I have a question here for the community and devs, Is it normal/realistic to have the LNAV do squiggly zig zag lines, double turns and etc., and extremely tight physically impossible turns right after takeoff? (I'm pretty sure not..) Also after it draws and plans idiotic tight turns, it fails to follow them and turns 360 degrees, goes back to the previous waypoint and keeps missing the turn and circling. Attached is an image of what I saw, these stuff happen all the time and modifying speed constraints sometimes fixes it, but yet there are un-explaned random turns like at SDV, why does it point out a bit between SDV and XIBUS? that turn can easily be taken. And agai…

Hello, I recently bought the A340 and I am enjoying it a lot, what a magnificent airplane. Today I departed from Helsinki on Vatsim, and just after rotating the GPS jammed (I got the GPWS pull up warning and ECAM memo saying GPS lost or something). I looked in the EFB and the GPS jamming was disabled. Is this normal? Thanks in advance Best regards Bram

The brightness of the volume knobs on the radio management panels doesn't seem to be affected by any of the brightness adjustment knobs.

EGCC to LPPT, Sayintentions. Initial cruise at FL230, levelled off then requested and climbed to FL400. Whilst in the climb to FL400 I set up my arrival XANAX2A ILS 02 via PESEX and added a couple of range rings over LPPT and LIS VOR. As soon as I levelled off at FL400, WASM crash. Hadn't clicked or changed anything, I think the FMA changed (from CLB to CRZ?) but I wasn't paying all that much attention to be honest! Aircraft: A340 EIS 1 Passenger Simulator: FS2024 Version: Marketplace Navdata Method: Navigraph OFP: Included in case it helps WASM Error: WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a340/SimObj…

Strange thing happening here. I've only done 2 flights so far, but both have had the same issue, about 1-2hrs after departure in the cruise, I notice all of a sudden that the MCDU's are frozen with no way to input or change anything, the aircraft also locks me out of changing any autopilot inputs and goes into what I assume must be heading hold, as it drifts off the track in a straight line for eternity. Not sure if anyone else is having this issue or not, but I'm concerned to see it twice in a row on my first two flight attempts!

I have all the auto-print functions enabled in the EFB, but nothing seems to print. Am I missing something about how to use the printer?

From time to time, the A340 incorrectly determines that there is no further waypoint after the next one—but rather a discontinuity—causing it to automatically switch to heading mode and stop following the route. Step climbs are still not being executed correctly in automatic mode.

I'm trying to submit an altitude change request in Beyond ATC, but I cannot get the ATC REQ DISPL* text to change from gray to blue. Is there something I'm missing to send this sorta request properly?

Just bought this plane today and noticed that the 100/1000 altitude increment selector in the FCU is inoperative until power is supplied to the plane.

Good evening. I just experienced a new bug concerning the ECAM which I think was NOT present on older versions: On the real Aircraft, when you are on an ECAM system page (for exampe Fuel) and press the key for THIS system page again on the ECAM control panel (so yes, a second push on "fuel"), you return from the system page to the basic ECAM page (on ground: Doors / in flight: Cruise). I think this worked on older versions and for sure works like this on the A350 (just checked it). Now you have to press the ECAM pushbutton several times, to return to the "basic" page. I hope you understand my problem and have look at it... 😄 regards, Benni Thill

Good afternoon Tried to fly the A340 today. When loading the a340 in, the game continuously crashed. Tried at different airports, same thing. On Xbox. Loading in other aircraft, like the a350 was perfectly normal

Good Day Captains, When applying the update for the A340 terrain under the ini app : Failed to verify the integrity and noted the path is correctly. I have tried to reinstall this multiple times directly from the ini app and in microsoft store for the MSFS2024 version and this had not resolved the matter. Any suggestions or advise would be appreciative. Warm Regards

Hello @iniBuilds , I am amazed on what work you have done with the A340, alongside with the updates you push out to improve the A340, such a phenomenal aircraft! I am currently flying this on Xbox and would highly request to add in the Terrain Radar for both EIS1 and EIS2 displays. Also you should also considering to implement the terrain radar to other aircraft, such as the Inibulids A330, A320neo, A321LR, and A350. Just like in the old MSFS2020 days the terrain radar used to work on the Inibuilds A320neo and would be very useful for all your great Airbus aircraft you guys developed. Please reach me out back if you any further updates regarding if you guys are able to pu…

Unlock the full potential of your Honeycomb Bravo Throttle with the incredible IniBuilds A340! If you've been struggling to get the reverse thrusters working correctly, you've come to the right place. In this detailed, step-by-step tutorial, we solve the common "stuck reverser" issue and show you how to create a perfectly seamless and realistic throttle experience.

Hey everyone, I saw a previous thread on hung starts which was solved by the maintenance page in the EFB but that is not working in my case. I am getting a hung start on each engine everytime I get in the A340. - All fuel pumps on, APU bleed ON, APU bleed pressure at engines 36psi, throttles idle, no hardware bindings for fuel control or engine starters. The engines will start eventually but each one is hung and takes about 2 minutes each to become available. Starting procedure at the time was 1 engine at a time 1>2>3>4. Hardware connected is: WINCTRL MCDU, WINCTRL ECAM, WINCTRL Throttle w/flaps/Speed Brake, Mini Cockpit MiniFCU, WINCTRL…

I've noticed that the flight control fault logic when failing PRIM's and SEC's don't follow the correct aircraft logic. For instance, failing Prim 3 and Sec 1 doesn't cause any impact to the LH outboard ailerons.