Why are FS2004 add-on gauges missing or not working?

Missing or dead gauges in an FS2004 add-on aircraft usually mean the package's .gau or .cab files are in the wrong folder, Panel.cfg references unavailable gauges, or the panel needs another aircraft or product. If instruments are visible but dark, check electrical power and the add-on's startup procedure first.

Identify what is actually failing

The pattern of failure usually reveals whether this is an installation, configuration or aircraft-state problem.

Where should FS2004 gauge files be installed?

In FS2004, panel definitions belong inside the aircraft's panel folder, while shared gauges normally belong in the simulator's main Gauges folder.

• FS9\Aircraft\AircraftName\panel\Panel.cfg defines the windows and instruments.
• FS9\Gauges\GaugeName.gau is the usual location for a compiled FS2004 gauge.
• FS9\Gauges\GaugePack.cab is the usual location for a shared XML gauge package.
• A panel-specific CAB may remain beside Panel.cfg when the package was deliberately supplied that way.

The FS9 root is the folder containing fs9.exe. A mistake we see constantly is an extra directory level such as Gauges\Gauges or AircraftName\AircraftName\panel. Our guide to the correct FS2004 add-on folders explains how to recognise and fix that nesting.

Do not unpack a gauge CAB merely because it looks like an archive. FS2004 can read CAB gauge packages directly, and extracting one into another subfolder often prevents Panel.cfg from finding it. For a complete explanation of panel artwork, configuration files and panel-local gauges, use our FS2004 replacement-panel installation instructions.

How do I fix missing gauges in an FS2004 aircraft?

Work through the aircraft's power state, package requirements and file references in that order; replacing files first can conceal the real fault.

1. Test the aircraft powered up. Unpause FS2004 and switch on the battery, avionics master and generators or alternators. As a diagnostic, load a default aircraft with its engine and avionics running, then switch to the add-on. If the instruments wake up, follow the add-on's proper startup procedure rather than reinstalling gauges.
2. Check the package requirements. A repaint, panel modification or expansion may require a separate base aircraft. It may also rely on default FS2004 gauges or files from another legitimately installed product; those dependencies are not necessarily included.
3. Back up the existing files. Close FS2004, then copy the aircraft's panel folder and any gauge files you intend to replace. Do not let an old installer overwrite shared gauges without a recoverable backup.
4. Find the real FS2004 installation. Confirm that you are copying into the folder containing the fs9.exe used by your shortcut. Multiple installations and Windows file virtualisation can leave files in another FS9 directory or in VirtualStore even though an installer reported success.
5. Merge folders rather than nesting them. If the download contains a folder named Gauges, copy its contents into the existing main Gauges folder. Apply the same rule to the aircraft's panel contents.
6. Check the selected panel variant. In Aircraft.cfg, the panel= entry under the relevant [fltsim.x] section chooses the panel folder. A blank value uses panel; a value such as wide selects panel.wide. If Panel.cfg contains an alias, the referenced aircraft and panel folder must exist.
7. Inspect the gauge references. Entries under sections such as [Window00] and [VCockpit01] begin with names such as gauge00=PackName!InstrumentName. The text before the exclamation mark identifies the gauge package. If that package is absent, install the exact dependency rather than renaming an unrelated .gau or .cab file.
8. Retest one change at a time. Restart FS2004 after changing panel or gauge files. If the same gauge works in another aircraft, concentrate on this aircraft's Panel.cfg, selected panel variant and aliases rather than the global Gauges folder.

Why are the gauges visible but not working?

Gauges with visible bezels or screens are often installed correctly but lack aircraft power or the conditions required to operate.

• All screens are dark: check battery, avionics and generator power. Some complex panels use custom switches rather than only FS2004's standard commands.
• Needles are frozen: make sure the simulation is not paused and that an instrument failure has not been enabled.
• Only navigation displays are dark: verify avionics power and any mode, brightness or display selectors described in the aircraft documentation.
• One aircraft variant fails: compare its panel= entry with a working variant. Repaints often point to the wrong or nonexistent panel folder.
• Several aircraft broke after installing another add-on: a shared gauge may have been overwritten. Restore the backed-up file or reinstall the affected FS2004 package rather than adding a random gauge collection.

Why do 2D gauges work but virtual cockpit gauges do not?

If the 2D instruments work, the gauge files are usually present; the fault is more likely in the virtual-cockpit configuration or model.

Virtual-cockpit gauges are assigned through [VCockpit] sections and displayed on surfaces built into the aircraft model. A panel made for a different model may have working 2D windows but no compatible virtual-cockpit mapping. Copying ordinary [Window] entries into a [VCockpit] section is not a reliable fix—use a panel intended for that exact aircraft model.

What if FS2004 crashes while loading the panel?

A crash when selecting the aircraft or opening a panel window points to an incompatible or damaged gauge, even when the crash report names PANEL.DLL.

Restore the original panel first. If necessary, work on a copy of Panel.cfg and temporarily remove half of its gauge entries, then retest and narrow the group until the offending gauge is identified. Our PANEL.DLL crash diagnosis covers that isolation process and the cases where the panel system is only reporting a fault caused elsewhere.

Can FSX gauges be used in FS2004?

FSX, Prepar3D and later simulator gauges should not be assumed to work in FS2004.

FS2004 is a 32-bit simulator with its own gauge interfaces. Binary gauges compiled for another simulator may fail to load or crash FS9, while XML gauges may use commands that FS2004 does not understand. Some older FS2002 gauges work when their author explicitly states FS2004 compatibility, but the safe choice is always the gauge version supplied for FS2004 or FS9.