Blank Map Screen after starting MSFS

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:On start up via X Box App the X Box screen logo is displayed but then blank until fully loaded. On selecting free flight and airport, the airport is shown but the World view is absent. On starting flight screen stays blank even after entering aircraft.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)? So far 3 out of four starts fail

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. dtailed above normal start procedure using X Box App

  2. All Add on are eliminated from MSFS only MSFS aircraft used

  3. Tried Repair via MS App list and checked for updates

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using:

[PC Only] Are you using Developer Mode or have you made any changes to it?No Changes

[PC, MSFS 2020 Only] Are you using DX11 or DX12? Was set on DX12 in MSFS2024

[PC Only] What GPU (Graphics Card) do you use?Nvidia 4070 Super

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.Pointless just blank screen after starting

If you start the sim using the regular FS2024 icon do you also experience the issue ?
Are you getting the same issue than reported here ?: Black world map after SU3

Yes I have tried starting via Store, X Box and Icon all have the same result. Occassionally if I close down the computer and restart it will open normally.Thnaks for the links, there are a number of options to try. I have not added any new software or hardware

Also just noticed new Graphics driver. I’ll try clean instal.

Still no success. Used ChatGPT to suggest options which included deleting various config files. Worked initially but today failed again via X Box. This is I think and Asobo/MS issue they need to address.

The difficulty here is to be able to replicate. Until not being able to, it is not possible to understand the root cause and fix it. Hopefully some users can provide their feedback (maybe hardware related ?) and from their identify a common pattern/root cause.

Currently working after trying a number of options. if I had to pin point the most likely factor for me it is the fact that I turned off V Sync

So if you turn on V Sync it works again ?

As I mentioned I tried many things including App repair and App Reset via System/App Advanced and then noticed someone mention changing V Sync. I just tried it off in Nvidia Control Panel MSFS 2024 program but on in the game and so far OK not 100% sure what did it

spoke too soon it is not solved today black screen again, this is getting tiresome

I am seeing this in SU5 Beta:

I see this is still an ikssue. I was not and have never been on Beta trials. Mine has stopped showing the black screen but I cannot be specific as to what caused it or why it is (currently) no longer a problem.Apart from the usual re installing driver etc, if I had to gues it is something to do with V-Sync. I have it off in all conditions Nvidia App and MSFS. I have no intention of testing this theory :slight_smile:

Hi there,

I am having the same issue for the last couple of weeks.
At times it appears fixed and two days later the exact same problem would occur.

Any one has a definite solution as to what could be causing it?
The game itself works but the rendering is a black screen (even during loading, the usual loading screen past XBOX Studios is black with the loading status at the bottom)

Answering myself but it seems that adding -FastLaunch as a start mode works (if it can help devs identifying the issue)