All Activity

Hello Team, So removing everything out of the community folder and leaving FSTl model matching , a350, 1 livery of delta, and 4 sceneries , the plane finally loaded at 100 to 108 fps no stutters. Prior to loading, I did a clean de install and re install. Cleared wasm, rolling cache. Now, right when I was putting my info take off numbers,I hit the button to sync and I got a wasm crash... ughhhh

Oh finally. I turn OFF the warning volume in the options, no more buzzer until you make a patch.

Imagine flying 5 hours with this f....g buzzer. It's very annoying On the first days using the plane, flying at FL310 to FL330 was perfect, no buzzer. But now at any altitude above FL300, it start. I really upset of that, please do a patch to fix that. MSFS2024 2026-08-20 20-35-39-727.mp4 MSFS2024 2026-08-20 20-36-10-509.mp4

The 1.1.0 update for VHHH introduced multi-jetway support but in the process broke compatibility with GSX. Is there any way to get a copy of the older version 1.0.2 that does work with GSX? Thanks.

Nothing yet unfortunately, still investigating on our end. Thanks again for your patience!

Thanks for looking at this for me. Any update available?

Hi, This indeed was implemented on V1.0.7 and further improved on V1.0.8 Which cockpit interaction system are you using: Lock or Legacy? Thanks!

Oh, okay. Yeah, only so much one can do about that. Thanks!

Thanks, added to the list of items to check tomorrow. Thanks again, Liam!

Thanks for troubleshooting the issue and coming to a solution!

No stress here, as long as it’s being looked at, it’s all good. Just another issue I’ve found, but haven’t done any digging on it yet, is that the ‘custom vdgs’ doesn’t work anymore at Manchester. Completed a flight and taxied onto stand 103 on pier 1, and the vdgs was blank. Uninstalled and reinstalled EGCC, also toggled vdgs off/on in the ini manager, and it still remains blank.

Hi, Changelog from 1.0.17 update : As part of our commitment to consistently improve performance across all iniBuilds aircraft, we have made the strategic decision to sunset the A350 cabin packs from v1.1.7 onward. Doing so allows our teams to focus entirely on optimising the core product experience rather than maintaining multiple cabin variants. So, not a bug, just removed for better performance. Thanks!

Hi Liam, Thanks for the continued photos and feedback. This is #1 on my to-do list tomorrow morning, and I should have a better understanding of what’s going on by the end of the day tomorrow. Thanks for your patience!

Hi, While we would love to add every available livery, all Xbox add-ons must go through the official in-game Marketplace, which requires strict airline copyright licensing. Hope this helps clarify. Thanks!

Hi Prabin, Sorry to hear you're having issues with the A340. Have you downloaded and installed the official iniBuilds A340 profile for simbrief? Let me know if that solves the issue! Thanks

Yes, correct. When using "A,O,U" there is no problems!

I have a flight SWR 161 for the A340 in Simbrief. However, i cannot import it. I get an error on the EFB that says: ERROR: Flight Plan Aircraft ICAO Code Incorrect SWR. The flight plans are all blank. I changed the call sign to AAL. But I stil get the above message. I have done only one flight successfully on the A340. I had given up on this error but finally decided it is time to seek help. Prabin A.

I am not sure, what you are saying, I think the issue is, if you use letters like "Ä,Ö,Ü" it is causing the issue.

Hey! Why no Quantas livery for the 220?🥹 On Xbox we are only able to use the liveries from the livery pack. Also, would you consider adding the Lufthansa City livery at some point? They’re taking delivery soon!

That's awesome and long over-due, thanks for pushing this internally Kyle and trying to make sure your application ends up with the same functionality we've had in similar software from most other developers/publishers for a long time now.

Second image showing them off/rendered grey when in proximity

Hi, Just having a quick play around, they dont render at distance now, so the lenses are purple, but when in proximity of them, they change to grey/off. Im assuming this is linked to them changing from red to green/off with the updated stop-bar characteristics you implemented

This is still not solved - or still a feature, right?

Hello, I fixed the problem, I was using "Throttle Axis 1/2 (0-100%)" and it's not compatible with this add-on, we need to use "Throttle axis 1/2" and now it's working correctly.

I believe that is where you're supposed to see which products have received an update that you haven't yet installed or applied. I'm currently working on a "Quality of Life" suggestion to pass along to the team for future consideration! Thanks!