BoeingSpeedbird

I only fly on MSFS24 and only fly A320n and A350. My staple has been the A320n and I thinks it’s pretty good. No problems as you’ve described. So, not sure what’s going on for you, but it can’t be a systemic A320 or MSFS problem or loads of others would be reporting it here.

The danger with AI - not always accurate - there’s mention of problems with flying on Vatsim with Xbox!

Consistent failure to load into Zurich with the a350-1000 - constant crash and /or memory low warning and/or WASM orange screens. Is anyone able to load into runway into LSZH?

Again, not what I experience on Xbox x a320n v2, so I wonder if you need to delete and re-install.

I’m not experiencing this as such, but I’ve noticed the 3 beeps on autopilot disconnect are now barely audible, which is significantly different from the loud beeps there used to be. Doesn’t matter what audio settings I change to address this, nothing changes. Xbox x, a320n v2

Interesting - consistently, if I take off from Glasgow by spawning onto runway, the a350 will not follow flight plan after takeoff. However, using the same flight plan, if I start from the gate, then it will follow the flight plan after takeoff. Any ideas?

Removed the SoFly Aerotone new addon - problem now seems fixed.

Worst day ever - 4x flights - every single had the Xbox equivalent of CTD almost all an hour into fight. So annoying. This has never been so bad.

This has been a problem on Xbox on 1.2.1 and 1.2.2 (we don’t have 1.2.3 yet). Interestingly, took off from Glasgow tonight and started from the gate - no problem after takeoff - NAV engaged successfully. Typically, I spawn straight onto the runway. I wonder if starting from gate, for some reason, makes a difference?

You have the 1.2.2 but it’s just the OIS states the older version.

Then this is wrong.

Is this only a PC update today? If so, when Xbox?

Long haul from Kuala Lumpur - 2 hours in and this is the UTC data. What’s going on? If I re-insert the landing airport (EGCC) and STAR then, for a short while, the UTC info corrects, but it goes rogue again quickly after. Why? On Xbox.

2020 was the future once.

Thanks for following up; appreciated. It was only recently that one of your colleagues mentioned that the published recent update might not relate (fully) to Xbox, hence drawing attention to any update information that might or might not relate to both PC and/or Xbox. It would be good if it could be clarified going forward in any published updates that it applies to both systems (or not).