Why does FSX freeze at 80% adjusting scenery objects?

FSX usually freezes at 80% on “Adjusting scenery objects” because it is reading a damaged, incompatible or incorrectly registered scenery package around the selected airport. A stale scenery index, missing scenery-library path or memory exhaustion can look identical. Disable recent scenery first, then rebuild the scenery indexes and isolate the offending area.

Is FSX really frozen at 80%?

A fixed progress display is not always a genuine freeze, particularly on the first load after installing or rearranging scenery. FSX performs much of this work on its main thread, so Windows may report “Not responding” while storage activity continues.

Allow one uninterrupted load if there is continuing disk activity. Treat it as a fault when activity stops, the same flight repeatedly sticks at 80%, or FSX never completes after previously loading that area normally.

Test a stock aircraft at a simple default airport in another region. If that loads, the problem is probably an airport, landclass, object-placement or library BGL covering the original location. If every location freezes, suspect a global scenery layer, scenery configuration, traffic package or damaged core file.

How do I find the scenery causing the 80% freeze?

The fastest method is to disable scenery by layer, rebuild FSX’s index, and then re-enable entries in batches.

1. Back up the active configuration. Preserve scenery.cfg before changing library entries; our guide to backing up FSX settings and add-ons explains which files matter. The active configuration is normally under %PROGRAMDATA%\Microsoft\ in the applicable FSX or FSX-SE data folder, not the template beside the simulator executable.
2. Disable the newest add-on scenery. Open Settings, then Scenery Library, and clear the enabled box for anything installed or updated before the freeze started. Do not remove default entries such as the base and numbered stock scenery areas.
3. Check every suspect path. A scenery entry must point to an existing, accessible folder. Look for add-ons on disconnected drives, unavailable network locations, renamed directories or an installer that registered the boxed FSX path instead of FSX: Steam Edition. Our FSX scenery folder and activation instructions show the expected structure.
4. Rebuild the scenery indexes. Close FSX completely. Under the applicable FSX data folder inside %PROGRAMDATA%\Microsoft\, rename SceneryIndexes to SceneryIndexes.old. Start FSX and let it recreate the indexes; the first load may take longer. If the folder is not recreated, check that your Windows account can write to that data location.
5. Use a half-and-half test. If several add-ons could be responsible, enable half of them and load the same airport. Keep narrowing the failing group until one scenery layer remains. This is much quicker than testing a large library one entry at a time.
6. Isolate individual third-party BGL files. Inside the identified package, move half its BGL files to a temporary folder outside FSX, or temporarily change their extensions from .bgl to .off. Repeat the test until the damaged airport, exclusion, object-placement or library file is identified. Never perform this experiment on default FSX scenery folders.
7. Reinstall or remove the culprit. Use a clean copy intended for FSX, confirm that its installer targeted the correct edition, and avoid combining different releases of the same airport. A scenery file compiled only for another simulator may not be compatible even when its folder structure looks correct.

Missing textures normally produce absent, untextured or black objects rather than a permanent 80% freeze. Prioritise BGL files, inaccessible paths and the scenery index before reinstalling every texture folder.

Can scenery-library order cause this freeze?

Scenery order usually causes visual conflicts rather than a hard freeze, but overlapping versions of the same airport can expose a defective BGL. Disable one version first instead of repeatedly moving both layers up and down.

Once FSX loads reliably, arrange airport, regional and global layers according to our explanation of FSX scenery-library priority. Correct ordering prevents duplicate runways, flattened terrain, missing exclusions and objects from the wrong package, but it cannot repair a corrupt file.

What if FSX freezes with default scenery too?

If a stock aircraft at several default airports still freezes after every optional scenery layer is disabled, the fault is probably global rather than tied to one airport.

• Reset the FSX configuration: back up and rename fsx.cfg, then allow FSX to create a clean copy. This resets display, control and tuning changes, so do not delete the original.
• Remove global variables: test with a stock aircraft, simple weather and AI traffic turned down. Third-party traffic BGLs and global object libraries are processed across many locations.
• Repair the simulator files: use the installation client’s verification function for FSX: Steam Edition or the repair option from the original media for boxed FSX. Back up any modified default files because a repair may replace them.
• Check memory pressure: FSX is a 32-bit application with constrained address space. If only dense airports fail, reduce Scenery complexity, Autogen density, AI traffic and texture-heavy add-ons. A repeatable freeze at one modest airport still points more strongly to a bad scenery package than to memory.

The “Adjusting scenery objects” caption identifies the loading phase, not the exact file that failed. A one-region freeze almost always calls for scenery isolation; an all-airports freeze calls for a clean configuration, global add-on check and core-file repair.