IniSteve

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.

Hi Thomas. Understand the frustration but this doesn't seem to be a widespread issue. Can you share your autosave and OFP/Flightplan details so we can try and reproduce the crash internally? The changes made to the model to reduce node and bone counts were really necessary, and not just for those on low-end hardware but even for those on higher end hardware, especially Intel and non-x3d chips. As mentioned in our post these changes significantly reduced stutters when looking around the aircraft or changing views, which of course benefits all of us even on the highest end chips and also helps with stability as these stutters can affect that as well. Regarding the cabin packs, unfortunately these changes broke them completely, and they were already very difficult for us to maintain as any minor changes to the interior 3d models had to be repeated manually for every cabin pack across every variant. With this change, it was a bit of a final straw, and we've decided that the time and resources needed to maintain them is simply not sustainable for us as these efforts are better focused on the core aircraft as well as our other upcoming projects. Hope that helps clear up the factors that led to our decision and helps everyone understand it wasn't taken lightly. (for others following along, I deleted the other posts that were not relevant to OP's issue so we can all focus on helping him)

logged. I will pass this on.

Hi Daniel. We are aware of the zoom limits on the 350 and are investigating the issue as it works correctly on our other aircraft which have the same boundary limits. Thanks for your patience while we figure it out.

OK, barring a line-item response to everything reported in OP's post I can say we take each and every one of these reports seriously and track and log them on our issue tracker. We know it can be frustrating when certain bugs linger or when smaller QOL items take longer than expected to resolve. Behind the scenes, our workflow is to prioritize fixes based on impact, reproducibility, and the resources we have available. Showstoppers and issues that impact use naturally rise to the top, but we also need to ensure those fixes don't cause follow-on issues, so the overall experience keeps moving forward. It’s a constant balancing act, especially when the same team is also maintaining existing products and supporting new development. Items like the HUD however are already set to receive a deeper update in the future. (Our intention is to completely rework the HUD but as you can expect these updates take significant time and resources, so they are planned out in stages) That said, we genuinely appreciate the patience and constructive feedback from the community. Your reports help us reproduce problems faster and understand which issues affect the widest group of users. of course we can’t fix everything at once, but we remain committed to steady progress and to delivering updates that meaningfully improve the experience for everyone.

Hi, We used high resolution mesh for the area but we're happy to take a look at further references if you have them and they are authorized for free commercial use.

Hi all, We are tracking this issue. We're not entirely sure what happened as it was working as expected in the RC so we're investigating. We have earmarked a hotfix for the known issues for this coming week and will try to rectify this and get it in as well, but we appreciate your patience in the meantime. Thanks!

Thanks for this feedback. I've passed this post on to the art team.

Thanks. I will forward this to the sound designer.

Not really no. We have found the sim itself exhibits poor stability above 4x so trying to combat that is a challenge.