Systems

Hi, as I was programming some SD profiles for the community I found some issues that needs to be fixed: - the DOT Variable for FCU SPD Display (L:INI_FCU_SPD_DOT) stays at "0" - the Variable for opening EXIT 2R (A:EXIT OPEN:5, Percent Over 100) stays at "0" - RMP1 ON/OFF switch switches power of both RMP1 AND 2 (L:INI_RMP1_STATE) I hope you can reproduce those issues and will fix them with the next update. Thx!Keep up the good work! Rgds Chris

COPIED ACTUAL FPLN IN SEC F-PLN, MODIFIED THE SEC FPLN WITH A PBD POINT AFTER DEPARTURE RUNWAY MADE WITH AIRPORTRUNWAY/RUNUWAYHDG/12nm (FACT19/191/12) FIX AND ALL FREZES, VIEWS WORK BUT ALL THE OTHER THINGS NOT Thanks

I just had a wasm crash when I was changing the landing runway in the MCDU. I already had a landing runway set for EDDF, noticed that there was a runway change, when I changed the runway the WASM crashed. Information Aircraft: A340 EIS1 Passenger Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: KDTW-EDDF Specs: Ryzen 7800X3D, RX 7900XTX, 32GB RAM Autosave: Attached latest .BIN file before crash WASM: WASM: Error during FMGS_gauge_update execution. Error code : 0xc000001d WASM: Module vfs://inibuilds-aircraft-a340/SimObjects/Airplanes/inibuilds-a340/attachments/inibuilds/Function_A343_Interior/panel/inibuilds-A340…

Got a WASM crash exactly at exactly 30 minutes on the chrono (related maybe idk). Autosave has never been enabled, no folder exsists, EFB says autosave interval (M) is 60. Clock remained ticking after WASM crash. No steps to reproduce, I was tabbed out of the sim for around 15 minutes before the occurrence. Aircraft: A340 EIS 1 Passenger Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: NIL WASM Error: [inibuilds-A340.wasm] Error: Unable to open directory [inibuilds-A340.wasm] \work\autosaves\ [inibuilds-A340.wasm] Specs: 13th Gen Intel Core i7-13700KF. NVIDIA GeForce RTX 4070 Ti. 32GB RAM. Autosave File: NIL. Autosave has n…

When creating a Custom Waypoint on the SEC FLPN, which is standard SOP for nearly all A340 Operations the sequence always get's messed up, furthermore after the creation of the custom waypoint directly in the FLPN example: KLO/276/1.5 it enters the Custom Waypoint but directly goes to the Primary or Main FLPN which is really annoying and not correct. Furthermore after creating the Second Custom Waypoint example: KLO/250/15 it completely messes up the sequence and duplicates waypoints. Looking forward to getting this fixed soon. Thanks

When trying to enter the ADF under RAD NAV it has no effect and the entry field always stays blank. Would be nice to have this working in a future Update. Thanks

Hello iniBuilds, I experienced a bug regarding the initialization of the flightplan in the MCDU: Yesterday, I flew a flight between EDDM and KSFO. I aborted the flight in cruise. Today, I wanted to fly the flight again, with an other route. I loaded the flightplan as usual, using the the tablet -> My flight -> import from simbrief and then going to MCDU INIT page -> Inserting EDDM/KSFO. It loaded the old flightplan from yesterday, not the new one I created today. I deleted the flightplans in the WASM directory and started the flight again, now it loaded no flightplan in the MCDU. The solution was to also delete the simbrief.json, a…

Just took off from EDDF and on the ground I was getting pretty good performance. It's only after take off and during cruise that my FPS is tanking and I am getting a lot of audio stutters. My base frame rate has dropped to 20-25 fps. This only seems to happen in cockpit view. When I use an external camera my performance returns to normal. I am using a 7800x3d and 5080. I also use autofps.

Doing long haul FACT to EDDF now through the night. GSX a mess and I guess I don't have the patience to fiddle. AP1 keeps disconnecting but AP2 is holding for 6 hours now. CAB V/S arrow keeps flashing at 50 ft/Mn. Need the centre FMC to work. So far going ok , would like ACARS etc.

So finally reached T/D without any problems or crashes for the first time since release, I was preparing for the approach and I noticed "trans alt" is there with numbers being entered in thousands. Isn't it supposed to be "trans level" and an entry as "FLxxx"?

It happened for the last 2 flights where the throttles wouldn't stay in LVR CLB in the cruise but just flickered back and forth. The next flight they just went to TOGA as I touched down, this time the AT was off. Thrustmaster Airbus Captain's pack.

Had 2 step climbs programmed (auto load and auto step climb OFF for me)-- when I passed the first one (had to wait for ATC handoff to request higher) I got a Step Climb Deleted message, but saw both step climbs were gone. Is that by design or a bug?

Seems the LOD is affected in VR when glancing down at the MCDU, some letters are missing and with a slight lean forward they appear? Overall VR performance is really great, hopefully this can be fixed.

So this was my very first flight with the A340 FRA-BAH, 01:30 into the flight while cruising smoothly, blue hyd system decided to fail on its own followed by the green one as well then lost thrust on engines 1 & 2. No armed failures, no active ones whatsover. I followed ecam actions then made an emergency descend, during descend suddenly everything was back to normal. I decided to continue to the alternate despite everything back to normal, prepared for an ILS approach, the second surprise was the airplane did not want to tune in the new ILS frequency, kept insisting on the original one of the destination, manual tuning did not work also whatsoever, ended up doing vis…

I´m having quite some issues with the ground handling. Even with nearly full rudder deflection at <20 Kts the plane does not turn more than 20°. The rudder controls the triller is used as setup and the rudder is bind to axis. Differential breaking help just a bit. Any hints are wellcome

Twice now, takeoff from EDDF and can't get any lateral or vertical mode to engage.. for credibly, airline pilot here. What am I missing, or this a bug?

Hey Just performed my test flight on the A340 but I’m a bit disappointed by the MCDU here are the issues I encountered - Several « company MSG Rcvd » nothing showing up in the ATSU - ATSU is super limited and many greyed functions shown it’s frustrating - ATIS can’t be taken from SI (possible on A350) - no CMS implemented. - MCDU feels super laggy - Can’t go to Init B once engines are running - fly by wire feels super heavy while the aircraft was light didn’t find Any guidance on particular settings - would like to have the option to actually print on real POS-80 printer I was hopping for a better MCDU similar to Fenix…

Hi is the ILS data in the ND working with track miles? I had EIS2 on a lufty and the data was missing? Running SU4 latest update. https://youtu.be/HpiRNCqWz9k

I tested it yesterday and it seems mostly in line with the other IniBuilds aircraft! The TAB for screen export combines all displays into a single one, but as you did recently with the A330, each screen should be exportable individually. I loaded the flight from SimBrief, added the SID and STAR, and it duplicated the entire route, giving me a DEST distance of about 117,000 nm. I had to manually delete every waypoint after landing! I only did one test flight, which I didn’t finish because of a CTD — not sure if it was caused by the PC, the sim, or the aircraft.

Changing the runway/SID doesn't clear the take off data.

switching the left ACP off also switch off the right one

I had this WASM crash when I clicked the RADIAL IN on the DIR-TO PAGE button on the MCDU To reproduce On descent crossing 11000ft All 4 engines running Open descent selected Click radial in button Systems freeze Information Aircraft: A340 EIS1 Passenger Simulator: FS2024 SU3 Navdata Method: NAVIGRAPH OFP: EDDF-EGPH Specs: Ryzen 9800X3D, RTX 4090, 64GB RAM Autosave: n/a WASM: Error during FMS_gauge_update execution. Error code : 0xc000001d EDDFEGPH_PDF_1759865867.pdf

Spoilers do not seem to have any effect on airspeed. It takes forever to lose speed during descent.

Was about halfway through a three-hour flight when the aircraft decided to go pitch down. Nothing was operable. Aircraft: A340-300 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: Attached WASM Error: WASM: Error : Unable to open directory Specs: i7-14700KF, RTX 4070ti and 32 GB RAM HECAEDDF_PDF_1759860224.pdf

hi, I’m using the available simbrief profiles but I get an error that the aircraft is not recognized, using the official Swiss livery from marketplace. Tried changing to others but it’s the same so GSX load doesn’t work. any suggestions?