IniSteve

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.

Hi. While we understand the frustration, much of what you're taking issue with has nothing to do with the aircraft and more a byproduct of the platform. (We don't turn off screens or hamper basic functionality with any xbox-specific performance culling) Unfortunately, we can't prioritize how the console prioritizes memory handling so sometimes what gets removed in one flight won't be the case on the next. Knowing that I can assure the Xbox builds have received the same updates and refinements as with their PC counterparts (as much as possible) We test each build as much as possible but it's inevitable things may sneak through. Can you share specific examples of switches that are requiring more than one input so we can take a look? Thanks.

Hello. Which Xbox are you on? (X or S) The S is pretty constricted in the way it handles memory management and it will cull (turn off) objects as required to prevent lockups or crashes

Where you in or near a region with active GPS interference? If not, did you inadvertently turn off one of the ADIRS switches on the overhead?

Hi. I have these throttles. You should configure them in SAP as follows - Select Single-stroke double shaft as this will allow full range of the axis to transmit as a single fluid motion. Then in MSFS you should config them as follows - (Mirror RaxisX controls to Throttle 1 & 2 and RaxisY controls Throttle 3 & 4) Now in the A340 EFB you should set them up as "2Axis" and assign the points as desired This should resolve any conflicts and allow use as intended with full reverse range.

Hi. All your marketplace content should be available on PC provided you use the same MS/Xbox login.

I've passed this on to the scenery team. Thanks

Hi Paolo, Thanks for your suggestion. As I'm sure you're aware, the A330 was made directly for Microsoft. If you have suggestion on how it can be improved, we recommend you make a post on their forums. They are the ones who can decide the upgrade path. Thanks!

Logged and sending this to the sound team for further investigation.