Xbox/PC screens go black then CTD

The fun soon goes away, for me haha. I’ve had maybe 10 CTD’s reported from the start of this beta. I will continue doing so over the weekend, but then i’m done. I did my part.

Besides that, i notice severe lag en stutters while planning a flight in World Map. And why can’t Asobo employees test it themselves, you can’t tell me they have no default Xboxes availabale at their office.


Can somebody give me a run through on how to download/ sign up to the beta testing?

Xbox Series X|S Testing Opportunity - Community / News and Announcements - Microsoft Flight Simulator Forums


When do you people think a fix/ update will be released for this?

I uninstalled all the marketplaces present on my Simulator. I tried a clean flight until the end without any sign of bug with this Beta mode. But as I approached the airport, the screen went black. Regrets are running through my head.

This Beta does not fix any problems and is not different from the public fs2020 Level. It does add some debugging hooks to the code so that error data can be analysed by MS/Asobo.


@SeedyL3205 can I test it offline to or do y’all just need online ?

I just wanted to let y’all know I j completely 3/ hours flight with beta testing


I have this bug a lot on series s. I’ve found that if you turn external power on after engines have started it sometimes brings the flight display screens back on. Most of the time i get this bug is on startup, the screens switch on then switch off when the checklist moves by the battery options.

Hey guys, Series S player here who faces this issues frequently as well. I’ve made a few observations but be warned - this is not how you intended to play the game.

  1. Turn off real time weather, real time air traffic, real world Bing graphics. I think this connection to real time data eats up RAM. My game became more stable once i followed these but you’re missing out on the beautiful landscape.

  2. Quickly swapping cameras in handcrafted airports/locations/memory intensive areas probably overwhelms RAM and black screen avionics. I flew from London to Newark using a BA livery on the Dreamliner. All fine till i was about to park at the gate and quickly changing to exterior view messed up my screens. Luckily - my flight was done :slight_smile:

  3. Is it possible that the marketplace liveries have to much graphical details? I’ve had more avionics issues on custom liveries than with Asobo’s.

  4. The avionics issues in flight start at around 1200 Nautical miles - probably by then enough data has been downloaded to overload RAM?

  5. When the ready to fly option is shown, clicking on it too quickly with 7/10 lead to black screens. Even though the option is given, wait for 10 second for the airport to load as well.

  6. Event though real time data takes just 200 mb for a 6 hour flight, it still causes black screens.

These are my observations - hope it helps anyone!

R u on Xbox beta testing

Kalt screens when out and restart my sim KAtl CTD every time I loaded in hopefully they got it

I’m new to the forum and just saw this today but I will participate from tomorrow.

Ran a flight today from Abu Dhabi to Singapore. No issues for 7 hours but I forgot to put real time weather and air traffic. However this time I put real world streaming so that’s good;

This flight was in the beta. I hope the developers got some information out of it.

Only issue was black avionics once I was at the arrival gate. I switched to external camera to enjoy the airport view . Attached in the picture. This happened as the jetway was being connected.

I used a custom livery for my Dreamliner - the airport had custom liveries for a320s.

Will keep updating any new findings here if appropriate and useful.

1 Like

Now screens won’t turn on like KAtl and other airports

My recommendation for everyone is to uninstall handcrafted ATL and DFW, those airports are very bad optimized for xbox, all the time causing CTD/Black screens

1 Like

Regarding the ongoing Xbox Stability Testing - we’ve received a lot of data on out of memory crashes on Xbox and are now analyzing the information and investigating a few different cases. The information we’ve received so far has been hugely beneficial to the team. Thank you very much for those who are participating!


Good news very good ! I won’t stop testing until you guys say it’s done . Thanks for the updates!


Quite welcome that MS/Asobo aknowledged our efforts and thanked us. What I’m missing in the short message is a perspective: is it still beneficial to continue and if yes what is the plan and specifically for how long should we continue and if yes, is there an end date? The communication as good as it is on technical details, seems a bit lacking the social component and understanding of what non-technical info and care we need. Above all we’re spending dedicated, personal and unpayed work for a commercial company.