[Displays Become Laggy and Non Responsive - No WASM Crash in Log]

12 hours ago, lpf20011 said:

I keep getting situations where the displays look like they have a WASM Crash, stop responding completely or become very laggy and then freeze. Checking the console log there's no WASM Crashes listed - is there anything I can do to interrogate when this happens again? 

If there's any way you could take a video of what's happening, or keep track of what you did leading up to the displays becoming laggy? It would help a lot to identify what could be causing it 🙂

[OTHH - ILS is not detected in the A350 at Runway 6L]

5 hours ago, marc_78 said:

Okay, it looks like it's not working at any other airport either. I just tried it in Frankfurt. The latest Navigraph data is installed. I just uninstalled and reinstalled the plane. It didn't help, though; the old settings remained. Any idea what else I can do?

Could you try deleting your WASM folder for the A350? You can find it here:
 

 

[A350 Pause at T/D distance limited]

17 hours ago, mseder said:

OK, should have noticed that. Thanks!
"calculated T/D from the FMC" so why not put 0 in order to get as close as possible to that estimate?
80nm in advance seems like a really huge preparation buffert.

 

There's a lot to do before descent - Get destination weather and ATIS, plan and brief your Arrival and Approach and insert it into the FMS, do your landing calculations etc. 80nm is only about a ~15 minute buffer for all that 🙂

 

[The A350 cannot load the flight plan on Simbrief.]

On 8/20/2025 at 9:45 AM, CUA9199 said:

The A350 cannot load the flight plan on Simbrief.

Hi CUA, if you are flying within China it's very important to make sure that your navigation database in the A350 matches that within Simbrief. There are some airports in China that exist within Navigraph's navadata (used by Simbrief), but do not exist in the default sim navdata. If one of these airports is in your simbrief plan, it will fail to load the plan in the A350 unless you have enabled Navigraph navdata.

[A350 ULR on Xbox]

6 hours ago, Kostya said:

Hello dear developers! I encountered a bug in Airbus A350-900 ULR on Xbox. I was planning to fly the Singapore-New York route. Simbrief calculated 124 tons for the flight, so I was going to refuel the plane, but I encountered a bug. The plane refueled 110 tons, which was the maximum, but the calculations indicated that it should have refueled 124 tons. I sincerely ask you to fix this bug in the next update of A350 on Xbox. Thank you for your attention!

Hi Kostya, We've been able to log the issue on our end as well, it seems to be specific to the Xbox version. I've made a note to the devs.

[A350-900ULR not working on Xbox]

25 minutes ago, Bk bro said:

Yes because when I load in to the game, it says A350-900 and I know it’s supposed to say A350-900 ULR (In the FLT OPS STS page) and the load sheet also shows 324 people and I know that the ULR only carries 160 ish. Also when I try to load in let’s say like 278,000 pounds of gas(from simbrief) but it then corrects it to 234,000 pounds which the regular -900 is capped out at.

Hi BK, So we've been able to recreate the issue on our test build, I'll make a note for the devs 🙂

-Steven

[Pink planes since last update A350]

Hi,

Do you have the livery packs downloaded? If so, try deleting the installation and letting them stream, that way they will be on the newest version alongside the airplane.

Let me know if that works 🙂

-Steven

[Frame Stutters every 4 seconds]

On 8/18/2025 at 11:10 AM, Sirraj said:

The stuttering problem with GSX has been completely fixed for me. The A350 is now very smooth throughout the flight and everything is working in MSFS 2024.. Thank you the continuing updates, I couldn't be happier with this aircraft.

Sirraj

Thank you for the kind words! 🙂

[v1.1.4 TERR an VSD bugged]

Any chance you can give a more precise location so we can try and recreate? 🙂

-Steven

[OTHH - ILS is not detected in the A350 at Runway 6L]

So it seems to be working for me, can you confirm you're on the newest Navigraph navdata?

[CTD, on the same route and at the same point of the route at cruise level 370]

8 minutes ago, jose luis said:

I was flying from EKCH to RJTT with the a350 on msfs 2020 and I received a ctd, it's the third time I've done the same flight and all 3 times in the same area and about 5 and a half hours of flight, at the same point, I receive the ctd, the approximate coordinates of the ctd are 47°49'14.0"N 068°48'57.0"E I don't know if it's because of the plane or because of msfs 2020. I will write in the flight simulator forum to investigate it please. I will also try with another plane with the same route, I will send you a screenshot of the error, sorry for my English.

 

Hi Jose, We'll take a look 🙂

What version of the plane were you using? We did recently fix some WASM crashes related to specific areas of the earth in 1.1.4. Could be related to this?

-Steven

[OTHH - ILS is not detected in the A350 at Runway 6L]

I'll give it a try right now 🙂

[A350 Seat Belt Sign]

2 hours ago, Jurian Roy-Mahoi said:

I was using both. 

Seems to work in the default cabin but broken in the cabin pack cabins. I've made a note 🙂

[A350 Seat Belt Sign]

3 hours ago, Jurian Roy-Mahoi said:

Flying the British Airways G-XWBM A350-1000.

cleared WASM folder and done a fresh install of the aircraft but no luck. 

Could be specific to the -1000, I'll give it a try on my machine and see. Also just to confirm were you using the default cabin or the British Airways cabin pack cabin?

-Steven

[OTHH - ILS is not detected in the A350 at Runway 6L]

2 hours ago, marc_78 said:

Hi, I wanted to fly to OTHH yesterday with the A350. I loaded the Simbrief plan as usual, using the latest Navigraph cycle. Unfortunately, despite repeated attempts, the plane didn't detect the ILS for runway 6L during the approach, nor did it detect the LOC. I installed the new OTHH scenery. Then I noticed that the Navigraph data shows a landing course of 156 degrees, but the Navaids show 155, although the frequency is correct. Does anyone have any idea what might be causing this or have had similar experiences?

Hi Marc,

Just to confirm, was the ILS 16L approach was selected through the MCDU and tuned on the NAV AID page? Would you happen to have any screenshots of the behavior so we can try to recreate it?

Best,

Steven

[terrain radar does not appear on the first officer's screen]

On 8/14/2025 at 1:20 PM, jose luis said:

Hello, I use msfs 2020, and I don't know if it's a bug in the plane or what, but I can't see the terrain radar on the first officer's screen.

Hi Jose,

It should be working in 1.1.4, give it a test and let us know 🙂

Best,

Steven

[A350 Pause at T/D distance limited]

On 8/14/2025 at 6:03 PM, mseder said:

Setting pause at t/d has never been working as I can't set the destination distance to more than 100 nm (cruise level max 300)
Any plans to fix this in the future?

MSFS2020

Hi Mseder,

The distance for Pause at T/D isn't from the destination, it's from the calculated T/D from the FMC. For the record, I've been using 80nm myself as that's what the FCOM suggests as when to begin descent preparations and it works wonderfully.

Best,

Steven

[A350 Seat Belt Sign]

On 8/15/2025 at 6:06 PM, Jurian Roy-Mahoi said:

After installing the new update and clearing WASAM folder, anytime I switch on or off the seatbelts sign. They still remain on. 

Hi Jurian,

I'm doing a flight right now and they seem to be working in the -900 variant, could you let me know what variant you're flying so we can try and re-create?

-Steven

[Frozen ND, PFD and CDU after 2hr of flight.]

Hi Seric,

This looks like a WASM crash, we've made some updates in this most recent build (1.1.4) that should help fix crashes that were caused in higher latitudes, so I would try updating to the latest version if you can. 

In the meantime, you can see our thread about how to document and report WASM crashes so that we can better re-create and troubleshoot them amongst our testing team. See here: 
 

 

 

Best,

Steven

[A350-900ULR not working on Xbox]

Hi BK Bro,

I've noted your issue so we can try and re-create it, but in the meantime, are you 100% sure it's loading the regular -900 variant? The -900 and ULR are visually identical so keep that in mind 🙂

-Steven

[CPNY T.O. REQUEST gives weird data.]

On 8/5/2025 at 6:28 AM, Prophet said:

Any update from iniBuilds regarding this issue?

Hi Prophet,

Apologies for the wait here, I've logged this for the devs to see 🙂

-Steven

[PC A350 "OIS NOT AVAIL"]

9 hours ago, Pilot_Ash said:

Please help, I can't seem to find anything about my problem, no matter what I do the EFB always ends up with a black screen and orange text saying "OIS NOT AVAIL"

Hi, if you set the EFB to "realistic" boot time, it will take 8-10 minutes for the EFB to boot up and be usable. Personally given the necessity of the OIS for interacting with the sim I'd just recommend leaving it on "instant" 🙂

[Aircraft does not follow speed and altitude restrictions properly during approach - Serious VNAV problem]

8 minutes ago, dectenor1 said:

I have made various reports on issues relating to VNAV stuff, F-PLN page predictions and how these are displayed, managed speeds, and again how these are displayed, constraint behaviour etc., etc. Please feel free to reach out for any info that may help in this regard. VNAV related things need a LOT of work currently!

Best

Hi Dectenor, 

Yes, I've seen your thread as well and been going through it. Definitely agree the VNAV needs work and that is something I am working with our RW A350 pilots on helping to improve.

Best,

Steven

[A350 Plane entirely unresponsive]

Hi Typuppy,

This looks like a WASM crash - they're a bit tricky to isolate the exact causes of so we've put some information on how to report them here so we can hopefully recreate and fix them. See below:

 

 

[Frame Stutters every 4 seconds]

1 hour ago, Sirraj said:

This problem went away for me. But yesterday I uninstalled MSFS 2024 and reinstalled the SU3 beta and the stutters are back. Do we know if this is a problem with the A350 or GSX? I've seen a few similar reports on discord.

We were having an issue with GSX that has been fixed for the next update that was causing stutters specifically during boarding/deboarding. Also, at the current time the A350 is not officially compatible with SU3 so for best performance I would stick to SU2.