Learn how to install gauges in FSX and Steam Edition, find the correct Gauges folder, keep CAB files intact, edit panel.cfg and fix blank instruments.
To install gauges in FSX or FSX: Steam Edition, close the simulator, extract the download, and copy the supplied .gau, .dll, intact .cab, or complete XML gauge folder to FSX’s Gauges folder. Then install or merge its panel.cfg entries, backing up existing files first. Use the aircraft panel folder instead when its readme requires it.
Where is the FSX Gauges folder?
The correct Gauges folder is inside the same FSX installation directory as fsx.exe.
| FSX edition | Typical Gauges folder |
|---|---|
| Boxed FSX on 64-bit Windows | C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Gauges |
| FSX: Steam Edition | C:\Program Files (x86)\Steam\steamapps\common\FSX\Gauges |
| Custom installation or Steam library | The Gauges folder beside fsx.exe |
These are defaults, not guaranteed locations. A 32-bit Windows installation may use Program Files without the (x86) suffix, while a custom Steam library can be on another drive. Confirm that the chosen root also contains folders such as SimObjects and Scenery.
If the download also contains an aircraft, our guide to placing complete FSX aircraft and their support files explains the relevant boxed and Steam Edition folder structure.
Install an FSX gauge step by step
The safest method is to preserve the package’s folder structure and treat its instructions as authoritative.
- Close FSX. The simulator may have gauge files loaded, preventing them from being replaced cleanly.
- Read the supplied instructions. Check which FSX edition and aircraft the gauge supports, and note whether it belongs in the main
Gaugesfolder or an aircraft-specific panel folder. - Back up existing files. Save copies of any same-named gauge files and the aircraft’s current
panel.cfg. Do not overwrite an existing folder merely because Windows offers to merge it. - Extract the outer download archive. Extract the ZIP, RAR or other download container to a temporary folder. A gauge supplied as a
.cabfile is different: leave that CAB packed unless its documentation specifically says otherwise. - Copy each gauge in its supplied form.
- Legacy compiled gauges normally use
.gau. - Other compiled gauges may use
.dll. - XML gauges are commonly supplied as an intact
.cabor a folder containing XML files, images and other resources. - Copy the entire named folder when one is supplied; do not flatten its contents into
Gauges.
- Legacy compiled gauges normally use
- Install the panel files. Copy or merge the supplied
panel.cfgentries into the aircraft’s active panel folder, normally belowSimObjects\Airplanes\<aircraft>\panel. Rotorcraft and other object types use their correspondingSimObjectscategory. - Start FSX and load the intended aircraft. A compiled gauge may trigger a security prompt on first use. Allow it only when you trust the package and its source, then check every relevant 2D panel and virtual-cockpit view.
For a practical example of both gauge copying and panel setup, the worked glass-cockpit mini-panel package shows how additional gauge folders fit into the main FSX directory.
Does copying a gauge make it appear in the cockpit?
No—copying the gauge only makes it available to FSX; a panel must also reference it.
Gauge entries sit inside a window or virtual-cockpit section of panel.cfg. A typical XML entry follows the form gauge00=PackageName!GaugeName, x, y, width, height. The package and gauge names must match, each gaugeNN number must be unique within that section, and the position and dimensions must suit that particular panel.
Merge supplied lines rather than replacing the whole configuration unless the new panel.cfg was made for that exact aircraft and panel variant. In aircraft.cfg, an entry such as panel=wide selects panel.wide, so editing the ordinary panel folder would have no effect on that variation.
Can I install a gauge for only one aircraft?
Yes; a gauge in the main Gauges folder appears only in aircraft whose panel configuration references it.
Some packages deliberately keep an XML gauge, CAB file or supporting resources inside the aircraft’s panel folder. Preserve that local arrangement when the instructions require it. Do not relocate files simply to make every package use the same structure.
Adding a separate instrument window also requires suitable Window and Window Titles entries. Our tutorial on setting up an outside-gauge panel or multi-monitor view covers that specialised panel arrangement.
Why is my FSX gauge missing or blank?
A missing or black FSX gauge usually means the panel is referencing the wrong location, the package structure was changed, or the gauge is incompatible.
- Nothing appears: confirm that you edited the aircraft’s active
panel.cfg, used the intended section, and did not duplicate agaugeNNnumber. - FSX cannot find the gauge: remove accidental extra nesting such as
Gauges\DownloadedPackage\Gauges\GaugeName. The installed path should match the structure shown in the package. - An XML gauge is blank: restore its intact CAB or complete folder. XML files often depend on bundled bitmaps, sounds, fonts or other resources.
- A compiled gauge fails to load: verify that it was built for FSX or explicitly described as compatible. FSX and FSX: Steam Edition are 32-bit applications, so 64-bit gauge DLLs and gauges made solely for newer simulators will not load. Older FS2004 gauges work only when their author confirms FSX compatibility.
- The gauge works in 2D but not in the virtual cockpit: check the relevant
VCockpitsection. The aircraft model must also contain a suitable virtual-cockpit gauge surface; editingpanel.cfgcannot create new cockpit geometry. - The instrument is black under DirectX 10 mode: temporarily disable Preview DirectX 10 to test an older gauge. If that fixes it, the gauge or panel artwork is not compatible with that rendering mode.
- FSX crashes after installation: restore the original
panel.cfg, remove the newly added gauge, and test again. Reintroduce the panel line and gauge files separately to identify whether the failure is configuration-related or a compiled-gauge compatibility problem.