All Activity

update: i managed to identify the cause of the issue my apologies.. it wasn't related to the scenery, navigraph or A350 itself i was accidentally selecting an unnecessary SID transition, which caused BRUCE and AGRIS to be inserted twice in the flight plan BRUCE and AGRIS were already included in the flight plan but i mistakenly selected them again as a transition because i thought i had to select one ,so there were 2 BRUCE and 2 AGRIS in the flight plan causing the looping trajectory Sorry for the confusion and thanks for your help!

i removed the custom airport and the scenery

hello i looked into the scenery and navigation database, that strange looping SID is still there

getting them in the 380 after the latest update as well. Will try the trick that worked for the synaptic 220 and delete the install and reinstall. Any idea when the 380 is coming to the ini manager>!?

Hello team, I experienced a WASM crash today upon updating to v1.2.8. Aircraft: A350-900 (no cabin) Simulator: FS2024, PC Navdata Method: NAVIGRAPH OFP: None loaded WASM Error: WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm gauge: EFIS Specs: i5 12600K, RTX 470 Super, 32gb DDR4 RAM, Windows 11 Autosave File: N/A Steps prior to crash: Performed update from v1.2.6 to v1.2.8 via IniManager. Launched MSFS2024 via Steam Selected Free Flight and selected YSWS as airport and Gate 25. Clicked Ready for Flight. From external view, used CTRL C to get to cockpit view. Used custom view key to select Overhead panel view Activated all 4 battery switches then Ground Power 2 and 1 then ADIRU switches 1, 3 and 2. Switched back to cockpit view then another key custom view key to display OIS panel. Went to Options and Navadata screen when OIS was live Clicked update for Navigraph data Download with progress bar showed its normal activity. When download of Nav data finished , immediate orange screen on almost all displays. OIS showed normal display. (Note general nav data update from Navigraph hub had not been performed yet)

Having them as well with inibuilds liveries only installed and used. Happened after the 1.0.6 update via Marketplace and downloaded/installed the plane for use

I have noticed that the arrows for 23L seem to either be bleeding through or incorrect. I don't have any other EGCC scenery installed just basic MSFS2024 and no addons. When I search the library EGCC Inibuilds is the only EGCC related scenery that shows up. Is the correct and what others see?

Hi Kyle, No, did not fly anything else yet into YSWS, however I did raise the issue on the Navigraph forum and they did confirm the airport map does not exist yet. Jeppesen need to make it. No ETA on if or when they will do this. So I would expect the same issue with the A380 to appear. Cheers

I noticed that TCAS senses altitude wrong. I have traffic 2000ft below me and TCAS shows -200ft. I am in FL410 and the other traffic in FL390. I can clearly see from outside view, that the traffic is 2000 ft below me. Because TCAS shows the traffic 200ft below me, it senses a Resolution Advisory see screenshot. I had it twice today. It seems, that the FL390 will be displayed as FL410. Why I don't know. Please check!

So I fly the A340-300 in real life. I can confirm, that this is not correct! They should touch the ground of course! The wheels of the center bogey are touching the ground the same than the wing landing gears. This is a bug and needs to be corrected!

If INI builds is a decent company you should refund all the buyers of EGLC

Scandinavian landscapes have a very distinct beauty of their own. They might not be "high-quality" in the way you’d like, but they’re certainly not that bad.

That's right friend, that's how they looked before, hopefully in V2 they can put the windows back like this

Great to hear, thank you!

Hi Kyle. Understood, but, as the A21N is an inibuilds marked plane, can’t you at least put some pressure on asobo so that they treat this plane in a decent way? Can you report them the issues and the need to fix them? This would be very helpful. We simmers have been trying to do so on the official forum but after months and various sim updates nothing has been touched. I’m sure that if you directly contact them they’ll listen. Can you please tell the team to do so? Please. It’s an amazing modern plane. We cannot absolutely enjoy it enough right now. Thanks Francesco

Wow, they looked like that before? I had no idea. Looks incredible.

The A330 will come to 2020 as well?(like A321LR,A400M and A330 BelugaXL)

And also, there is no working GSX Profile for MSFS2020 I added one that at least is far better than the default one https://flightsim.to/addon/118128/gsx-pro-profile-for-asobo-inibuilds-a321lr

any news on this? i was really happy seeing the option to remove gps but we really need the nav 1 radio to work

What happened to @Rezab are also happening with me, @iniKyle V1.0.5 was good, but suddenly by V1.0.6, I felt like it revert back to V1.0.3. After landing, PA AFter-Landing Announcements are working twice again, one is when passed 70 to 60Knots, the second happened when vacating the runway.

Thanks Kyle. Honestly, I'm really frustrated about this—it completely came out of nowhere. I was flying this aircraft regularly in MSFS 2024 with zero issues until the September AIRAC cycle update. What makes it even more annoying is that I’ve already tried every standard troubleshooting fix I could find, but nothing has worked.

I am having similar issues (the entire cockpit will not load) and do not have any mods installed.

Indeed, all those gates are multi-jetway gates and by accident, the other ones I tested randomly were single jetways. Installed your tool and works fine, aweseome! Thanks and have a nice evening.

The OIS on the Ini A350, not sure what Aircraft version being simulated here. Would be nice to get an accurate Airbus/Thales FlySmart OIS version on the Ini A350. In line with most current operators. Fantastic aircraft otherwise.

I have tried everything now - I guess. Login out off and back in to Navigraph, reinserting my Simbrief ID. Didn't do any good. Reinstalling the A350 and togling Navigraph and Simbrief connections. Didn't do any good. Even reinstalling MSFS2024 did not help. All steps above were preceded by clearing the WASM folders. All involved apps/aircrafts are on the same Navigraph AIRAC cycle 2611 rev. 3, and the same Simbrief ID. I'm on MSFS2024 update 7.1 (build 1.9.21.0) amd Windowws 11 pro 26H2 build 26300.9818. So my conclusion right now is, that I cannot use the A350/A380. rgds Søren