Eddie

Hello, I've forwarded this to the team. Thank you!

Hello, We are nearing the Xbox release; just wrapping up the testing and hopefully roll it out to you all soon! Thank you for your patience! 🙂

Hello, Thank you for sharing your findings! 🙂

Hello all, The update we just pushed out (1.0.11) addresses these concerns as per: "UPDATED: Elevator trim blending logic proposal for smoother rotation handling when transitioning from ground to air OIS" from the change-log. We've worked on it extensively and recommend you all to try again with this update. 🙂 Let me know how it feels and enjoy! Thank you for your continued feedback and have a lovely weekend.

Hello, Unfortunately, as much as we wish there is a "final indefinite fix", that simply is not possible. Most WASM crashes are either extremely specific to a certain routing, departure, arrival or specific action done on the aircraft and even if properly reported to us, we sometimes may not be able to reliably reproduce the specific issue to fix it. I understand it is VERY frustrating and I assure you, we feel that frustration right alongside you. We have fixed hundreds of reported WASM crashes already and continue to do so. Regardless, MS/Asobo are actively looking into further WASM stability that will hopefully stabilise it going forward. If you have the time and would be willing to help, getting us steps to reproduce this will help us at least investigate the specific WASM crash you have experienced: Thank you for your understanding and we sincerely apologise for the inconvenience. Have a lovely rest of your week! 🙂

Hello, Apologies for no reply here! We've identified the problem and are working on a fix; I assure you it's a priority. Apologies for the inconvenience!

Thanks for the video, I've forwarded this to the team. As for the 320Nv2 issue, again, I truly understand that it's frustrating but these are Microsoft products and we have no say on update distribution. Lastly, your follow-up reply is extremely unnecessary seeing as it hasn't even been 24 hours since I last replied. Refer to my signature for my actual position as the forum tag has nothing to do with it. Thank you

Hello Please check in SU16 for MSFS2020 if this issue persists and let me know (in regards to the 320NV2). If not, please reach out via MS/Asobo's support Channels for further enquiries regarding this issue. Much appreciated! As for the A350, I'll give it a look and log if able to reproduce. Thank you for taking the time to type this up and apologies for the inconvenience.

Hi again, A cabin will not be made for the MSFS2020 version of the A350. The A350 has art effects in BOTH simulators already.

Hi there, Custom cabin announcements have been suggested in the past and we are looking into ways to incorporate that into the aircraft. No promises on when that could come 🙂

I am not sure I understand what you're asking. When is what? There is no cabin for the MSFS2020 version and no plans on implementing that. The ART effects are present across both simulators.

Hello, If you haven't tried already, please clear your scenery indexes and make sure any default scenery for KJFK is disabled via the content manager. To clear your scenery indexes, locate your folder by following the path below: MSFS 2020 MSFS 2024 Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS. Most times this resolves any uneven terrain as well as other issues. Thank you 🙂

Hello, This is not forgotten about. It is on our list. I cannot confirm/promise which update this will go into as it is unfortunately not a priority item at the moment. Thank you for your patience and understanding! 🙂

Hello, I am very sorry to hear that you've been experiencing this issue. As you can see by the original thread creator here, we need a few more details to be able to action these WASM reports. They're rare and differ greatly from person to person. Sometimes they're common and its an easy fix, other times we need said person to give us their specific report so we can squash that specific WASM crash. Regardless, we are finalizing testing on version 1.0.9 and that version also comes with a slew of WASM-crash fixes. Please take a look if all is well in that version. Thank you for your patience and understanding!

Hello, Please ensure the DEFAULT Asobo EGLL is disabled in the content manager in-sim. If yes, try clearing your scenery indexes. To do that locate your folder by following the path below: MSFS 2020 MSFS 2024 Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS. Let me know either solves your issue.

Hello, Very sorry to hear that you've experienced a WASM crash. While this is not a guaranteed, please clear your WASM folders just incase: I'll forward this to the team. Thank you 🙂

No worries at all. I'm glad you figured it out! 🙂 Let me know if you need anything else! Thank you

Hello Peter, Can you please grab me a clip/video? Are you scrolling or literally "grabbing" by holding click and dragging up? Thank you

Hello, Thank you for the report. Will take a look and apologies for the inconvenience!

We're working hard on the 1.0.9 update doing our best to ensure this no longer happens! Your patience is very much appreciated. Thank you

Hello, Thank you for the follow-up. This should be resolved with the coming 1.0.9 update 🙂

Oh my.. so.. I may or may not have misread the category. So used to replying to A350 threads. Terribly sorry!! Unfortunately, the A400M does not support physical input, no. I believe it has been requested to MS/Asobo in the past. We'll see if we'll be asked to implement this or not. Again, apologies and thank you 🙂

Ok thank you

Hello, Apologies, missed this. Can you clarify which of the autosaves is more relevant? We preferably need one. Thank you!

Hello, Can you specify what sounds specifically? Perhaps a short video of the problem so that we can investigate. Thank you 🙂