IniSteve

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.

Hi. Im trying to understand what exactly your issue is. Is the gear not retracting or did it deploy in flight unexpectedly?

Great to hear! I will lock the post but leave it up for others in case it happens again.

Keep me posted.

I am convinced something else in the sim is causing all these conflicts. While it's not the most elegant solution, you may consider a reinstall as a "nuclear option" to reset everything and then slowly add 3rd party content back in.

Here is video of my takeoff after a rwy spawn with no data input. After takeoff, you can even see where I release the stick and the nose settles again as the trim hasn't quite caught up with the aircraft. What jumps out to me in your vids is the FMA is indicating a VSI of +10000. Not sure where the aircraft is getting the pitch up command from. Are you certain every single assist is off in the menus? 350 Rotation.mp4

Deep breath... We can get through this. The display issue is a byproduct of a change in SU4 memory handling which we are actively working to rectify (it's causing us the most frustration) Are you on our community discord? It may be easier to provide live support there if so.

We aren't seeing this widespread and aren't able to reproduce this in testing. Despite that something is amiss as you can see. Ruling out assist my next suspicion is you have a conflicting addon that is commanding this sudden pull up. Can you remove all add-ons from the community folder (You can simply rename the current folder to "_community" and the sim will generate a new one on launch) then install the A350 in the fresh folder. Afterwards, try to replicate this and see if it continues. Can you also send an autosave if possible and furnish your flight route and OFP

You have auto assistances enabled. Turn all of them off and then see if this behaviour continues.

Glad to hear your issue is sorted, Paul.

FS20 has yet to receive any major sound modifications so it's possible your ears are deceiving you. Once we update it to the same standard as FS24, we'll make an announcement, and you'll be able to tell. 🙂

Hi Aya, Thanks for the report. Can you confirm which console variant you own? (X or S) There is def something wrong with the version if you're seeing 1.1.4. You followed the correct method to reinstall the product, but I would confirm that doesn't happen again. Regarding the the bugs we've already logged the Terrain/Navdata issue but it's something new affecting only xbox so we suspect it has do with memory management. The display issue on load is related to something in SU4, which we are also actively investigating.

Which variant of the Xbox are you on (X or S) and where/what kind of conditions where you flying? Xbox seems to have pretty aggressive memory management from what we've seen and while we've tested the aircraft in some pretty memory heavy areas (350 at EGLL in poor wx) there is a chance you found the perfect scenario to tax it further. Reply to this topic

The dev has pushed a compatibility update and since you own the product, it's available to you.

Thaks for the feedback. I'll pass it on to the sound team.