IniSteve

The above made me chuckle. As for the erroneous TCAS error we have taken a deep look and suspect it's an external issue (we've seen reports of it happening in other addons. Despite that, we continue to check when we see reports and investigate when it's consistent.

Ownership notwithstanding, this is likely a nav database issue. Did you replace the base data with NG via their hub? Can you share the routing so we can take a look and see if there is a formatting issue causing the 320 to parse it incorrectly?

Do you have an autosave you can share?

For this kind of thing you should reach out directly to the Web assembly devs (W3C) as they can deep dive you into how wasm works and what causes exceptions. On our end there is rarely one unique cause for crashes. Some of the code we use is written in C++ and xml among others. Best of luck to you in your thesis!

Do you have an autosave you can share?

Hi all. We ID'd this as an issue in 1.0.6 and it should be resolved in the forthcoming update.

Hi. Please see this thread for the preferred method to report crashes. Following these steps allows us to diagnose your issue to see if it's something aircraft related or if it's more closely related to the sim. Thanks!

Thanks. I'll pass this on.

Thanks for passing this on. I'll pass to the scenery team.

Welcome to Airbus. 🙂 As others have pointed out, the AP disconnect function requires a double press- Once to disconnect autopilot and another push to silence the warning alarm.

All good. As someone who is also up quite early, I can understand how morning eyes cloud things 😉

Also, are you on our discord server? It will be much easier to do "live support" there versus here.

Ok, that's helpful. Can you confirm you're on the latest version and send a screenshot of "My Library"

What platform are you on?

It appears the WASM hasn't fully initialized. Try reloading the scenario and checking again?

Hi. Can you send images or video of your exact problem?

Hi. Not sure how you're interpreting the response this way. We have reach out to the MP team regarding approval and have yet to receive a response but we will continue to query them. Once we get an official answer we'll make an announcement.

Will pass this on to the sound team. Thanks

Rest assured. We do respond and we do track items but there is only so many times one can say "we will take a look at this" before it feels like we're just placating you. Despite that, again, the flight model is continuously being refined and looked at. The data we have checks out with what our subject matter experts say is correct behaviour but we field user feedback and try to strike a balance. Please also understand that updates to one facet of the FM can cause negative follow-on effects to the other states so we do our best to find an overall solution. With an aircraft as complex as the 350, this can prove to be a challenge. In any case, we are back from the holidays as of yesterday so this will pick up again and we'll continue to look at ways to make it as correct as possible.

Hi. Thanks for reporting. This appears to have snuck back in on the xbox build. We've notified the art team and they will sort it out for a future update.

Hi, the issue is known and we've put it on the roadmap for future update as it will require some model refinement.

Hi. We are aware of this and working towards a resolution for this crash.

Did you calibrate them in SAP and then in MSFS24?

We haven't changed anything drastically that would cause this. It might be worth flushing the package cache (uninstall/close sim/restart sim/redownload) of the aircraft to see if there was a conflict between versions. While I don't expect that to occur it wouldn't hurt.

Thanks. Can you share the procedure as well as exact steps just before the crash? Additionally, attach the autosave just before the crash if avail.