FSX crashes when selecting a military aircraft? Isolate faulty models, gauges, textures and DLLs, then repair the add-on without reinstalling FSX.
FSX and FSX: Steam Edition do not crash because an aircraft is military. A crash when selecting one usually means the aircraft has an incompatible model, corrupt texture, faulty panel gauge or missing support DLL. If every aircraft crashes, investigate FSX itself, the active flight, graphics configuration or scenery instead.
What does the timing of the FSX crash tell me?
The point at which FSX closes is the quickest way to narrow the fault, although it is a clue rather than proof.
| When FSX crashes | Likely cause | Best first test |
|---|---|---|
| When merely highlighting one variation in Select Aircraft | Corrupt thumbnail.jpg, malformed variation data or damaged preview-related files | Rename that livery's thumbnail.jpg and compare its [fltsim.x] entry with a working variation |
| After pressing OK, while the flight loads | Aircraft model, textures, panel, gauges, sounds or a support module | Try another variation of the same aircraft, followed by a temporary stock panel |
| Just after the cockpit appears | A gauge or helper DLL beginning execution, or a virtual-cockpit model problem | Check the Windows crash record for a named faulting module |
| With one paint scheme only | Corrupt texture or an incorrect model=, panel=, sound= or texture= suffix | Compare that variation with one that loads correctly |
| Only at a complex airport or with demanding scenery | FSX's 32-bit address-space or graphics-resource limits | Load the aircraft at a simple airport with reduced AI and scenery settings |
| With stock and add-on aircraft alike | A broader saved-flight, configuration, scenery or simulator problem | Work through our broader Free Flight crash checks |
If several military aircraft from the same package fail while the stock Cessna loads, they probably share a missing gauge or DLL. The military category itself does not activate any special FSX code.
Compatibility labels also need scrutiny. Some FS2004 port-overs use legacy models or gauges that are unreliable in FSX, while aircraft built only for another simulator are not interchangeable with FSX aircraft. Boxed FSX may need SP2 or Acceleration when the documentation requires it. FSX: Steam Edition includes Acceleration-era functionality, so do not install boxed-FSX service packs over it.
How do I fix a military aircraft that crashes FSX?
Most crashes caused by a single military aircraft can be fixed without reinstalling or resetting FSX.
- Confirm that the failure is aircraft-specific. Load the stock Cessna 172 from the same Free Flight screen. Then try another variation of the military aircraft. If the stock aircraft works, avoid changing scenery or deleting the main FSX configuration until the suspect package has been isolated.
- Quarantine the complete aircraft folder. Back it up and move it outside
SimObjects. Merely renaming a folder while leaving it underSimObjects\Airplanesmay not prevent FSX from scanning it. If removing the folder stops the crash, use our component-by-component method for isolating faulty FSX add-ons. - Check the package requirements. Confirm that it was made for FSX and whether boxed FSX requires SP2 or Acceleration. A DLL compiled for a 64-bit simulator cannot be substituted into 32-bit FSX, even when Windows itself is 64-bit.
- Reinstall the full package structure. The aircraft's main folder should contain
aircraft.cfgand its model, panel, sound and texture folders. Copy separately supplied gauges, effects and other support files to the matching FSX folders exactly as the documentation directs. Merge folders; never replace the complete FSXGaugesorEffectsfolder with one from an add-on. - Check for an extra nested directory. A common extraction mistake produces a path such as
SimObjects\Airplanes\PackageName\AircraftName\aircraft.cfg. The actual aircraft folder containingaircraft.cfgshould be placed directly where the package instructions expect it. - Compare each aircraft variation. In
aircraft.cfg, a value such asmodel=cleanrefers tomodel.clean, whiletexture=greyrefers totexture.grey. The same rule applies to panel and sound suffixes. An empty value uses the unsuffixed folder. Duplicatetitle=values generally cause warnings or missing menu entries rather than a hard crash, so they should not be the first suspect. - Substitute a known-good panel. Back up the original panel folder, then temporarily use a valid panel alias pointing to a stock FSX aircraft. If the aircraft now loads, the visual model is probably usable and the fault has been narrowed to the original
panel.cfg, gauges or panel-related DLLs. Restore a copy of the original panel and disable suspect third-party gauge lines in small batches to identify the offender. - Inspect the Windows crash record. Reliability Monitor or Event Viewer may name the actual gauge or DLL that failed. A package-specific module name is actionable; generic modules such as
ntdll.dllorKERNELBASE.dlldo not by themselves prove that Windows is damaged. Our guide to finding the faulting FSX module explains where to look. - Retest in a light flying situation. Start with a stock aircraft at a simple airport, use clear weather and reduce AI traffic, then switch to the military aircraft. If it works there but fails at a detailed airport, memory or graphics-resource pressure is more likely than a missing file.
Where should GaugeSound.dll and FSX gauges be installed?
Install gauges and helper DLLs in the location specified by the aircraft documentation; for many older FSX packages, GaugeSound.dll belongs in the main folder beside fsx.exe, not inside the aircraft folder or a Windows system directory.
- Aircraft-specific files belong under
SimObjects\Airplanes\AircraftName. - Shared gauge containers commonly belong in the simulator's
Gaugesfolder, although some packages deliberately keep them in the aircraft's panel folder. - CAB gauge archives should normally remain intact unless the supplied instructions explicitly require extraction.
- Global effects and sounds belong in the matching simulator folders when the package supplies them separately.
For the full folder layout and panel.cfg checks, use our folder-by-folder FSX gauge installation instructions.
With Steam Edition, locate the installed files through Steam and confirm which folder actually contains fsx.exe. Older automatic installers often write to an unused boxed-FSX directory instead of the live Steam installation. If Windows offers an Unblock option on the downloaded archive, apply it before extraction so its DLLs are not silently blocked.
Use the DLL supplied or specified by the aircraft package. Do not download an unrelated file merely because it has the same name, and do not overwrite an existing global DLL without backing it up. Approve an FSX module security prompt only when the filename and source are recognised.
Should I reinstall FSX if one military aircraft crashes?
No; reinstalling FSX is unnecessary when only one military aircraft or package causes the crash.
A simulator reinstall cannot supply gauges or support files omitted from that add-on. Move the faulty aircraft outside SimObjects, repair its installation and retest before touching the base simulator.
If the aircraft was saved in the default flight and FSX now crashes before reaching the menu, move its folder out temporarily. Start FSX, select a stock aircraft and save a replacement default flight before continuing the diagnosis.
Consider a boxed-FSX repair or Steam file verification only after stock aircraft also fail with the suspect add-on removed. Back up intentional modifications first: verification can restore altered default files, but it usually leaves unrelated third-party files behind and will not clean up a badly installed add-on automatically.