While the overall A350 product is mature and can be very enjoyable, I'm writing this post in a sort of frustration. I believe most of these bugs are acknowledged in some form either here or on discord. However updates after updates - none has been resolved. 

I list them here for clarity. 

1) CRUISE PAGE - LDG ELEVN

- This should be rounded to the nearest 50ft based on the runway elevation. I.e. WSSS 02L Rwy is 22feet based on Navigraph charts - this gets rounded down to 0ft. At the moment the aircraft displays this as 100ft which is incorrect. 

- If it is 30ft and above - it gets rounded to 50ft. Like wise, if it is under 80ft it gets rounded down to 50ft, and so on. Above 80ft and up to 130ft, it gets rounded to 100ft. 

- The Landing Perf Page on the OIS shows 23ft so this data is obviously available somewhere, and just needs tweaking on how it is displayed on the CRUISE PAGE on the ECAM

2) HYD ELEC Pump on HYD Page

- When the cargo doors are opening - the ELEC PUMPS on the HYD page do not reflect the current status that the pump is running and shows no PSI on the Yellow pump

3) Take off and Landing ECAMs

- This NEEDs to be addressed. The A350 (like the A380) is different to the older airbuses. The formatting has been an issue that's there since the start, and has NOT been fixed despite multiple reports

- T.O ECAM (See FBW A380 for reference) should be:

SIGNS or SEAT BELTS ON

GND SPLRs ARM <- currently the iniBuilds A350 still shows SPLRS (capital S) at the end on T.O ECAM Memo

FLAPS : T.O <- iniBuilds A350 missing the "." between T.O

AUTO BRK RTO

T.O CONFIG NORM <- iniBuilds A350 again missing the "." between T.O

- LDG ECAM 

Similar issues with GND SPLRs <- iniBuilds A350 does not even display the "s" just GND SPLR

4) HUD FPV issue - currently using community mod for this

5) VSD display on initial level off altitude not shown (see another topic since 1.2.1) / VSD does not display V/S profile when using V/S mode

While issues 1, 2, 3 do not affect flying as much - some of these things are what makes an A350 an A350. The immersion factor is immediately lost or reduced as soon as you notice these things on a flight. These things are understandable if this aircraft was literally released today, however after 20+ updates and 14months since initial release, this is getting a bit ridiculous. 

Issues 4 and 5 might be harder to solve - at least for issue 4 we can use the community mod for the HUD. 

Thanks for your efforts in looking into these things. 

Cheers,

Chen

It is easy for us all to flag things when they don't go right, but we don't always share positives. So, I just wanted to say I have now completed a couple of flights with v1.2.5 including a longer sector using time acceleration. I have repeatedly kept changing the arrival rwy/star during the flight to see if it breaks it but so far I have to say it is taking it in its stride.

Well done to the team.

Regards,

Kevin

I’ve just updated to v1.2.5 and completed a few flights. I noticed several issues that seem to be new or persisting. I would appreciate it if these could be fixed in the next update.

• Autopilot Disconnect Sound: When the AP is disconnected, the alert sound stutters or is momentarily interrupted.

• LNAV / Direct-To Issue: When executing a "Direct-To," the aircraft does not follow the LNAV path correctly and turns in an unexpected direction.

• Autobrake Disarm Voice: The "Autobrake Off" callout is extremely quiet (like a whisper) and hard to hear.

• TCAS Reset on Takeoff: On my second flight, even though TCAS was set to ON/TA-RA, it automatically switched to OFF upon rotation/takeoff.

• Company Message: The "Company Message" notification still does not disappear as expected.

Thank you for your hard work on this project!

Just trialled the A350 v1.2.1. 

Re: VSD - glad to see some updates e.g. magenta area pre-departure. However have noted regression on the vertical profile no longer showing initial/non-cruise altitude level offs during climb phase or descends, with the predicted profile in dashed lines. 

V/S mode still not showing predicted profile - I believe this is known. 

See video of depature and climb - 

Thanks

I am currently experiencing an issue where the ILS signal is not being captured while flying the iniBuilds A350-900ULR (No Cabin model).

Here are the specific details of the problem:

• Symptoms: The ILS frequency appears in magenta on the bottom-left of the PFD, indicating that the aircraft has tuned to the station. However, the ILS scales (diamonds) do not appear, and the signal is never captured.

• Troubleshooting Performed:

  • I have tried manually tuning the ILS frequencies in the RAD NAV page.

  • I have verified that my Navigraph AIRAC cycle is updated to the latest version.

  • I tested multiple airports (including default sceneries) to rule out specific scenery issues, but the result remains the same.

• Comparison: Interestingly, RNAV approaches work perfectly fine. Both the Localizer and Glide Path indications appear and can be captured without any issues.

Is there a specific setting or a known bug regarding the ILS reception on this version? I would appreciate any guidance on how to resolve this.

Best regards,

While the issue doesn't appear bad at first you quickly realise there is also no control of the plane itself. I couldn't disengage AP and fly it manually as pressing the buttons did not do anything, neither did cycling the battery, switching displays or anything you might expect would solve the problem physically. This is definitely a bug and I dread to even imagine this happening in real life as it would be fatal.

The only other time I've ever had this same issue occur was right at the beginning of FS2024 in the A320 V2 but I was still able to land as it occurred right on approach and I still had control of the systems. I've also had similar freezes on the A330 trying to use the SEC FPL option or simply during flights consecutively where the screens would simply stop responding and once turned orange with a WASM fault occurred message. The issue now seems to have manifested itself on the A350 and results in complete control loss.

Spoiler: The plane kept descending in a straight line, off the approach, and eventually crashed into the ocean about 8 minutes later. Kind of haunting..

I'm pretty certain this is not a system error relating to my PC since it doesn't behave as such and the thing is still running. I've had many successful flights in the A350 and that includes ones which were +12 hours with successful landings. This issue occurred after 4 hours and usually occurs after 2-3 hours.

https://youtu.be/z3ZFCs-PtIU

I've also sent a ticket via email to support to officially register this problem along with any logfiles and save files

I've read somewhere that you are aware of this and you "think" you know what's causing this and are in direct discussion with Asobo to try and rectify this

Would you consider adding a little more functionality to the Air Data Switch?

I believe when selected the associated FD should be removed and the PFD message BKUP ALT/SPD with the degraded amber = should appear.

Kind regards

If I overspeed the aircraft the protection kicks in correctly but then the program exits and resets as it detects a crash condition, what settings do you need for it to be less sensitive or work correctly?

Thanks

I have just tried the OZZZI 2 arrival into ATL.

Using DES mode the logic completely ignored the manually entered 12000ft at OZZZI, and the stored 9000ft at CALLA and went straight down to 8000ft using the restriction at POSEY.

Is DES mode modelled?

Thanks

Adrian 

Any one else experiencing this or any suggestions.

Thanks.

I am using this great AIRCRAFT starting in FS2020. Now in FS2024 and before SU5 all was running fine.

But now I have these problems

1 - If I start a flight and choose a runway (so not in Cold and Dark), the aircraft crashes but the sim set it "in the right way" ..

2 - I have got a WASM pronlem (orange screen) and had to restart the sim

3 - There is a problem with the data SIMBRIEF send - they are not well received by the Aircraft - For exemple the ZFWG was wrong and the P-FPLN is not received (the Recieve F-plana button is not active)

Thank you for your help

I recently got the a350 and since installing it I've had issues with the EFB not loading properly. I have tried clearing the WASM folder which did not do anything.

Attched some screenshots of the issue I am expierinecing.

I am on version 1.2.5, installed via the inimanager.

• Aircraft: A350-900
• Simulator: FS2024
• Navdata Method: NAVIGRAPH
• OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes
• WASM Error: It for some reason only shows vdgs related items? But clearly the displays are frozen and my A/C is flying to the northeast instead of east. 
• Specs: Ryzen 9800X3D, RTX 4080 Super, 32GB of RAM
• Autosave File:  Included

JX119_YWG_FRA.pdf 1766248844.bin

After updating version 1.25 these days, I used the new version to fly the ZBAA-LSGG-ZBAA route. The first leg of the flight experienced a simulated freeze and the plane crashed directly. After about an hour of recovery through AUTO SAVE, the simulated freeze occurred again and the plane crashed again. After recovering through AUTO SAVE again, it returned to normal. After landing, I cleared the WASM folder. After about five hours of flight, the second segment of LSGG-ZBAA experienced simulated freezing again. The plane deviated from its flight path and spun around. Normal after recovery through AUTO SAVE. Fly at double speed throughout the entire journey.

The previous 1.24 version also experienced simulated freezing, but after clearing the WASM Wenjia folder, it did not freeze again. Frequent freezing occurred after updating version 1.25. Yesterday, I flew back and forth for a one-way trip of three hours, totaling six hours. Everything was normal.

2 - on the Fenix Airbus planes when you import a flight plan using Simbrief, the charts such as ground sid and stars for both airports are pinned already so we don't need to go looking for them , the SID/Star charts are what simbrief recommended.

Thanks for your time 

Shrek!

hope you’re all having a great day.

I usually prefer to disable the GSX Remote Control, as I actually enjoy using the GSX toolbar in-sim a bit more. Also, the flashing orange indicator in the OIS was starting to get a bit nerve-wracking.

However, since doing this I keep running into an issue where GSX only detects 1 passenger, even though my SimBrief flight plan shows the correct (and much higher) pax count.

My ideal workflow would be:

– set fuel to instant via the aircraft / EFB

– then load passengers progressively via GSX

Has anyone found a reliable way to do this with the iniBuilds A350 in MSFS 2024?

Or is this a known limitation / bug when the GSX Remote is disabled?

Would love to hear how others are handling this.

Thanks a lot and warm regards,

Claas

If I'm doing a long flight I switch on auto 4x and go do other things. I've had these issues. 

Multiple times - I've come back and MSFS has COD. 

Once so far - I've come back and MSFS is still running and you can click on things / move around / escape to menu etc but no instruments in the cockpit are responsive. 

I've been able to complete long flights on auto 4x before so not sure whats changed. 

Thanks, 

To rule out external causes, I use no overlays, keep the A350 up-to-date  at all times and systematically disabled all other add-ons in my Community folder step by step to eliminate possible conflicts. None of these measures resolved the issues described below.

1. WASM Crashes
   If I do not completely delete the WASM folder before every single flight, I experience random WASM crashes in virtually any phase of flight. Most frequently, this occurs while entering arrival and approach data into the MCDU. The crashes are unpredictable and make normal operation impossible.

2. Autopilot and Cockpit System Failures (without WASM crash)
   In addition to the WASM-related issues, I regularly encounter situations where autopilot and other cockpit systems simply stop functioning without any visible crash. The aircraft starts to deviate from its flight path and becomes uncontrollable. At that point, the flight cannot be continued in a meaningful way.

3. Autoland Touchdown Rate
   The autoland behavior appears rather firm, typically around 350 ft/min. I am not a real-world pilot, so this is only a subjective observation, but the touchdowns feel noticeably hard compared to what would be expected from a long-haul aircraft of this class.

Due to the frequency of especially the first two issues, I have temporarily uninstalled the aircraft. This is disappointing, as I truly want to enjoy and use this product.

This post is not meant as an attack on the developers or the aircraft itself. On the contrary, it is precisely because of the A350’s potential that these issues are so frustrating. I would greatly appreciate any guidance, troubleshooting steps, or clarification regarding known issues and upcoming fixes.

Thank you for your work and for taking the time to look into this.


PC Specs:
CPU: Intel i9-14900K

GPU: RTX 4090

RAM: 64 Gb

OS: Windows 11