All Activity

Hi, Not having this issue on my end, do you mind taking a screenshot of your console menu? I'll attach a howto. Thanks! Turn on Developer Mode by going to Settings > General > Developers > Developer Mode and switching it to ON. Open the console by pressing the ` (tilde) key on your keyboard, or select it from the top DevMode toolbar via Debug > Console. Type iniBuilds or EGLL into the search bar to filter for relevant error messages, which are typically marked with red crosses.

Terminal 2B Gate 235 pink sign above the docking station.

Hi, Although I don't have an exact date, we're hoping to have more info for you all soon. Thanks for your patience!

Hey team! Was just wondering when the next A350 update will release as it was mentioned almost 3 weeks ago from the development update? Thanks for the hard work and excited for this update and A380 release soon!

Very weird. I have no doubt about your ability to fly the aircraft, I feel like there’s something bigger at play here. Whether it’s a conflicting keyboard keybind, a peripheral conflict, or something else, there has to be something that isn’t playing nicely. Hopefully we can get to the bottom of it!

Hi, I'm not entirely sure why it would be behaving differently, especially since it works with the A330. I don't personally have any experience using racing pedals as rudder pedals, so I'm not quite sure what to suggest. Thanks!

I am also using TAA. Just tested again after applying that hot fix and everything is working as intended.

Im using racing pedals as rudder and on any other aircraft (737,787,A330) the rudder is been working normally and on the a320v2 its doing this problem 2026-09-08 13-29-34.mkv

thank you, i believe now that all is good. thank you for touor help

What graphics settings are you running? Specifically DLSS or TAA? As I have TAA selected instead of DLSS which is currently to go to setting.

Exactly the same to me. Every day I have to reinstall MSFS2020 version from the inibuilds installer, for the screens to light up. I think I might go back to the marketplace version; that one always worked. I'll give 1.0.9. a last chance :)

Hi. how did you delete by manually and clean up “exe.xml”. Thanks

Yes my sim and Airac have always been up to date. I did a flight yesterday in MSFS2024 in the Inibuild A330-300 and the aircraft behaved the exact same way as the A320neo. When I made a direct, the whole route actually got deleted from the MCDU. And I had to fly the aircraft on heading all the way down to the runway. I have been flying in the sim for the past 20 years - and I´ve been working onboard the airbus (A319/320/321/330/340/350) for many years in real life - I should know how to fly the aircraft. But I am surprised how I am the only one with this problem.

First of all great job with this aircraft already. I’m still a fs2020 user and for me the main issue regarding the sound is that even in cruise we hear the engines quite a lot, both in the cabin and the flight deck. Whereas on the real liners (all commercial aircrafts) the engine sounds are quite high during take off and landings. But as we gain airspeed the airflow becomes the most present sound and the engines are not heard anymore. Personally I always end up reducing the engine sounds manually through the EFB during the climb. It would be great if the engine volume could be adjusted according to the airspeed. Thank you for lessening to our feedback and keep doing your great work!

Hi, When you disconnect the autopilot, does your speed start slowing down? As soon as the AP is disconnected, manual trim is required. The aircraft will pitch up or down depending on where your manual trim reference is set. Thanks!

I'm not entirely sure, it can't hurt to try the hotfix though!

I am using MSFS 2020. I routinely disconnect the autopilot about 5 mile final, autothrottle on FMS speed about 165 knots, flaps 2, gear down, stable with wings level, descending about 700 fpm. When I do this, the aircraft seems to be trimmed slightly nose down, and a slight amount of right aileron trim. So if I don't immediately correct it with the sidestick, the airplane will steepen its descent and begin banking slowly right. It does not seem to me like the correct behavior, and--yes--I have checked the calibration of my sidestick.

Pretty sure they use Javascript, it's also why the OANS when the airport map pops up on touchdown is why there are no stutters compared to the a350

Does the 350 use virtual displays? There’s a hot fix (616.86) which fixes: This hotfix addresses the following: Intermittent flicker may be observed in browsers when navigating to certain websites [6673430] Fixed an issue where virtual displays could not be created after updating to driver 616.56 [6674464] Remote Desktop Protocol (RDP) sessions may display a black screen after updating to driver 616.56 [6687328] https://nvidia.custhelp.com/app/answers/detail/a_id/5906/~/geforce-hotfix-display-driver-version-616.86

If you're willing, I’d recommend giving this tool a try. I use it myself and can vouch for it. It’s helped tremendously in certain situations. Note: If you do decide to use the tool, restart your PC afterwards, then try jumping into the A350. https://flightsim.to/addon/92765/msfs2024-cache-removal-tool

No, look at the ETA at the various waypoints. It’s clear there is something fishy going on here.

RTX5070Ti It’s an odd one as when I made this initial post I had got it working again, but after doing a couple of flights in the Fenix, I decided just to try and load up the 350 again as I was planned a flight in it tomorrow,, and I have the same issue as before, aircraft fails to load and GPU hangs. I originally installed the driver on its release day on September 3rd. I don’t think anything should have changed between then and you installing it now, to warrant me doing a driver reinstall.

We are still doing some testing on our end, but I can assure you it has been logged with the team and they are aware. Thanks for your patience and understanding!

Any news on these stop bars please? I cured the taxi light issue by moving EGLL to be above EGCC and EGSS in the scenery order in dev mode or at least thats what I think cured it. The stop bar issue remains.