Why is Microsoft Flight Simulator scenery not loading, and how do I fix it?
Fix Microsoft Flight Simulator scenery not loading in MSFS 2020 or 2024: restore online data, clear the cache, check packages and isolate add-ons.
Microsoft Flight Simulator scenery usually does not load because online world data cannot stream, the rolling cache is corrupt, an official package is missing, or third-party scenery conflicts with it. Confirm the problem’s scope, restore data services, delete the cache, then test the same place with all add-ons disabled.
What kind of scenery loading problem do you have?
The symptom reveals whether to investigate streaming, installed content or an add-on first.
| Symptom | Likely cause | Check first |
|---|---|---|
| Generic buildings or flat city areas | Photogrammetry is disabled, unavailable or not provided there | Online world-data settings and local coverage |
| Blurry ground textures that never sharpen | Slow streaming, a damaged cache or restricted bandwidth | Connection, data cap and rolling cache |
| One airport is missing or replaced | Package installation, entitlement, dependency or duplicate scenery | Content library and add-ons for that ICAO |
| Aerial tiles are blank after using a map tool | Failed imagery source, cache or leftover network redirection | Disable the tool and restore its network changes |
| Download or package installation will not complete | Connectivity, storage or content-library failure | Free space, account state and download queue |
| The loading bar never reaches the cockpit | Broken package, aircraft or incompatible add-on | Start with no third-party content |
Broad reports such as nejde to (“it doesn't work”) or por qué no me carga (“why won't it load?”) need one distinction: does Microsoft Flight Simulator reach the cockpit but show incomplete scenery, or does the flight itself never load? Those are different faults.
How do I fix scenery not loading in MSFS?
Work through these checks in order and retest the same location after each change.
- Establish whether the fault is local or global. Load a default aircraft at a standard airport away from the affected area. If scenery fails everywhere, suspect streaming or core content. If only one airport or city is affected, investigate its coverage and packages.
- Enable every required online-data control. In the simulator’s online or data settings, confirm that online functionality and world graphics data are enabled. Photogrammetry is a separate option in builds that expose it. Check that a simulator data cap has not been reached and that the owning Microsoft or platform account remains signed in.
- Test the underlying connection. Fully close the simulator, restart the network connection and try again. Open a normal website on the same device; if the website won't load either, fix the connection or captive-portal sign-in before changing MSFS. Temporarily test without a VPN, proxy or security filter, but restore normal protection afterwards.
- Delete the rolling cache. Use the simulator’s data or bandwidth settings to delete the existing cache rather than only turning it off. Restart MSFS, then leave the cache disabled for one test or create a new one. Remove any manual cache covering the problem area as well. Our step-by-step rolling cache reset explains what to remove without disturbing installed scenery.
- Inspect the content library. Look for paused, disabled, incomplete or missing world, city and airport packages. Confirm there is enough free storage and that the correct account owns the content. If a package repeatedly stops or scenery cannot stream, use our scenery download and streaming checks.
- Run without third-party content. On PC, close MSFS and rename the active
Communityfolder so the simulator starts with an empty one. Safe Mode can provide a similar test when it is offered after an abnormal shutdown. On consoles, disable or uninstall optional add-ons through the simulator’s content library. - Undo map-enhancement changes. Some imagery tools alter the system proxy, DNS configuration or hosts file. Simply deleting the tool may leave those changes behind. Use its restore function or reset the affected network configuration, then clear the simulator cache.
- Repair before reinstalling. Use the platform’s file verification or repair function for damaged core files. A complete reinstall is a last resort: it will not fix a data cap, blocked service, account problem or external Community folder.
Do not change five settings and remove every package at once. A single change followed by the same repeatable test tells you which fix actually worked.
Online data is active, but scenery is still not working
An active online toggle does not prove that world graphics data is reaching the simulator.
- Check the separate controls. Online functionality, world graphics, photogrammetry and multiplayer are not interchangeable. Multiplayer can work while imagery streaming fails.
- Toggle and restart properly. Turn world-data streaming off, apply the setting and close MSFS completely. Reopen it, enable the setting and test again; returning only to the main menu may preserve the failed session.
- Inspect the data limit. A configured bandwidth or monthly data cap can stop high-detail scenery while the rest of the simulator remains online.
- Check account state. Sign out only after closing the simulator, then sign back into the same account used by the simulator and any purchased content.
- Consider a service-side interruption. If unrelated online features fail on multiple devices while ordinary internet access works, repeated reinstalls will not help. Retry after the service is available.
Why does MSFS load generic scenery instead of photogrammetry?
Generic autogen means the base world has loaded, but photogrammetry has not.
Photogrammetry covers selected cities rather than the whole planet. It requires its own setting, working world-data streaming and enough bandwidth to fetch the higher-detail geometry. Terrain Level of Detail changes draw distance; raising it cannot create photogrammetry where no coverage exists.
If a supported area remains generic, disable photogrammetry, apply the change, restart MSFS and enable it again. Delete the rolling cache if that fails. Briefly simplified or distorted buildings can be normal while data arrives, but scenery that never improves points to streaming, cache or coverage rather than graphics-card failure.
Why is my downloaded airport scenery not showing?
A downloaded airport usually fails to appear because it is in the wrong package folder, has an extra nested directory, lacks a dependency or conflicts with another version of the same airport.
- Confirm that you used the active Community folder. Its location differs between MSFS versions, store installations and custom package paths.
- For a conventional PC package,
manifest.jsonandlayout.jsonnormally sit directly inside the package folder. If they are inside a second wrapper directory, install the inner folder. - Check whether the scenery was made for MSFS 2020, MSFS 2024 or both. Compatibility should not be assumed merely because the files are accepted.
- Install any required object libraries, world updates or other dependencies listed with the package.
- Remove duplicate scenery for the same ICAO, including an older freeware airport and a separate handcrafted version. Removing the duplicate is safer than guessing at package priority.
- For purchased content, confirm that ownership, installation and activation are all associated with the account running the simulator.
A short identifier such as MRLV may refer to an airport code or package label. Search for it in both the World Map and content library rather than assuming global scenery has failed. Our checks for one missing airport cover map filters, entitlements, dependencies and duplicate packages.
I don't have this setting or folder — is MSFS 2024 (“MS 24”) different?
Yes: the diagnostic order is the same, but menu labels, package access and reliance on streamed content differ between simulator versions and platforms.
| Platform | What to use | What not to expect |
|---|---|---|
| MSFS 2020 or 2024 on PC | Online-data settings, content library and the active Community folder | The same folder path for every installation |
| MSFS on Xbox | Simulator content library and console storage controls | Direct access to a PC-style Community folder |
| MSFS 2024 on PS5 or PS5 Pro | Simulator content library and console storage controls | Direct package-folder access |
Microsoft Flight Simulator 2024 streams more content than MSFS 2020, so an internet or account failure can affect aircraft and airport assets as well as aerial imagery. A package not appearing as a conventional local installation is not automatically missing.
Microsoft Flight Simulator 2020 was never released on PlayStation. If a guide mentions a setting your build does not expose, do not create guessed folders or delete official package directories; skip that control and continue with the connection, content-library and clean-add-on tests available on your platform.
I've done all that and it is still not working
If nothing worked, stop repeating cache and network changes and run one clean control test that separates a local scenery fault from a simulator-wide failure.
- Close MSFS completely. Empty or rename the active Community folder on PC, or disable optional add-ons on console.
- Use stock content. Select a default aircraft and a standard airport outside the affected region. Avoid the aircraft, airport and saved flight involved in the original failure.
- Test online and without streamed detail. First test with the required online services enabled. If your platform has offline scenery packages installed, test those as a comparison.
- Interpret the result. Use the outcome below rather than applying the same fixes again.
| Clean-test result | What it means | Next action |
|---|---|---|
| Stock scenery works until add-ons return | A third-party conflict is confirmed | Restore packages in halves until the faulty group is isolated |
| Other locations work, but the original airport does not | The fault is local to coverage or an airport package | Check that airport’s installation, dependencies and duplicates |
| Default flights work, but streamed detail fails everywhere | Network, account, service or data-cap problem | Recheck authentication and streaming controls; do not reinstall yet |
| Offline or installed base scenery is also absent | Official content may be incomplete or damaged | Repair files and reinstall the affected official package |
| The flight never reaches the cockpit | This is a loading failure, not merely missing scenery | Use the stuck-flight loading checklist |
If you did all of those tests at once, repeat the clean test with one controlled change at a time. If even the main menu does not open, move away from scenery troubleshooting: the simulator has a launch or installation fault instead.