Why are FSX add-on cockpit screens or instruments blank?
Blank cockpit screens in FSX add-on aircraft usually mean the avionics are unpowered, the required gauge files are missing or blocked, or the aircraft was built for a different simulator version. Start with electrical power and brightness, then reinstall the panel and gauges exactly as supplied, approve trusted modules, and check the add-on’s dependencies.
Is the panel unpowered or is a gauge missing?
If every display is dark, check aircraft power first; if individual instrument apertures are empty or black, suspect missing gauge files.
| Symptom | Most likely cause | First check |
|---|---|---|
| All glass displays are dark | Battery, avionics, generator or brightness controls | Start the aircraft properly and turn up each display’s dimmer |
| Only some instruments are black or absent | Missing, blocked or incorrectly installed gauge package | Inspect the aircraft’s panel.cfg and gauge files |
| Default aircraft also have blank instruments | Damaged shared gauges or an FSX-wide graphics problem | Restore default files and test without DirectX 10 Preview |
| The 2D panel works but the virtual cockpit does not | Virtual-cockpit gauge entries, model compatibility or DX10 rendering | Inspect the [Vcockpit] sections and disable DX10 Preview |
On a complex airliner, battery power alone may not be enough. It may require external or APU power, generators, avionics switches and IRS or ADIRS alignment. Ctrl+E is a useful quick test on simpler aircraft, but it does not initialise every custom aircraft system.
How do I fix blank cockpit instruments in FSX?
Most blank FSX panels can be fixed without reinstalling the simulator by checking the aircraft in a controlled order.
- Check power and display brightness. Turn on the battery, avionics master and generators or alternators, then adjust the individual PFD, ND or panel brightness controls. Load the aircraft in daylight so an unlit panel is not mistaken for a missing gauge.
- Confirm that the download is a complete FSX aircraft. A repaint or livery package normally depends on a separate base aircraft and does not include its model, panel or gauges. An FS2004 or Prepar3D aircraft may appear in the FSX selection menu while its compiled gauges remain incompatible. For Steam installations, use our FSX and Steam Edition compatibility checks before replacing files.
- Reinstall the aircraft from a clean extraction. Close FSX, extract the archive to a temporary folder and follow its readme. Copy the complete aircraft folder, including
panel, and place any supplied.gau,.dllor.cabfiles exactly where the instructions specify. Our explanation of the correct FSX aircraft folder structure helps identify nested folders and files copied into the wrong simulator installation. - Verify the actual FSX root folder. It is the folder containing
fsx.exe,GaugesandSimObjects. Steam libraries and custom installations may not use the path assumed by an old installer. A common mistake is installing gauges into a boxed-FSX folder while running FSX: Steam Edition elsewhere. - Keep XML gauge cabinets intact. A gauge supplied as a
.cabfile will often be loaded directly from the aircraft’spanelfolder or the mainGaugesfolder. Do not unpack it unless the aircraft instructions explicitly require that. - Allow the required trusted module. FSX may ask whether to run a gauge or DLL the first time the aircraft loads. Approve it only when it belongs to the add-on you intentionally installed. If it was previously rejected, close FSX, back up the FSX configuration file and remove only that module’s entry from the
[Trusted]section so FSX can ask again. - Install the stated dependencies. Some aircraft require FSX service packs or Acceleration features, a legacy SimConnect component, a runtime library, custom fonts or another supplied module. Install only the prerequisites named in the aircraft documentation; copying unrelated gauge DLLs into FSX can create version conflicts.
- Test with DirectX 10 Preview disabled. Older panels and virtual-cockpit materials can display incorrectly under FSX’s optional DX10 Preview mode. Untick that option in the graphics settings, restart FSX and load a new flight.
If downloaded files are being blocked by Windows, close FSX, open the original archive’s Properties, use Unblock if that option is present, and extract it again. Also check that an installer was permitted to write into the FSX directory; otherwise it may report success without installing the gauges.
How can I identify the missing FSX gauge?
The panel.cfg entry for an empty instrument usually identifies the gauge package FSX is trying to load.
Open a backup copy of the file and examine sections such as [Window00] for 2D panels and [Vcockpit01] for virtual-cockpit displays. A line resembling gauge00=Package!Display,... refers to a gauge package named before the exclamation mark. Look for the corresponding package in the aircraft’s panel folder and the main FSX Gauges folder.
An alias=aircraft_folder\panel entry means the aircraft borrows another aircraft’s panel. If that target aircraft has been removed, renamed or installed under a different folder name, the borrowed instruments will not load.
Do not replace panel.cfg or collect random gauges from unrelated aircraft. Use a repair made for the exact base package and variant. For example, the dedicated repair for the SAA A340-313 panel supplies files for that specific aircraft; it is not a universal Airbus panel fix.
What if default FSX aircraft have blank gauges too?
If default aircraft are affected, the fault is probably in FSX’s shared gauges, configuration or graphics settings rather than the add-on aircraft.
Test a stock aircraft in a new daytime flight. If its instruments are also missing, disable DX10 Preview and undo any recent changes to the main Gauges folder. When an add-on installer has overwritten or deleted default files, our FSX Gauge Recover utility is designed to restore missing default gauges and effects; back up the affected folders before using any repair tool.
A full FSX repair or reinstall should be the last step, not the first. If stock aircraft work and only one add-on remains blank after a clean installation, that aircraft is missing a dependency, references the wrong panel, or is not compatible with the FSX edition and configuration being used.
Why does only the 2D or virtual cockpit panel fail?
A difference between the 2D panel and virtual cockpit narrows the fault to separate sections of panel.cfg or to the aircraft’s virtual-cockpit model.
- 2D works, virtual cockpit blank: check the
[Vcockpit]gauge entries, required model files and DX10 Preview compatibility. - Virtual cockpit works, 2D panel blank: the add-on may not include a 2D panel, or its
[Window]definitions and panel-window assignments may be missing. - Both are blank: concentrate on electrical state, shared gauge packages, blocked modules and aircraft dependencies.