iniSteven

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

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

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

I'll give it a try right now 🙂

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

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

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

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

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

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

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

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

All systems updates in 1.1.3 are for both 2020 and 2024. It's only the art changes that are for 2024 only.

This specific effect is only compatible with 2024 with the windshield effects option turned to "high"

Hi Prophet, Apologies for the wait here, I've logged this for the devs to see 🙂 -Steven

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" 🙂

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

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:

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.

Thanks! I will see if I can recreate.

Hi Ekosif, I've been working on tracking the VNAV system and documenting its behavior for the dev team. I see you're flying an arrival here, but you could let me know the specifics of which arrival? I will try and fly it myself to see if I can recreate the issues. Best, Steven

Hi, does this occur with other aircraft as well or just the A350?

Could you give us some more information? Was this in 2020 or 2024? Which gate were you at? Did you select your parking gate through GSX? I've just hopped in to the sim and the VDGS is working for me, so this information would be good to know so we can narrow down the issue.

Hi Mopy, we've been tracking this bug and it should be resolved in the next update. Appreciate you bringing it to our attention 🙂 -Steven

Hi, this bug is being fixed, there should be an update available soon that will correct this issue.