Install a 2D cockpit panel in FSX or Steam Edition safely, with correct panel folders, panel.cfg entries, gauges and fixes for blank panels.
To install a 2D cockpit panel in FSX or FSX: Steam Edition, back up the aircraft’s existing panel folder, copy the new panel files into that aircraft’s folder, install any supplied gauges, then set the correct panel= value in aircraft.cfg if the package uses a named panel folder.
Identify what the panel download contains
Read the package instructions before copying anything because FSX panels are distributed in several forms. A folder called panel is usually a complete replacement, while a bitmap accompanied by configuration text is more likely an extra popup window that must be merged into the existing panel.
| Package type | Typical contents | Installation method |
|---|---|---|
| Complete replacement | panel.cfg, bitmaps and possibly gauges | Install as panel or as a named alternate such as panel.my2d |
| Additional popup window | Bitmap plus [WindowXX] configuration text | Merge the supplied entries into the existing panel.cfg |
| Structured FSX package | SimObjects, Gauges and other top-level folders | Merge those folders into the FSX root while preserving their structure |
For comparison, this complete F-4 replacement-panel package uses a different method from this cabin-window panel that is merged into an existing configuration.
Install the FSX 2D panel step by step
- Extract the download outside FSX. Do not work directly inside the compressed archive. Check for a readme and identify whether the files form a complete panel or an addition to one.
- Close FSX. Locate the aircraft under
<FSX>\SimObjects\Airplanes\<aircraft folder>. In Steam Edition, the FSX root is normally inside the Steam library understeamapps\common\FSX; a boxed installation may be elsewhere. - Make a backup. Copy the aircraft’s existing
panelfolder andaircraft.cfgsomewhere outside the active aircraft directory. This matters because a replacementpanel.cfgcan also alter virtual-cockpit instruments. - Copy the panel files. For a direct replacement, put the new
panel.cfgand its bitmaps in the aircraft’spanelfolder. Check that the result ispanel\panel.cfg, not the common mistaken layoutpanel\panel\panel.cfg. - Install an alternate panel when appropriate. Name its folder something such as
panel.my2d. In each relevant[fltsim.x]section ofaircraft.cfg, setpanel=my2d. A blankpanel=selects the ordinarypanelfolder; do not enterpanel=panel.my2d. - Copy the required gauges. Preserve the supplied folder structure and do not rename or unpack gauge archives unless the instructions explicitly require it. Our FSX gauge installation instructions cover global gauge files, panel references and Steam Edition paths in detail.
- Test the exact aircraft variant. Start FSX and select a livery whose
[fltsim.x]entry points to the new panel. The main 2D panel is usually toggled withShift+1; other windows can be opened from the simulator’s instrument-panel menu.
FSX may display a security prompt when a newly installed gauge loads for the first time. Approve only a gauge that came from the panel package you deliberately installed.
Should I replace the panel folder or install an alternate?
A named alternate panel is the safer choice when you want to retain the stock panel or apply the new cockpit only to selected liveries. A direct replacement is simpler when the download was designed as a complete substitute for one specific aircraft.
Take extra care with aircraft that have a virtual cockpit. The 2D windows use sections such as [Window00], while virtual-cockpit gauges use [VcockpitXX]. Replacing the whole panel.cfg with one that lacks the required virtual-cockpit sections can leave the 3D cockpit present but its instruments blank.
Do not combine unrelated panel and virtual-cockpit sections without a backup. Gauge coordinates and texture assignments are often specific to the aircraft model.
How do I add only one 2D popup window?
Add a single popup by merging its title, window section, bitmap and gauges into the aircraft’s existing panel rather than overwriting the whole configuration.
- Choose an unused window number. In
[Window Titles], add the supplied title using the next freeWindowXXentry. - Add the matching section. Paste the supplied
[WindowXX]block intopanel.cfg. If you changed its number because that slot was occupied, change both the title entry and section heading. - Copy the bitmap. Place the referenced background image directly in the active panel folder, retaining its original filename.
- Install its gauges. Copy all dependencies named by the package. Gauge numbering only needs to be unique within that particular window section.
A mistake we see constantly is replacing the complete [Window Titles] section with the download’s short example. That removes the aircraft’s existing radio, GPS and other popup-window references; merge the new line instead.
Why does the new 2D panel not appear?
A missing panel is usually caused by the wrong aircraft folder, an incorrect panel= value, a nested folder or incomplete [Window Titles] and [WindowXX] entries.
- The old panel still opens: check the selected livery’s exact
[fltsim.x]section. Different variants can point to different named panel folders. - No main 2D panel is listed: confirm that
[Window Titles]referencesWindow00and that a matching[Window00]section exists. - The background appears but instruments are blank: one or more gauges are missing, blocked or incompatible with FSX. Use our blank cockpit instrument troubleshooting steps to trace the failed references.
- The virtual cockpit loses its displays: restore the backup because the replacement configuration probably omitted or changed the aircraft’s
[VcockpitXX]sections. - FSX hangs when the panel opens: restore the original panel and remove the newly added gauges. Old or incompatible compiled gauges are a common cause.
- Configuration changes will not save: Windows may be protecting an FSX installation under
Program Files. Edit a copied file and move it back with administrator approval rather than relying on a hidden virtualised copy.
Panels made for older Flight Simulator releases are not automatically compatible with FSX. Their bitmaps and configuration may load while legacy gauges fail, so use a package that explicitly supports FSX whenever possible.