All Activity

I purchased this airport, everything works fine except the static cars which are displayed in pink, as per the loading issue, is there any way to fix the problem?

One to add. CPLDC won’t log in to Say Intentions Settings for maintenance stuck on disabled

I'd be curious what the leg is coded as in the Navigraph database, as what is depicted on the chart is not always what actually gets exported into the database - I will take a look. Regarding the actual approach, did the aircraft fly the procedure within acceptable limits?

I’ve had a read of the WASM crashes. No need to add as they’re already there. Mine is primarily entering. STAR and hitting the STAR button in menu. Someone has mentioned click spots on the overhead. I have the same and periodically all other click spots around the flight deck. MCP, FMC, lights etc. Allan all round mismatch. Hope this helps Ryan

You've very welcome :)

Hello, thx

Hi, We are investigating the WASM and stability issues occurring with A300.

Also @iniBuilds any progress in your discussions with Asobo on the sim communication issues that are causing the systems freeze? Thanks

@C. Schaffhausen Have you had this issue recently? I havent mentally recovered from the pain this addon has caused me in the past and have yet to complete a single long haul flight successfully

Yes, worked. Thank you very much 😍

https://forum.inibuilds.com/topic/35422-inibuilds-a300-master-wasm-crash-thread-v108-fs24/

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.