All Activity

Hi, I am not sure if this is how the texturing is supposed to be, however I have noticed an annoying issue which doesn't appear present on any other aircraft in the sim (apart from the a321lr and the a330, albeit less noticeably). When I fly the a321 and activate the strobe lights, for the period the white lights are flashing, it introduces a dimming / blackening around the rest of the picture frame. It is most noticeable when using wing view, resulting in areas outside of the strobes natural light area dimming, such as behind the wing and surrounding horizon. I am unsure if it is EV exposure related, but despite a number of setting adjustments it is still present. It happens in all conditions - I have tried with weather off, same occurs on the ground as at cruise. This video shows what I mean. https://drive.google.com/file/d/1OpxjjzCkDWcEENvQaoTZ5KnZ3Jl_19v-/view I am running the sim in 4K and ultra (though have tried in all different configs and issue remains). I am on a 4090 with the latest NVIDIA graphics driver, have tried a reinstall but again issue still present. I have tried a clear community folder and still present. Anyone else experiencing this? Many Thanks :)

Has anyone investigated whether Navigraph navdata can be the culprit here? I saw a couple of the threads allude to this. Regards,

I flew the A350 today from LSZH to EGKK. I set up the FMC and autopilot as I usually do, and I think I did it correctly. The flight plan had no discontinuities and the magenta line for the route appeared and was checked and confirmed from takeoff to touchdown on the ND. However, when I got airborne and activated the autopilot, instead of NAV appearing in the mode annunciator panel at the top of the PFD, "RWY NAV" appeared. I have never seen that before, and the inibuilds A250 manual does not seem to mention it. Also, the route was no longer shown as a solid magenta line, but as a dashed yellow line. I disconnected the AP and hand-flew the aircraft to intercept the route line, but even if I maneuvered the aircraft close to this line, NAV would not engage. I followed a tip given on this forum, re-engaged the AP and engaged DIR to the next waypoint, at which point NAV appeared in the annunciator panel, the route line turned to magenta and the aircraft followed the route. However, RWY NAV remained shown in blue, as if armed (see image). Can anyone explain this? Thanks.

As we know and are told the a340 has delay on pilot inputs to the ailerons through the flight computer and so does the a330 and a350, as well as the A380 which I know isn't available yet from you guys. I have made comparison videos however can't submit here however on the A350 and A380 the sidestick position does not at all correspond with input lag, so why is it like this for the a340. I don't think that would be happening in the real aircraft either (unless it's just cause it's older) P.S. please fix takeoff pitch rotation, it is getting really annoying that you guys don't respond to anything that may be wrong with yall's aircraft flight controls wise, it's rude

In The image above shows the inibuilds a340 in the simulator with the N1 indicators outlines EGT box outlines being grey, as well as below FOB and Flaps and Slats Indicator. However in the image below the outlines appear far more white then what inibuilds has put into the aircraft. Considering inibuilds thinks alot of airbus things are the same I am not surprised, oh well.

Hi! I’m encountering an issue in FS2024 while generating aircraft thumbnails.. The thumbnail creation tool freezes when processing this aircraft, and the message indicates that there is a problem in the model related to the static_pitch and static_cg_height values in the flight_model.cfg. Could you please confirm whether this is a known issue, and if there are recommended values or an official fix planned for this model? Thanks a lot for your support!

Same problem here - despite the NAV annunciation after take off, the a350 does not follow the flight plan. Direct to has to be enabled to a waypoint to enable the following of the plan.

Yep also a mixture binding possibly

JCMK, thanks for the workaround. I have acquired the same problem in the last few flights, and had no idea how to solve it. Your suggestion worked in the my current flight. I also see on the flight mode annunciator (top of the PFD) that there is an entry called "RWY NAV." I can't find that in the inibuilds A350 manual.

I can confirm that this happens to me as well quite regularly. During flight at cruise altitude, without any input or activity from my side, some functionality of the A350 stops working and/or modules freeze and you have to abort the flight. It is hardly possible for me to have a 3-4 hours flight without the A350 crashing rather sooner or later. It is then also a bit frustrating when iniBuilds celebates the A350 in their 2025 review but in fact for me the very expensive airplane is actually useless. A long-range model that crashes on nearly all long-range flights. For me, stability of the A350 has not improved. All other airplane models in MSFS 2024 are stable and I hardly have any issues with anything else than the A350. Today I logged a WASM crash report in the forum (in the MSFS2020 section of the forum by mistake), hoping it helps resolving issues. iniBuilds says they are seeing less A350 WASM crash reports than in previous months and conclude that the A350 is much more stable now. My perception is rather that many customers gave up on the A350 at all or stopped reporting bugs out of frustration because not a lot changed in all those months. I cannot confirm that the A350 is even close to stable.

Oh, I realize I posted this in the MSFS 2020 section instead of the MSFS 2024 section. Please kindly move my posting to the right section. Thank you!

it works for me and better of my solution with reading lights

Dottore_15ita Member 1 Posted November 30, 2025 i found the way to make work the light, go to option and serch: Glareshield light on and Glareshield light off and put your own button. hope im in time

For all those poor souls who are freaking out about the non-functioning screen lights on the A320NEO V.2 SU MSFS2020, here's a little trick that will alleviate the discomfort of the darkness enveloping the cockpit. I discovered that it is possible to obtain a (partial and not optimal) solution to the problem by activating and setting the reading lights on the cabin ceiling, above the pilots' heads, to the maximum level. Better than nothing...

Did a fresh install of MSFS2020 and reinstalled the A300 as well. Unfortunately when trying to start cold and dark, no systems work. Alignment is does not work, cannot move any systems, tried in EFB quick,real and instant alignemnt of INS not working. When importing simbrief flightplan LSK1 gets filled but and the indication AOC Flight loaded however after the IRS alignment should allow you to initiate the its update. Does not appear. I have remove all folders and deleted all files including the registry file and yest still I have the same issue. I have reinstallled this aircraft 4x already and cannot get the GE/PW/F to work. Its very frustrating at this point. I would take on any suggestion to get this fixed. My VA cannot fly without this bird am I am grounded unfortunately

Hello and Happy New Year 2026 When i load the Airport i get Pink colors around Please Support

Information Aircraft: A350-900, Standard Cabin, Ethiophian Airlines livery from inibuilds Manager Simulator: MSFS 2024 SU4 Navdata Method: NAVIGRAPH subscription Specs: Intel i7-12700K, RTX 3080 12GB, 64GB RAM, Windows 11 Other add-ons: BeyondATC (latest version), GSX Pro (latest version) Hardware: Winwing EFIS, FCU (via SimApp Pro), Thrustmaster Airbus Throttle/Joystick Autosave: Attached latest .BIN file before crash. Autosave file is from 15:07h. Crash was shortly after. The A350 was flying on FL410, there was no user input or any activity for minutes, I was just observing the flight, then suddenly many cockpit displays turned red, showing a WASM Crash message (see attached pictures). The error message on the red displays (see picture) says: WASM module crashed Package: inibuilds-aircraft-a350 Module: /SimObjects/Airplanes/A350/attachments/iniBuilds/Function/Interior_A350/panel/inibuilds-A350.wasm Gauge: EFIS I stopped MSFS 2024 after the WASM crash (probably ~2mins after the crash). It was not a CTD, I left the flight myself as it was obvious that the flight / A350 was gone. Then I realized I should restart MSFS 2024 to get to the console. In the dev console, no WASM Crash message was seen. The console messages visible on the screenshot came from starting MSFS 2024 again, it seems. Given the type of error and the error message on the red display, it obviously was a WASM Crash related to the EFIS module. I hope this report helps you finding the root cause of this issue. If there's anything I can do in addition, please let me know. Comment: Due to the constant crashes of the A350, this morning I deleted the A350 WASM folder following these instructions, just to make sure that there are no issues coming from outdated files in there. On one hand, I love the A350, but then again it is the one airplane in MSFS 2024 that nearly constantly crashes, since day one, and it only mildly improved during the past months. The MSFS stock A320 V2 runs very consistently, can't remember the last time I had a crash with the A320. Unfortunately, there is hardly any longer flight (more than 60-90mins) with the A350 that does not end with a crash, still. "Crash" does not mean CTD usually, but that the A350 or some functions of it get unresponsive and you have to abort the flight (I guess a behavior that people usually would qualify as "typical WASM crashes"). 1767276420.bin

Hello, I think you purchased it through the Marketplace too like me. We're experiencing this problem because the version there is outdated. In this case, we'll either have to wait for an MSFS update or transfer the product to the inibuilds account via the inibuilds manager. I'm doing the transfer now because it's unknown when MSFS will update.

Just checked and it seems fine on my .7 version. Logo seems fine to me also.

What is your CI? Do you use Simbrief for your flightplan?

Probably because the scenery was designed for 2020, and I don't think Ini are putting much support in to 2020 products anymore.

Now, i dont know if i am missing something, but my A350 is unable to climb further than FL350. I did a flight from KJFK to EDDM, my first one since i bought MSFS2024, but i did this flight plenty of times in MSFS2020. But in this moment, i have 18 tonnes of fuel on Board and a GW of 182 tonnes. The plane is unable to climb further, it tries and maybe it would have made it after 5 hours or something. I goes up with 600 fpm, than loses speed and goes down and gains maybe 20 feet in the process, but after climbing like 700 feet after 10 minutes at 4x sim rate, it kinda stops. The recommended FL in the FMGC is FL413, and i have 18 knots of tailwind wich should'nt have impacted that either, because i have tried headwind and tailwind. Maybe i am just missing something but this has never happend before to me. Now again, this is only one flight, i havent tested this on any other flight, so it could just be one thing that is broken, but i am rather asking if this is a known issue, so yeah i still need to do more testing

Exactly, really annoying and Echo 19 used the exact same sample for the a350 and the a340, I don't exactly think we would hear it during cruise or descent..

indeed…. I feel like they never answer any forum posts…

This is because of the fuel calculations in the fuel and load. The calculations are always wrong when step climbs are being added. If there are no step climbs, the fuel is normal. @iniBuilds Team @iniBuilds @IniSteve