All Activity

The same is happening to me, taxi lights and landing lights not iluminating the ground, they light up in the external view, but they are not working properly. I cleaned my community folder, both of them, did a fresh install of the aircraft and the problem still presented itself.

This is the mistake. You can only program DIR TO waypoints out of your flight plan.

Thanks, now it works!

Hello all I have read the topic : "https://forum.inibuilds.com/topic/24979-how-to-direct-to-dir-to-a-waypoint-via-the-mfd-fms-or-nd/" But it does not work. What I do : I am ready to fly on a runway I have not set any FPLN I just want to set an AIRPORT as a DIR TO Waypoint I click on the DIR knob - set my airport name - Insert it as TMPy .. But when I go to the FPLN I stay on PPOS .. Thank you for your help and ...advices

Have had the same issue as you several times. Now just recently after a 3,5hr flight about to enter the final airspace. Not providing any logs since I ragequit and you're having the same issue. Have been able to reproduce this issue 3-4 times in my 5 days of owning the aircraft simply by just selecting or changing a STAR.

Do the wipers work at all? I just got the plane a few days ago and both the wiper switches has DEACT. stickers on them and are not clickable.

Here another screenshot of the ND

Hi everyone, I am having a recurring issue with the iniBuilds A350 in MSFS 2024. No matter which flight I plan, as soon as I import the SimBrief data and set up the flight plan, calculated points such as the Top of Descent are placed far away from the actual route, sometimes completely off the ND route line. As a result, the fuel prediction on the fuel page also becomes unusable and shows a negative value for fuel at destination. In my latest example, I planned a flight from EDDM to EDDH. The route appears broken on the ND, with green route segments drawn across the map in a “spaghetti” pattern. The FMS/ND also shows a point with a distance of around 2967 NM, which obviously makes no sense for such a short flight. On the fuel page, the trip/fuel calculations then show invalid or negative values, including negative destination EFOB. Important detail: I am not importing SID or STAR from SimBrief into the MCDU/FMS. I select the SID and STAR manually in the aircraft after importing the SimBrief flight plan. So the issue seems to happen either after the SimBrief route import or when the manually selected procedures are combined with the imported enroute route. In the screenshots, the suspicious item seems to be INPU3E. It looks like the FMS may be treating the SID name or procedure incorrectly as a route point, or it may be connecting the procedure to the enroute route in a wrong way. This results in a route distance of several thousand nautical miles and breaks the fuel/TOD calculations. What I have observed: The issue happens on multiple flights, not just one specific route. SID and STAR are selected manually in the A350 FMS. SimBrief is only used to import the OFP/enroute data and fuel/load data. TOD is calculated far away from the actual route. The ND route display becomes broken, with long route lines across the map. Fuel at destination / EFOB becomes negative. On the example EDDM–EDDH flight, a distance of about 2967 NM is shown, which is impossible for the planned route. The active nav database shown in the aircraft is 14MAY–10JUN. Steps to reproduce: Create a flight plan in SimBrief. Load the iniBuilds A350 in MSFS 2024. Import the SimBrief data into the aircraft. Manually select the SID and STAR in the FMS. Check the ND and F-PLN pages. Notice that route geometry may be incorrect, calculated points like TOD are placed off-route, and fuel predictions become negative. Expected behavior: The imported SimBrief route and manually selected SID/STAR should connect correctly. TOD should be calculated on the active route, and the fuel prediction page should show realistic destination fuel values. Actual behavior: The FMS seems to create an invalid route with extremely long legs or incorrectly placed waypoints/procedure elements. This causes TOD to be displayed far away from the actual route and makes the fuel prediction invalid, often showing negative fuel at destination. Has anyone else experienced this issue with the iniBuilds A350 in MSFS 2024? Could this be related to a navdata mismatch, procedure handling, or a bug in the way the A350 connects manually selected SID/STAR procedures to an imported SimBrief route? I have attached screenshots showing the broken ND route display, the F-PLN page, and the negative fuel prediction values.

I am having this issue in MFSF24. I just bought the plane and the only way I can start the modern with avionics that has the red starter pull is by starting on the runway. The starter is not clickable and CTRL+E will not start it either. The classic that has the small red button works and will start. If this plane will not start and is still broken then I think a refund is in order. This thing has been out a while and should not still be having this issue.

The clickspot issue appears on my end as well for overherad buttons. They are clickable, but the spot is tiny.

Are you able to add a video of this happening in the sim, thank you

Hi, I'll ask the team about this one as I am not to sure myself either.

Hi, I've logged this for the team, are you able to link a video of this happening in the meantime for me to add for them as well. Thank you

1 year later.. still no touchdown sounds.. Even when reported to asobo’s zendesk.. ScreenRecording_05-17-2026 11-16-54_1 2.mov

Exact same problem as yesterday - crashing while setting up the FMS. Not bothering with going through all the nonsense of posting what happened. It's simple enough to reproduce.

Can disregard this as there already another forum post that I missed when I first looked. Thanks.

Hello, I'm having what seems like one specific issue with PDC using the ingame ACARS on Vatsim. I can request my PDC (Pre-Departure Clearance) just fine. I get the clearance from ATC and I reply with the Wilco option. However this message is never sent or recieved by the ATC. Requesting push and start always results in me needing to recieve the clearance again by Voice. Using EasyCPDLC has no issues, so it's not an issue with Hoppie. When Airborne I can also connect to CPDLC, but I haven't used it enough yet to know if I can acknowledge CPDLC messages.

Everything on the plane uses degrees C, except for the cabin temp which is degrees F. Since everything else (including the air feeding the cabin) is in Celsius, could we get the cabin temp changed too please?

I finally found the solution by myself. If someone is interested, here is the configuration you should set in the "sensitivity" settings:

Thanks for your advice. I will delete all files in community and keep testing.

Bro,there must be something going on with your mods folder. I do regualr flights, all over 10 hours...

Here is the relevant SDK link and excerpt: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/CFG_Files/System/Pneumatic_System_Setup_Information.htm " Valve Modes When the pneumatic system runs, there are several modes that can be selected for the valves assigned to the system lines. However, these are not fixed modes that are only set once when the aircraft system is initiated, but instead they are changeable during the flight according to what the pilot does on the overhead cockpit controls. As such they are not defined within the CFG files by any parameter (although you can set them using the FLT file [PNEUMATIC_SYSTEM_EX1.N] section for specific flights or missions).   The possible valve modes available are as follows: Auto: The system manages the target status of the valve on its own. Manual: The target status of the valve is set by the pilot on the overhead. Open: The valve is forced open. Closed: The valve is forced closed.   When the valve is forced open or closed, it will ignore any target status change from the system. It should also be noted that an open valve can be set to a percentage open, for example 50% open. However, this does not mean that the airflow will be cut to 50% since a semi-closed valve will cause a pressure increase on the input side and so make the flow greater than the 50% one might expect. To have the flow match the percentage opening of the valve, the MaxFlow parameter can be set on the input Line, and this will block the flow proportionaly such that closing the valve will cap the flow rate at the percentage of MaxFlow corresponding to the percentage that the valve is closed. " Set is accomplished by: https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/Key_Events/Aircraft_General_Systems.htm#PNEUMATICS_VALVE_SET

Today directly while entering the A350-900. Installed everything yesterday new, cleared the Wasm. Another Saturday finished......

Oh I totally agree. It certainly should be possible in an aircraft that is the ‘ultimate airliner experience’ and has ‘unparalleled realism’.

I'm experiencing the same issue. MSFS2024 works fine, but MSFS2020 crashed when I selected A350 ver.1.2.6 and loaded a flight. This happens even with the default inibuils livery.