Fix missing or blank add-on aircraft instruments in Prepar3D by checking power, panel.cfg, gauge files, aliases, trust settings and 64-bit compatibility.
Add-on aircraft instruments are missing or blank in Prepar3D when the simulator cannot load the gauges named by the panel, or when loaded displays have no electrical power. Common causes are missing support files, a broken panel alias, blocked modules, incomplete installation, bad saved states, and 32-bit gauges used in 64-bit Prepar3D.
What does the cockpit symptom tell you?
The visible symptom usually separates an electrical or aircraft-state problem from a gauge-loading failure.
| Symptom | Likely cause | First check |
|---|---|---|
| Bezels are visible, but screens are black | No electrical power, avionics off, brightness down or a bad saved state | Battery, external power or generators, avionics and display brightness |
| There are empty holes where instruments should be | Missing gauge package, bad panel.cfg entry or failed panel alias | Gauge files, panel configuration and content error log |
| The 2D pop-up works, but the virtual cockpit is blank | Broken [VCockpitXX] entries or incompatible virtual-cockpit mapping | Compare the 2D and virtual-cockpit sections in panel.cfg |
| Only one repaint has missing instruments | Wrong panel= selection or absent base aircraft | Compare its aircraft.cfg entry with a working livery |
| Digits or labels are absent, but the instrument body remains | Missing fonts or panel textures | Reinstall the package's fonts and textures |
| An FSX aircraft fails in Prepar3D v4 or later | Legacy 32-bit compiled gauges | Find a native 64-bit update or compatible replacement panel |
If the exterior model is invisible, skeletal or missing parts as well, this is not just a panel fault. Use our separate diagnosis for an invisible or incomplete aircraft model.
How do you fix missing Prepar3D gauges?
Check the aircraft in this order so that you identify the cause before editing or replacing files.
- Establish the scope. Load a stock Prepar3D aircraft and check its instruments. If only one add-on or one livery fails, concentrate on that package; if stock aircraft also fail, the simulator's content or user configuration may need repairing.
- Start from a clean scenario. Load a simple default scenario and aircraft, then select the add-on. A saved scenario can retain a dead battery, failed avionics, an incompatible panel state or another condition that makes a working cockpit appear broken.
- Restore power and brightness. Switch on the battery, external power, APU or generators as appropriate, followed by the avionics. Check display brightness knobs as well. Complex aircraft may also require their documented systems-start procedure before the displays initialise.
- Confirm the exact Prepar3D compatibility. Prepar3D v4 and later are 64-bit and cannot load old 32-bit compiled
.gauor.dllgauges. An aircraft appearing in the selection menu does not prove that its panel code is compatible. When choosing another package, check the stated simulator generation in our Prepar3D freeware catalogue. - Reinstall the complete aircraft package. Use the supplied installer or installation instructions and select the correct Prepar3D version. Copying only the aircraft folder is a mistake we see often: gauges, fonts, effects, sound modules and shared system files may be installed elsewhere. A repaint also requires its specified base aircraft.
- Check Windows blocking and security software. If Windows shows an Unblock option in the downloaded archive's properties, unblock it before extracting and reinstall the package. Review quarantine records for removed gauge modules, but restore or trust a file only when it came from the package you intentionally installed. If a Prepar3D trust prompt was denied, back up the simulator configuration before resetting only the relevant trust decision.
- Inspect the active panel configuration. Legacy aircraft normally sit under
SimObjects\Airplanes, while packages usingadd-on.xmlmay be stored elsewhere. Make sure you are not editing an unused duplicate copy, then checkaircraft.cfg, the selected panel folder and itspanel.cfg. - Restore fonts and cockpit textures. Missing fonts commonly remove radio frequencies, autopilot digits or glass-display text without removing the surrounding gauge. Missing panel textures can leave instruments transparent, white or unreadable. Reinstall these files using the package's documented method rather than moving them at random.
- Enable Content Error Reporting. Run Prepar3D once with its Content Error Reporting option enabled and read the generated log in that version's user-files location. Entries naming a missing gauge, failed alias, bad texture path or module-loading error are much more useful than repeatedly changing
panel.cfg.
What if the screens are present but black?
Black screens with intact bezels usually mean the display has loaded but has not initialised.
- All displays are black: check the battery bus, generators or external power, avionics master and brightness controls.
- The aircraft always reloads dead: reset its saved panel or aircraft state using the package's documented procedure, then test from a clean scenario.
- Power is available but no display wakes up: reinstall the complete package so that its avionics module and shared files are registered or placed correctly.
- Only one display remains blank: inspect the corresponding gauge entry and the content error log; a general power problem would normally affect more than one unit.
Do not assume every black glass cockpit is broken. Many airliners intentionally load cold and dark, and some require more than the basic Prepar3D battery and avionics switches.
Can FSX aircraft have blank instruments in Prepar3D?
Yes. The aircraft model may load correctly while its older gauge code fails, especially after moving from 32-bit FSX or Prepar3D v1–v3 to 64-bit Prepar3D v4 or later.
| Gauge design | What to expect in 64-bit Prepar3D | Suitable action |
|---|---|---|
| XML or CAB-based gauges | Often portable if their paths, textures, fonts and dependencies are present | Repair the installation and panel.cfg references |
| Native gauges built for the relevant Prepar3D generation | Expected to work when installed with all required modules | Use the matching package build and installer |
32-bit compiled .gau or .dll files | Will not load in Prepar3D v4 or later | Install a native 64-bit update or replace the panel |
| Protected or deeply integrated custom avionics | A generic replacement may not restore the FMS, autopilot or aircraft systems | Use an update designed for that aircraft |
No edit to panel.cfg can convert a 32-bit compiled gauge into a 64-bit one. Compatibility mode and running Prepar3D as an administrator do not change the gauge's architecture.
What does a broken panel.cfg or panel alias look like?
A bad panel selector or alias produces empty instrument spaces because Prepar3D is being directed to a folder or gauge package that does not exist.
In a livery's [fltsim.x] section, an empty panel= value selects the standard panel folder. A value such as panel=wide selects panel.wide. If only one repaint fails, compare that value with a working repaint before changing anything else.
Inside panel.cfg, an alias= entry points to another installed aircraft's panel. The target aircraft and panel folder must both exist. Gauge lines such as gauge00=Package!Gauge,... must refer to a matching gauge package in the panel or gauge locations used by that installation.
Do not extract CAB files, rename gauge modules or renumber entries unless the package instructions require it. Make a backup first and change one item at a time.
Why does the 2D panel work while the virtual cockpit stays blank?
A working 2D panel proves that the gauge package can load; the fault is usually confined to the virtual cockpit.
The pop-up windows use [WindowXX] sections, while virtual-cockpit displays use [VCockpitXX]. Missing entries, incorrect gauge coordinates or a panel built for a different virtual-cockpit model can leave only the VC blank. A replacement 2D panel does not automatically repair the model's VC texture mapping or clickspots.
When is a replacement panel the right fix?
Use a replacement panel when the aircraft model is otherwise sound but its original gauges have no compatible Prepar3D build.
The replacement must match your Prepar3D generation and may change the cockpit layout or remove aircraft-specific functions. A focused repair is preferable when only files or configuration entries are missing; this A340 gauge-and-panel repair package illustrates how supplying the panel's required gauge files can restore instruments, though any such fix still needs to be compatible with the Prepar3D version being used.
“Sigue igual”: what if it is still the same?
If the panel sigue igual—still blank after a clean reinstall and the checks above—stop making random configuration edits and use the remaining pattern to identify the fault.
- One old aircraft fails while stock aircraft work: hard gauge incompatibility is the likely cause. Find a native update or compatible replacement panel.
- Only one repaint fails: correct its
panel=selection and confirm that the required base aircraft is installed. - All third-party panels fail but stock panels work: recheck blocked files, quarantine actions, inactive add-on packages and shared gauge locations.
- Stock aircraft fail as well: back up your files, test with a fresh Prepar3D user configuration and verify or repair the simulator's installed content.
- The 2D panel works but the VC remains blank: the gauge itself is not globally missing; the virtual-cockpit configuration or model mapping is incompatible.
Reinstalling the whole simulator rarely fixes one isolated FSX-era aircraft. When every other cockpit works and the affected panel depends on 32-bit compiled gauges, a compatible gauge or panel replacement is the only practical solution.