Systems

@iniBuilds this is getting a little ridiculous now. Details below. I changed approach to RWY 14 at LSZH (NEGRA 2A). The crash happened when I tried to enter the waypoint TRA after AMIKI. This is basic stuff iniBuilds - the fact that the aircraft cant handle this is a joke. Aircraft: A340 EIS 2 + Passenger Simulator: FS2024 SU4 Navdata Method: NAVIGRAPH OFP: VABBLSZH_PDF_1768099299.pdf WASM Error: "WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005" Specs: i7-9700K, RTX2080 and 32GB RAM. Autosave File: 1768124718.bin

This affects all inibuilds airbuses, however retard atleast in the a340 should not be instant as soon as 20FT however it is after 20 in the a350 which it is changed in the a340 for some reason, it should be right after the callout of 20FT. It should also still call even if the thrust is set to idle beforehand, furthermore it should also override any RA callouts, not overlap over them. This is also the case with all ini airbuses. I have not done an autoland at all but I assume it wouldn't do retard at 10FT either.

Every time I enter a coordinate in DATA it goes into WASM CRASH!

Hi, I just noticed something new for me. If you make any changes to the original files, you get a WASM crash error. My Thrustmaster throttle wasn't working in reverse. Following advice, I changed the `false` value in the `[throttle] reverse_on_axis = false` line of the WASM file to `true`. After that, the reverse started working well, but in subsequent flights, it started giving a WASM crash error right at the beginning cause of this manuel change. To fix this problem, completely deleting and reinstalling the A340 files only resolves the WASM crash issue. I think there's some kind of program protection involved. But,the WASM throttle data file doesn't sav…

As the title says, when entering the ETOPS entry point on stored waypoints on the FMGS the wasm crashes.

Like the title describes... If you are not perfectly aligned on the flight director, and engage the autopilot, the aircraft makes a very abrupt movement towards the flight director. Looks like the elevators jump to 0 first in stead of keeping them on the present position. Please check the values of your "PitchPID"...

As we know and are told the a340 has delay on pilot inputs to the ailerons through the flight computer and so does the a330 and a350, as well as the A380 which I know isn't available yet from you guys. I have made comparison videos however can't submit here however on the A350 and A380 the sidestick position does not at all correspond with input lag, so why is it like this for the a340. I don't think that would be happening in the real aircraft either (unless it's just cause it's older) P.S. please fix takeoff pitch rotation, it is getting really annoying that you guys don't respond to anything that may be wrong with yall's aircraft flight controls wise, it's rude

Hi all I just noticed that my bird gets lighter from itself on the ground. No engines running, no defuling, no operations. Like there is leaking fuel. Tried to catchit in a short vid. 20260104-1028-32.0789070.mp4

VOR is not engaging on selected frequency. Possibly related to the fact that on approach the LOC was not engaged even tho the LS was selected and the frequency was shown in the display and on APPR mode.

Hi guys, I am trying to help you out with the WASM stuff going on. I am really enjoying the aircraft and would like to enjoy it further without a worry of these crashes. I completed a flight from CYYZ-TNCM and everything went perfect. Once on the ground and deboarded the pax at the gate I figured I would mess around with the MCDU to see if I can trigger a crash. I played around with it while on the ground at the gate TNCM by manually entering a transatlantic route from CYYZ-EHAM which requires manually entering LAT/LONG positions. I entered 3 of them with no issue. After about 2 mins of looking away from the MCDU the crash happened. I also tried selecting random poi…

the CPDLC in inibuilds a340 not responding on aircraft's panel, I tryed a solution that works for me and is as follow: 1) ADIRS has to be aligned 2)verify in EFB that CPDLC is set to BYATC 3) compile and send departure clearance request and wait till BYATC app respond with clearance via text ON THE APP ,not the aircraft panel where it doesn't works at the moment 4) change in EFB CPDLC to HOPPIE 5) compile again the departure clearance request exactly as before and send again 6)in EFB reset CPDLC to BYATC 7) WAIT and you will receive the reply correctly in Aircraft system IMPORTANT ADIRS must be aligned before trying this procedure reported also to B…

In The image above shows the inibuilds a340 in the simulator with the N1 indicators outlines EGT box outlines being grey, as well as below FOB and Flaps and Slats Indicator. However in the image below the outlines appear far more white then what inibuilds has put into the aircraft. Considering inibuilds thinks alot of airbus things are the same I am not surprised, oh well. Also noticed on the PFD it is also white on the top if indications of A/THR I think that is all meant to be white in the CRT's

Helllo guys, I took off from Athens today with the 340 and shortly after takeoff I had this bug in the cockpit with the screens etc turning orange and saying WASM module crashed, what do I have to do to solve this? Jan

For some reason taxi lights are not working.

1. The LSK2L and 2R have to be blue, as the values can be edited by pilot. 2. Whne LSK1R is pressed, the values have to vanish 3. The logic need to be adapted. The ini A340 has GPS, so this logic has to be implemented: "The preferred way of initializing the ADIRS is to use the GPS position, because this does not require any flight crew intervention. Less than 1 min after setting the ADIRS to NAV, the INIT page displays the GPS position without displaying the ALIGN IRS prompt. If the flight crew enters a CO RTE or FROM/TO, the INIT page displays the departure airport reference-point coordinates, and the ALIGN IRS prompt appears. If this prompt key is no…

Hello, i got the a340 today and went to install navdata, i pressed on it in the EFB and it did nothing, i then went to the navigraph hub, reinstalled it and it still did nothing. Has this ever happened to anyone else?

I have had multiple crashes in the last weeks on around a third of my flights, with versions .4, .5 and .6. They look like wasm crashes (nothing responsive anymore), but with wasm crashes, the plane normally remains controllable with primary flight controls, in this case the flight controls are also frozen. The crashes happen out of nowhere, while not doing anything to the plane. Aircraft: EIS 2 + Passenger, if i remember correctly the eis1 was also affected once. Liveries are multiple liveries from the ini manager, they are current. Simulator: FS2024 Navdata Method: NAVIGRAPH Specs: AMD Ryzen 5 5600X, 32gb of ram, RTX3060VR 16GB Aut…

Hello, when spawning the A340 (any variant) the plane spawns in floating (gear up) and with the WASM already crashed. I've tried deleting the WASM folder and reinstalling the plane entirely several times. I am on the latest SU 4 beta Below are some pictures:

This blue field can't be filled

Found a bug on the Autopilot panel, I am not able to switch Vertical Switch any higher than 200 ft Per min , then it scrolls automatically back to zero, It will however step climb when ALT is pushed in. Otherwise a fantastic aircraft

I find that the autothrottle takes too long to engage on takeoff. I set it to 250kts, and the speed climbs past 250kts to 280kts before it kicks in and drops back to 250kts.

Hi, I figured that various Vars regarding the MCDU (FMS) stay at 0 (zero) even when values are entered in the MCDU. The following are affected: (L:INI_V1, Number) (L:INI_V2, Number) (L:INI_VR, Number) (L:INI_FMS_MDA, Number) These Vars are needed for script writing and addons for the excellent A340-300! Could you confirm and maybe fix this? Thanks and keep up the good work!

Hello, Since v1.0.5, the addon is not usuable. i'm getting random WASM crash at every flight. I'm not the only one. We need an Hot Fix. Thank you.

Hello Inibuilds Team, I saw that none of the WASM crash issues were stated in the V1.0.6 Changelog. Did you have a look on the numerous wasm problems it has ? R/W change / Coordinates / DIR TO / SEC FPLN etc etc...

Hello ini Team, @Eddie, @iniSteven, I have no idea what you are doing. Please, tell us what is the version of the FMS you try to implement? With 1.02 you downgraded the IRS INIT to HONEYWELL P3. Now you implement an OFFSET version of HONEYWELL P4. Some of my reports are based on the assumption you do P3, but if it’s now P4… So, what is it now? left P3 / right P4