All Activity

Works for me also! THX alot

Hey, I have version 1.0.3 installed but the Terrain Radar still doesn't work. In the earlier version there was always water displayed. Now, in version 1.0.3 not even water is disyplayed where it should be. I downloaded the aircraft in the sim and the EFB also shows version 1.0.3.. Also I can't update my Airac via the EFB. I selected the Navigraph Database. It shows that my Airac isn't up to date but won't let me update it. I did a restart of the sim as well but there waas no difference in both topics.

Now that's a bit better, still got a stray jetway though, at 555 in from KMIA.

@iniKyle @iniBuilds Pablo Hello again. I thought this issue would be fixed with the latest update release but the issue is still there in VR. I have attached a photo of the same issue with labels missing and a knob being relocated on the windshield.

I updated to Version 1.03 and flew a 1.5 hour flight from Hanoi to Hong Kong. I am glad to report that after the update the frequent autopilot disengaging that I encountered previously above, did not happen at all throughout the flight even as I turned on live weather and medium turbulence. I did calibrate my joystick in Windows though before I flew that flight. I extended the runway centreline and the aircraft did capture the localiser and glideslope beautifully.

To resolve the issue of excessive sensitivity on the A350 when using SPAD.neXt or default settings, try adding a response curve (Sensitivity/Curve) or reducing the Response/Axis Scale values directly within the SPAD.neXt configuration for the Pitch and Roll axes; additionally, carefully check for conflicting control assignments between MSFS and the external software.

Just removed and reinstalled EGLL and the GSX profile and it seems to be working.

So, this is my set-up for Gaming, @iniKyle . here is my setup for reference—I'm using an HP Victus 16 display with these settings: Here is how it looks normally: However, as soon as DLSS Super Resolution is enabled, it looks like this: As you can see, the display quality actually gets noticeably worsen. I agree with the others here—please adjust the Flight Director to improve this. Just to clarify, I'm running a clean setup with no external shaders or third-party add-ons installed. Cheers!!

Sitting at gate 307 at EGLL and trying to connect jetways I get an error, see attached - doesn't matter which door or jetway I choose, none of them work.

Dear @iniKyle @FlyingYellowFox , Just had this exact same thing happen to me! I loaded up a flight to see if I could replicate your issue, and sure enough, I ran into it too. Mine overshot into the grass, but as soon as I slewed it back onto the pavement, I was able to taxi out normally again 🤣 Must be some weird bug. Cheers!

Streamed Aircraft is unable to be uninstalled, try disabling then re-enable it, @Sweet19blue hope that works, Cheers!

Do you have any plans to create airline-specific cabins for the Airbus A380? Thank You!

A good 10% of the time, my clicks on the screens in the A350 don't register. I have tried various screen refresh rate settings. Thought it was just me.

Siete fortunati ho provato i vostri suggerimenti ma ho lo stesso problema.

Due to GSX having interesting ideas of where my plane should spawn, I had the experience of tailstriking while cold and dark :D In the flight deck, the aural warning "pitch, pitch" can be heard. Clearly there should be some basic requirements (like power to the ADIRS perhaps, not to mention power to the speakers). Not sure if it's related, but A330Driver recently (https://www.youtube.com/live/HP5ZaSw0d8A?si=KvxHOo9--_STofXn&t=983) had terrain warnings despite being on the ground and even turning the TAWS off. Clearly some of these warnings occuring in incorrect configurations/situations/aircraft states.

Sorry, I wasn’t able to play for a little while... I’ve already changed the settings. It doesn’t crash anymore, but it’s still a bit buggy on the ground before the flight loads. I’ve also attached a WeTransfer link to a video showing the problem. In the video, I set TOGA with the parking brake on and there’s no chime. I also triggered an overspeed and there’s no chime either, but the A/P disconnect does chime, which is really strange. Same thing for the engine fire / APU fire test: no chime. I don’t know what to do... There is the link hope u can help me : https://we.tl/t-gGi2PRi42kYN240F

Update: clean reinstall did NOT fix it. To rule out a corrupted download, I fully uninstalled the A380 from My Library, reinstalled it fresh (2.38 GB), fully quit MSFS 2024 on Xbox (not just dashboarded), and restarted. The WASM crash still happens on every load — identical error, inibuilds-A380.wasm, Gauge: DU, all displays orange before I can touch anything. Tested both a runway spawn and a cold & dark start at a gate. So this is not a bad file on my end. It looks like a v1.0.3 regression on Xbox specifically — it went from ~0.3% of loads to 100% right after the update. Happy to test anything you suggest.

Cancel that, I found the switch you referred to. Boris

It's been a while, but I just came across the same issue in v1.08. Rudder Controls Tiller set to NO Tiller deflection with full rudder: Nose wheel deflection with full rudder: Same deflection with full tiller input. Is it supposed to be this way? Boris

Hi team, reporting a WASM crash on the A380 that has gone from rare to every single load. Aircraft: iniBuilds A380 (v1.0.3) Simulator: MSFS 2024 on Xbox (console) Navdata: default Xbox (EFB navdata source not verified) WASM error: "The WASM module has encountered a fatal error and stopped responding." Package: inibuilds-aircraft-a380, Module: inibuilds-A380.wasm, Gauge: DU. All display units go solid orange with the "WASM module crashed" message. On one occasion the new v1.0.3 crash diaog appeared instead. Automatic reporting was DISABLED and no manifest ID was recorded, so nothing was sent automatically. Reproduction (100% — happens on every load): Load the iniBuilds A380 at any airport — either a runway spawn or a cold & dark start at a gate/heavy parking. The displays are already solid orange with the WASM crashed message before I can touch anything. Even on a cold & dark start with every power switch in the OFF position, the screens still show orange with the WASM message. Frequency: this used to happen on roughly 0.3% of loads. Since around Oct 8 (after the v1.0.3 update installed) it is 100% — every load, both runway and gate starts. Notes: I am on Xbox so I cannot provide dev-console output, INI_CRASH LVARs, or the.bin autosave file — none of the PC verification steps apply on console. Happy to test any steps you suggest.

Could be that they’re at an expo so are tied up. Also I’ve heard anecdotally that apparently if you enrol in the SU7 beta that the issue isn’t present, which feels as though it could have been an Asobo issue rather than inibuilds, but they may not have enough info to say that out loud. Obviously that’s just me speculating

Agree about this issue on the A350! But hadn't bothered reporting as was focussing on more systems stuff. Hopefully fixed with v2!

Hello iniBuilds team! ❤️✈️ I play MSFS 2024 on PS5 and absolutely love your airliners! I’m really looking forward to the A340, A350 and A380. I heard rumours about their release a while ago, and I’m ready to buy them as soon as they arrive. Could you please share an estimated release timeline for these aircraft on PS5, even if it’s only an approximate timeframe? It would mean a lot to us console pilots. Thank you! ❤️

Hi, I had the same issue with Beacon and strobe and 100% they were on since start.