All Activity

I have the same issue… Been trying for hours now but haven‘t found a solution.

Hello I was just wondering why is the flight plan still not going into the mfd everything that I could think of has been uploaded right but still seems to not show

I'm not getting any transmition from my VHF 1 or 2 in a350 even though Vpilot sees the frequency I set in aircraft. My VHF knobs are pulled out and I turned the volume to max. I can see that people are talking on frequency (RX light is blue in Vpilot) but I can't hear them. I have tried using different airbus aircraft from different developer company and it worked fine.

Same for me today! WASM: Error during FMGS_gauge_update execution. Error code : 0xc000001d Aircraft: A340 EIS 1 Passenger Simulator: MSFS2024 Navdata Method: Navigraph ( up to date with the current AIRAC ) OFP: Not included or imported into EFB. Was just manually entering a flight plan into MCDU. WASM Error: Didnt a chance to copy it in the same but I have a picture included. CPU: Ryzen7 8900x3d, GPU RTX 5080 16 GB VRAM, RAM: 64BG Autosave: don't know

i agree, especially the a340, takeoffs in that thing are too violent if you get what i mean

Yes, there is a problem and a recommended configuration to circumvent it as long as they are working on it. What else do you want? Oh, I have. In particular, people using outdated Navdata in Simbrief are creating invalid flightplans. Oh, that problem occurred for the large majority of the users. Additionally it was confirmed by the team. Your "bug" is observed by only one user and not confirmed. It becomes a bug if enough people are complaining about it, and it is confirmed by the team. Which both is not the case for your problem. No, that is definitely not the case. There may be problems caused by addons causing problems in specific other addons, but not in all. Think about the problems caused by addons having no "package_order_hint" entry in particular with Navdata. It looks like a problem of the plane or the scenery, but finally it turned out to be a problem with the Navigraph Navdata caused by old MSFS2020 sceneries not involved at all in a specific flight. It is enough if the old addons were installed to disturb the navigation. Oh, I'm sorry about that. Then you have never developed software for Operating systems the user can configure in an open way and install other software. Otherwise, you would know, how external components can influence the behavior of your software. Just let other tasks consume the resources like CPU or memory and lets see, how good your software performs with missing resources. A problem of your software or of the user not providing a clean environment?

from what i have heard, people got banned for sharing their disappointment and criticism on discord...

I am NOT mentioning about the past statements here, that's not even a valid viewpoint, of course they might mention about the TCAS a few months ago but hey look, still having problem here? Regarding my VNAV problem, my navdata is correct and up to date. No problem with PMDG products or Fenix 320 or ini 330, so this one is the only problematic one. Therefore you can not blame the navdata. Flightplan is standart Simbrief flightplan and I've never see any single person had conflict in that. And I clearly indicated above that there were no waypoints for next 50 miles (no direct to as well). You said a lot of people would complain, but here is the one item from last update: Fixed - WASM texture loading bug introduced in SU4 on some machines As you can see, some bugs do not occur on every user. I don't know how you can say this is DEFINETELY not a bug but let me say it very clearly, I don't think you are the person who decides it is bug or not. Let me summarize it for you again, if your simulator and all other systems and addons work without any issue with the other aircrafts but not with the A350 then you can consider it as a product bug. I am a SW engineer with master degree, if your SW is not working on all of your target systems or platforms then you are doing something wrong on fail catching or management and you are not robust against different noise factors and that is also a BUG!

Double-check your install path in iniManager! MSFS 2024 handles the Community folder a bit differently depending on whether you're on Steam or Game Pass. If the liveries are in the folder but not in the game, try a quick restart of the sim - sometimes the new UI takes a minute to refresh the livery list for the A350.

Looking at this post. It goes back to August 2025. A well known issue. Now January 2026. Same problems. What’s happening inibuilds end?

That is not true, there have been several statements from the team regarding TCAS in the past. Regarding your VNAV Problem: I can't confirm it. During the Christmastime I did a lot of flights with the A350 on random connections (chosen with https://where2fly.today/). There was never an issue with VNAV, neither in occupied areas (Europe, USA), nor in lonely regions (Asia, Africa). Neither with handcrafted airports, nor with standard airports. I think, either your navdata is not correct installed, or there are conflicts between your flightplan and your navdata. Maybe you are using outdated waypoints somewhere in the chain? Well, it is definitely not a bug of the plane, since otherwise a lot of people would complain about this issue, and you are the only one.

An empty folder means an empty folder: Delete all (other) add-ons except the A350. In particular liveries, sceneries and tools.

Hi all, Hugely impressed with the scenery, just have a couple of issues I think are tied to the custom GSX Profile. I've already tried an uninstall/reinstall of both GSX and the scenery, ad the issue still persists. So far I've encountered 'No jetways here' or 'Invalid jetway data' at a couple of stands. 308L - 'No Jetways here' Despite there being one clearly there. 207/207R 209L/209 - Skips between no jetways here, and invalid jetway data. Not sure how many other stands are affected, so far they're the only ones I've noticed amongst the ones that do work correctly.

Hi Eddie, What do you mean ? The community folder is where MSFS is finding add-ons, what is an empty folder? Thanks,

They are still, we better hope it's good, although I have 1% hope ini can excel with these two aircraft with no violent pitch up or flight model issues such as wrong pitch rotation. it is getting more and more infuriating the days they don't fix it for the a350 and the a340, since they are very pitch sensitive on takeoff, and the system depth better be fenix level for such a legendary aircraft, atleast we know the modelling will be excellent judging from the emirates bar we have seen

Hello! I also have a winwing mcdu, and it's been a long time since this topic started, but it still hasn't been resolved. How did winwing manage to support your A340, but not the 320 v2, 321, or 330?

Can we get an option for this type of lighting too?

That to, and the only way to get them to fix stuff is discord, some things even here and on there say have been logged and untouched for months. Their discord moderation team is terrible, and some of those people who aren't staff staff and work for inibuids get the pre release aircraft even though they are terrible moderators *cough cough* I have one in mind, inibuilds needs to hire more staff not moderators 😂 I think with the overpriced aircraft they sell they can afford more staff...

I can't edit but the retard callout can cut off, this appears to be for the older airbuses I would assume with the ra callouts taking priority after idle, then it cuts off.

Still happening to me in MSFS2020.

it just hangs

Hello all! Tbh, I am really pissed off. Each update fixes something but break another thing. Now one of the essential feature is not working properly, which is VNAV!. Last time I've reported incorrect TCAS callouts but no one from ini team had a look at it. Now I am in trouble with VNAV (not happened just one time!). During the climb, aircraft stop climbing at random altitude even though there is no restriction or mode/target altitude change. For example, I set climb to FL240 with managed mode, but it stop climbing at FL120, then I push the altitude button, it continue to climb but stops again at FL175... So in order to reach desired altitude, I have to push the altitude knob several times, which is really annoying after some time! During descend, same thing also happens. I have to push altitude knob several times to descend to desired altitude. Again, no restriction or change on anything! There was not even any point in front of me for next 50 miles! And also, during approach with ILS, it randomly switches from G/S mode to vertical speed mode, literally for no earthly reason! A considerable amount of time has passed since the plane was released but we are still struggling with basic and essential bugs. I personally don't have unlimited time so trying to make a flight in very limited time window and do not want to spend my time with this kind of things.

Hello, I have KPAE for 2020 and now for 2024. In 2020 I can use the drone camera and go into the hangar and look at the planes being built. But in 2024 I cannot, I hit the outside wall of the building. I think it's the same airport right? Why is this happening? Is it 2024? I've only just installed 2024 last week. I tried to post this question in the airport section but I didn't see a KPAE for either sim. Thanks.

@AndyMThis is the correct logo for EGLL terminal 5A at least

Yes i do youse Simbrief and my CI was like 120 but i did a few flights, re installed and now it is gone so sorry to bother