All Activity

Dear inibuilds Team, First of all, thank you for the incredible work you've done on the A340. The aircraft already feels immersive, detailed, and full of character -- especially for Airbus fans who've waited a long time to see the A340 represented at this level. There's one thing, however, that would truly take the immersion to the next level: the RA (Radio Altimeter) callouts. The real A340 has an iconic, deep, almost haunting RA voice that gives the aircraft a unique personality. That "retard... retard..." and the altitude callouts have a very recognizable tone that aviation enthusiasts instantly associate with the A340 family. Right now, the callouts sound more generic, and it loses a bit of that legendary Airbus atmosphere, It would be amazing if you could recreate or emulate the authentic A340 RA callout sound profile -- the deeper cadence, the classic Airbus vocal tone, and the distinctive audio texture heard in the real aircraft. Small details like this are what transform a good simulation into an unforgettable one. The A340 isn't just another Airbus. It has soul, and that iconic RA sound is part of its identity. Thank you again for all your hard work and dedication to the flight sim community. We genuinely appreciate the passion you put into your aircraft. Best regards Mason Aurnhammer

Also with RNP AR Z I think this issue also happens on A340

In VNKT RNP Y Rwy 02 (AR) Approach via IGRIS, the leg between KT552 and KT550 should be a RF leg, but in ND and MCDU, it's just a straight line KT550 is the last point in approach transition and the first point in final approach. There are two lines in database, the first line is approach transition with path_termination 'RF' and waypoint_description_code 'EE ', while the second line is final approach with path_termination 'IF' and waypoint_description_code 'E F'. So I think there is something missed when the aircraft processing the path.

Almost everytime there is a wasm crash, and yeah as u might say, clear your wasm folder, but till how long? INI really gotta get their stuff together or use a custom model like fenix, whereby fenix has never ever had a wasm crash (at least according to my experience), really @inBuilds yall gotta get your stuff together, every update is "WASM improvements", and really nothing ever changes, same old INI A350, other than performance, ofc!

I am tired to say it again like I did in the past (the posts were deleted or moved). There is a fundamental error with the FMC in the A300 premium version in MSFS 2024. I did hundreds of flights with the A300 in MSFS 2020 and the A300 compatible version in MSFS 2024. No such errors. This kind of error exists with the A300 premium version in MSFS 2024 only.

I've logged this for the team to take a look at, thank you.

Personally, I preferred using Toggle Reverse instead of Hold Reverse. The problem is that Toggle Reverse doesn't work or doesn't work well on half of my aircraft add-ons, notably the PMDG aircraft, while Hold Reverse works well on all of them, except for the L1011. Therefore, I ended up opting to use Hold Reverse so I wouldn't have to use two different methods depending on whether Toggle Reverse works or not. I think I'll start using Toggle Reverse on the aircraft that work with it and Hold Reverse on the ones that don't from now on. I'll see if I can get used to having to use two different reverse methods and not get confused because of it.

Hi, it looks like something has corrupted during your install or the initialization during the first load. Do me a favor and go ahead and clear the WASN for me, relaunch the sim and let me know if this issue is still occurring.

I did a flight following these instructions, and the aircraft followed the GPS route perfectly, with the HSI pointing to each waypoint. I believe I made some mistake on the first flight I did with GPS-only mode, where the A/P didn't follow the route. But since it's following it now, I consider the matter resolved.

I have a Honeycomb Bravo, and I do prefer to be able to have independent reverse thrust settings for each lever. Unfortunately, as of yet, I haven't been able to find a way to set up a reverse thrust toggle input that works at all in SPAD.next, even for all three levers at once. The bindings that usually work with other aircraft simply don't work with the TriStar. I've had similar problems with a couple of other iniBuilds aircraft, where the thrust reversers and a few other controls only work using MSFS' built-in bindings and can't be made to work using any of the common bindings in SPAD.next. Super annoying, because I'd love to be able to make all the controls work exclusively through SPAD, but iniBuilds apparently doesn't allow that at the moment.

richboy2307, I tried your information. Changed the name of my Community folder to, Old.Community. Then loaded the sim to build a new community folder. Then loaded the L1011 and everything worked as it should. I then closed the sim and deleted the new community folder and re-named my old community folder back to Community. Once again I loaded the simulation and opened the iniBuilds L1011. Went through the startup procedures... It all worked great! I am not sure but feel the GSX system or SayIntentions may have been the issue. I'll check in a future flight. It appears to work as it should now. Have no idea why the problem appeared and then disappeared. Thankyou very much for the assistance! The iniBuilds Support Team have been wonderful! Thankyou Again. William(Bugeater64)Simpson

The A330 with no support for the Winctrl MCDU and the A340 with the grouped pop-outs. Two A/C that would easily be the best in MSFS2024 now being handicapped by yourself. I can’t believe it! IniDeveloper pls fix this and you have the best Airbus family in the flight sim environment.

Interesting, ok! Good to know.

The issue is that many times, when ATC says to contact the next frequency, nothing happens. The normal behavior is that your FO will acknowledge the order and then tune the new frequency.

I'll pass this along to the team, in the meantime are you able to assist with providing documentation an FCOM or some sort of material reference for the team to look at as well, thank you :)

Hi Jamir, thanks for your response. As I mentioned I closed the game in disappointment when I got the WASM crash, this was a longer Vatsim event I had planned for for a few days so I didn't remember to get the WASM logs. However I should be able to add more information regardless: To Reproduce: Loading a STAR is the only thing that's caused a WASM crash for me so far. The plane is awesome otherwise. First crash was into EDDP: initial STAR loaded fine but switching to another one crashed it. Latest time, no pre-loaded STAR in FMS; selected one near arrival and it crashed. Other flights, choosing or swapping STARs worked fine. Hit and miss. Aircraft: A300-600 Freighter PW (Premium) Simulator: FS2024 Version: 1.0.8 IniManager Navdata Method: NAVIGRAPH OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes WASM Error: Not provided Specs: CPU: AMD Ryzen 9 9950x, GPU: AMD Radeon RX 7900 and RAM: Kingston FURY Beast DDR5 6000 MHz CL36 64 Gt Autosave File: No Autosave folder or BIN file? EHAMOJAI_PDF_1779005610.2b914fd1.pdf

Yes ensure the MASTER RADIO ESSENTIAL and NO.2 are engaged. We have also identified some other specific scenarios which may cause it to stop working in SU5 due to JS conflicts - expect a fix in v1.0.7. Appreciate your patience meanwhile. Thanks!

Hi, it would be appreciated if next time you can provide the route you did so and whether it was sim data or Navigraph and which variant of the aircraft. You are correct that in some instances this is happening more often than not, but sometimes this can be on a route per route basis or even between Departure and Arrival airports, one or the other and vise versa. If I go into the sim and load a flight there is a chance I won't get a WASM crash and then the viability of the testing and reproducing is already lost whereas if you tell us which route you were on when you had the crash, which is visible in the image above, then if I go in and try this route 5 times and get a crash even once or twice; it now gives us more to look at and investigate into. Thank you

That basically works BUT Owners of throttle quadrants (HC Bravo etc) probably like to have toggles for each engine and applying (reverse-) thrust with each lever separately. Should not be a biggy, since the commands are already there ...

I can confirm this (on the PC version, purchased on Marketplace, running on the ultra preset).

The community identified a potential conflict with Twotter Revived mod that was preventing ENG 2 startup. If you use the mod, ensure you updated it to the latest version.

This one is kind of by design as a sim-ism for both stability and performance reasons. The entire INS computations/detection logic is inhibited unless user does a TK CHG 0 (P.POS) to another waypoint to initiate it.

@here Mod Conflict Can you please try with an empty community folder? Its possible there is some other mod installed that is now causing a conflict. There was already one identified by the community (Twotter Revived) that was preventing ENG 2 startup. That mod itself has received an update which will prevent the conflict with Tristar (or any other addon), but its possible there are other mods influencing core sim functions even when their respective add-on is not loaded. So a conflict needs to be ruled out. You need not uninstall any addons, simply rename your existing Community folder (e.g. _Community) and the sim will create a new empty one in its place on next start. Once you're done testing, delete the empty one and rename the old one to restore your addons. Assistance Settings Verify that all assistances are disabled. They have a tendency to reset after sim-updates even if you had previously disabled them. These ones are known to conflict with logic Automixture AI Auto-Trim Auto-Rudder Disable Crash Damage (ticked = disabled) Disable Aircraft Stress Damage (ticked = disabled) Disable Engine Stress Damage (ticked = disabled) Unlimited Fuel No Repro On our end we're not able to reproduce these issues starting the APU from C&D. Neither using the auto-flight engineer nor manually. See video attached on a streamed copy of 1.0.6. 1.0.6 - Starting from C&D manually - Standard 2026-05-18 23-42-12.mp4 1.0.6 - Starting from C&D via PFB FE Autocomplete - Cabin w/ Lounge 2026-05-18 23-49-46.mp4

Thanks we'll investigate