All Activity

Why isn't the MSFS2024 version of the airports mentioned in the subject line available here yet? CASABLANCA AIRPORT GMMN MSFS24 PREALSOFT Available since October 14, 2025 on SIMMARKET TUNIS CARTHAGE AIRPORT DTTA MSFS24 PREALSOFT Available since October 14, 2025 on SIMMARKET Does the developer no longer wish to offer their products here? Best regards, a customer

@IniSteve @IniJamir Hey guys, just reporting back as promised on this bug now that v1.0.3 is now on the Xbox Marketplace. Good news first, the UPS cargo ramp now has all of its missing objects and looks great. Big thanks for getting that corrected. Posted a pic of it just to show how much improved it looks. The bad news is that the missing texture files for the concrete barricades and pylons around the terminals are still corrupted in the PC package uploaded to the Marketplace and needs a code correction to fix it on the Xbox package. As usual, this is tested with a clean install, cleared rolling cache, default KDFW scenery disabled and all other iniBuilds sceneries disabled as well. All other Ini sceneries work great and have no missing textures. Just let me know as things progress, thanks as always! --Nick N.

Had today directly after update the A350 for MSFS 2024 two D3D12Core.dll CTDs. Never had this before......

Hi, I have calibrated my Thrustmaster Airbus Throttlequadrant as follows: Engine 1+2 on LAXIS X and Engine 3+4 on LAXIS Y After calibrating in the OIS the detents work fine. However, even though engine 1 and 2 should have the same position in idle, engine 1 is slighty higher, which results in more thrust than engine 2 when flying with manual thrust or applying taxi thrust. Physically both levers are in the same position. Here is a screenshot of how it looks in the OIS. Any ideas, how I can fix this?

Hi, FYI I did more tests and I think I found the problem : I tried to send some messages on the Hoppie network as you can see below The format seems to be : - ATC message : /data2/<act_message_id>/... - Plane response message : /data2/<plane_message_id>/<atc_message_id>/... The A300 is incrementing the plane_message_id like the other planes, but will always put 0 instead of the atc_message_id, so that's why the controllers are not seeing my response I guess. As you can see below, other planes are responding with the correct atc_message_id : Thank you for investigating this issue and have a nice day !

WASM crash appeared while starting descent to SKBO (from SAEZ). After starting descent at EGEPI, ATC (FSHud) gave me a STAR and approach. I entered the MCDU to check they were the same ones I had selected. More precisely: Pressed FPLN in the MCDU1 Pressed LSK6 (SKBO) Then I pressed the approach I had selected (ILSX 14L) in order to see which STAR had I selected, and I got the orange displays instead. This is the info required: Aircraft: A340 EIS2, pax version Sim: FS2024 (obviously), Steam version Version: 1.0.10, from iniManager Navdata method: Navigraph OFP: see attached PDF Specs: Ryzen 7 5700X3D , 2x16 GB DDR4-3200 RAM, Nvidia RTX 5060Ti 16GB. Running in a 1080p monitor, using DLDSR 1.78x (so make it 1440p), locked at 30 FPS with RTSS and then applied Lossless Scaling. Autosave file: I have no autosave files or folders for the A340, so no .bin to attach WASM error: see this picture WASM: Error during FMGS_gauge_update 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 The previous poster had the same error messages. I'm not sure they can tell anything 😞 PS: I had purchased the bus last night and this was my second flight. Also, this is my first time I get the orange screens ever. To be disappointed is an understatement. I'm attaching a photo of the orange screens and the flightplan. SAEZSKBO_PDF_21Mar26.pdf

Consistent failure to load into Zurich with the a350-1000 - constant crash and /or memory low warning and/or WASM orange screens. Is anyone able to load into runway into LSZH?

Hey team, thanks for continously developing aircrafts and getting better and better at it. Ive just flown the A300-600F for the first time (MSFS24 premium version) and I have problems loading the aircraft via GSX. (via the EFB its working perfectly, but its not really connected to GSX) A native GSX integration would be fantastic and as a cherry on top - could you add the function to save the FOB on exit of that specific airframe? So when you load this airframe back up you have the last FOB loaded already? Thanks

I have just encountered the same issue at EGLL ILS09L, LOGA2H arrival was fine, LAM inital approach to 09L was halfway there, (up to LAM34) rest was gone. Had to fly via HDG and the charts to the ILS, the aircraft intercepted the LOC and GS just fine. The MCDU went crazy, also on the ND the next waypoint was jumping back and forth.

What a shame the version of the F27 in MSFS2020!!! What is going on in Inibuilds???

After the last update, it is not loading in MSFS2020, my main sim!!!!

The A380 is a highly anticipated aircraft model, and its massive size has left a profound mark in the history of aviation. While anticipating the A380, I have noticed that the previously released A350, which shares the same MCDU as the A380, has had quite a few issues. However, the A340 performs much better. Therefore, I hope its performance can be as stable and reliable as the A340. A comfortable and smooth flying experience is exactly what I am seeking. Finally, I am also eagerly anticipating news about the A380 as soon as possible

I had this happen to me yesterday having updated to 1.2.4. I also steadily lost ias until I hit a floor and AP disconnected. I set a new altitude and descended to that level and it evened itself out but never had it before latest update

Morning all, Loaded up at EGLL today and i have now got texture-less cars in the carparks around the airport. I never had this issue up until installing the new city update 14 today, along with a few updates to the base content, city & world updates. Any ideas what's going on? https://postimg.cc/68tpqHyk

I have the same issue... despite cleaning WASM folder

Exactly same situation on same approach to KJFK. The only difference was 16 hours haul from WSSS. WASM deleted before clean install to 1.2.4. First run on runway, and so on. FS2024 SU4. Will try next night same haul after again deleting WASM.

Could you possibly share your expertise (as per my other comment) about why mouse clicking seems to work on PMDG 777 despite I believe this uses WASM and not html/javascript? Also with your idea about passing x/y coordinates into the wasm, I propose another solution to @iniSteven which may significantly reduce those simconnect overheads. Why not have clickable regions - i.e. pass the corners of 2D polygons as x/y coordinates through simconnect as "clickable regions", each representing a button or field on the current MFD page which can be clicked, along with an identifier. Then have an LVAR which can trigger one of these regions to be clicked. And/or another solution would be to pass the currently displayed mfd page as an LVAR string with some markup language style tags, with clickable buttons/fields having a tag associated with the LVAR value which triggers it. Then an external dev could produce the basic graphics to reproduce the MFD on their home cockpit or software add-on.

Firstly, I would like to second the other comments here about having missing click/touch functionality in the pop out displays. I think is it very disappointing and not well thought through for customers that don't want to keep changing their camera view in order to make MFD inputs. That rant being over, I note that the PMDG 777, unless I am mistaken, uses WASM guages for the lower EICAS and this works with pop out mouse inputs for the checklists. So mouse inputs for WASM on pop out must be somehow possible. I think this is something inibuilds should investigate.

Thanks for opening up this discussion. If the core features are in place from the start, I’d already be very happy. One thing I’d strongly encourage you to prioritise, though, is a stable way to stream the A380’s KCU / "MCDU" to a browser, so it can be used on a tablet or iPad. That would make a huge difference in day-to-day usability. #remoteMCDU&OIS Other features—like offsets and additional refinements—can absolutely come later. What really matters most, in my view, is solid, reliable performance. When the A340 was first released, performance felt quite acceptable. It may have degraded somewhat over time, but hopefully that can be improved again. In any case, I’d really urge you to ensure that the A380 doesn’t end up being a performance-heavy aircraft like the A350 was at release. #performance

I am seeing loads of news from INIBUILDS regarding this update and that update, but ZERO news from them regarding the issues on the A300 pax amd Frieghter for MSFS 2020 especially for XBOX. Considering it was optimised for XBOX does anyone know if they are fixing the A300 and if the glass cockpit update is coming to MSFS2020 for XBOX?

Again, not what I experience on Xbox x a320n v2, so I wonder if you need to delete and re-install.

I’m not experiencing this as such, but I’ve noticed the 3 beeps on autopilot disconnect are now barely audible, which is significantly different from the loud beeps there used to be. Doesn’t matter what audio settings I change to address this, nothing changes. Xbox x, a320n v2

Done, but the lights still aren't working. And im flying on PC 😄

Hello ini team, personally I am looking forward to the inibuilds a380, although I hope I'll be spared from disappointment, suspiciously to many times inibuilds has repeated we have learnt from xyz release however with the earlier release of the a340 it was again not feature complete on release with system features being added in later, while I don't expect crazy abnormals system depth (although many simmers love and appreciate system depth as shown countless times in navigraph surveys) I think it'd be better for things to be complete on release, alot of the time people will suggest to wait a few updates. I'd rather have a complete product in my hands instead of a "we'll release it when we think it's good enough" product (as said by staff in the discord once). Another thing, considering the amount of talk in introductory videos in relation to the flight models of the a350 and a340 I hope a key issue across all airbus fleets made by inibuilds so far doesn't have the glaring taking off like a 'helicopter' feeling/feeling immensely sensitive in pitch (which is only on takeoff) and while I want to believe you guys that data collected is accurate I just don't think it feels right, and that's only on takeoff, otherwise I think from a simmer standpoint the a350 and a340 handle fine. But also considering that you guys have used videos as references for general handling, takeoff just always feels weird from the a330 to the a350. Other aircraft for the sim don't seem to have an issue with this. I have also looked at Captain Paddle's takeoff videos in the a340-300 and 10-12.5 degrees back pressure is applied, he did the same technique in the inibuilds a340 and I could immediately tell it was not a smooth rotation and seemed to quick, although it all depends on weights of course, he did say that it feels quite laggy at higher weights. But the pitch sensitivity seems consistent no matter what the weight is on both the a350 and a340, as well as the pitch rotation, countless threads here have mentioned it but either have been dismissed in discord or ignored elsewhere. There also seems to be barley any gear compression for the a350 and a340, I remember there was a freeware mod for the a350 that added more gear compression as per real life although the person who made it just gave up on continuously fixing it. I think the community is the best resource for feedback but it seems all the belief in handling gets put on the real world pilots and I find that a bit of a chokehold as again and again the helicopter feeling is present, while I have never seen such in real world cockpit videos (which is stuff you guys use as well), I just don't understand how the takeoff issue gets dismissed. But oh well. Hoping the best for the a380 but please.. don't be marketplace exclusive like the tristar.. it's ridiculous even if it is to combat piracy especially with the L1011, the second it gets released on inimanager it's going to get pirated nothentheless, it may force people who really want it to buy which is good for the team, but most probably stick it out, I have 0 clue. I do apologise if this seems kind of arrogant/rude but I'd be curious if any of these disappointments I might as well call it that, that make me not enjoy ini aircraft as much could be fixed, to have the best possible experience for future aircraft, and on the off chance this helicopter feeling can be resolved with some further tuning, that would be great. (Among the other things mentioned)

HI there, I deleted the WASM and reinstall the whole A350, now it can fly stably, but then the HUD, "Normal" and "X-wind" switch did absolutely nothing to it... any idea?