Systems

hello :) When I enter the flight plan and try to add the AMKEN waypoint, everything turns red.

As the title suggests, I am getting several TCAS warnings for aircraft that are no where near my position. During my climb out of Zurich, I was getting constant TCAS alerts to the point where I just turned my transponder off. https://medal.tv/games/microsoft-flight-simulator-2024/clips/lRzlxMsb0gy72sYP6?invite=cr-MSx2SEUsMTkzNzg2ODc5&v=135

Hi, So had the GPS Jamming set to real world and somewhere over the Pakistan Afghan border it triggered (makes sense). However the behaviour is odd. You lose the GPS and revert to INS which is correct, and you get GPWS faults and following the ECAM actions disable the GPWS. However despite that I still had "PULL UP" "PULL UP" going off which shouldn't be correct.

When using engine reverse selectively the engine display behaves weirdly. I've found this in v1.0.7. When reverse is selected on Engine 1, all engines show as in reverse on the engine display. When reverse is selected on engines 2, 3 or 4, no reverse indication is shown on the engine display.

No option to activate a secondary flight plan.

Hi all, I just had a hung engine/failed engine start on engines 1 & 4. APU, pumps, bleeds, all configured as they should be. Am I missing something? No warnings other than hung start appeared, no failures were armed. Edit: A340 v1.0.6 on MSFS w/ SU4 on Xbox series X.

Hello everyone,I have problem with Ini request function Although the EFB can import flight plan from simbrief Successfully, but in the mcdu , when you click ‘ini request’ it just says’Ini request: ERROR DOWNLOADING DATA ’ . And you have to repeat 2 to 20 times click the ’ini request’ until it imports your flight plan successfully And I checked the simbrief aircraft model which is the Ini official profile and I try to change my network and I try to use vpn also tried vpn tun , I also checked my efb simbrief account setting, but all of these didn’t work. Actually I didn’t change any efb settings since I first configured the EFB settings properly，and in the…

How can it be a longhauler/oceanic plane has no HF radio installed,when Domestic planes like Fenix A320 and PMDG 737 have.

Hi, Like many others I also had WASM issues with the A340 and concentrated around creating custom waypoint and coordinates. After the A340 came on Inibuilds Manager I uninstalled the A340 completely from Marketplace and transfered the purchase to the Inibuilds Manager and installed it from there. I have now 3 times been able to create waypoint and coordinates without any WASM crash, so if you are still getting WASM crashes try to transfer it and install it through the Inibuilds Manager. Best regards Peter Lund

When Ifly in daytime and then it comes night there is no lighting in the cockpit. When I start the flight in nightime the cockpit light are ok.

WASM Crash after ZDN/DANIB waypoint in Iran Same exact type of WASM crash as I get with A350's, always happens after a waypoint during autopilot following the waypoints. Aircraft goes out of the magenta line and turns away and does it's on thing. In this example, all buttons worked apart from AP1&AP2, with thrusts not registering climb either, TOGA LK is replaced by this. Altitude wasn't changing either and I went up 3,000 feet randomly, with the heading also changed from --- to custom, which was the aircrafts doing and not myself's as I came back to this. I have reported this problem multiple times previously in both the WASM Issues - iniBuilds Disco…

Tried twice to fly using this flight plan, both times same thing happened screens all went red with WASM error. Aircraft: A340-300 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: EDDFKBOS Flightplan attached WASM Error: [inibuilds-A340.wasm] Error: Unable to open directory [inibuilds-A340.wasm] \work\autosaves\ [inibuilds-A340.wasm] WASM: Error during DisplayManager_gauge_draw execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a340/SimObjects/Airplanes/inibuilds-a340/attachments/inibuilds/Function_A343_Interior/panel/inibuilds-A340.wasm is now dirty Specs: i5-8400, Intel Arc B57…

I am unable to insert the TRIP WIND in the INI page. Example: Headwind of 43Kts Whould be entered as "HD43" right ? When I enter this, I see the FMC recalculating data, but wrong. If I instert 2kts, 30kts or 150kts, The recalculated data says the same. Also the insterted value will never appear in the field "trip wind". (not giving me a format error or anything) Is this only me or... ?

Howdy. Since updating to Ver 1.0.6 I cannot get a takeoff performance calculation in the EFB. Using stored Simbrief test flights which have never have failed, now every time I push “Calculate” an orange banner appears which states unable to find safe take off data (or something to that effect). This precludes setting appropriate vspeed, flap and trim settings in MCDU. This has never happened before this build. I have uninstalled and reinstalled the plane to no avail. Is anyone else seeing this? TIA, -A

@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…