How do I install and update the Zibo 737-800 in X-Plane 12?
Install the X-Plane 12 Zibo 737-800 by extracting the official full package into X-Plane 12/Aircraft, leaving one B737-800X folder. To update it, merge the correct XP12 patch into that folder and overwrite matching files. Never patch Laminar Research’s default 737 or leave the aircraft double-nested.
How do I install the Zibo 737-800 in X-Plane 12?
Use a fresh full package labelled for X-Plane 12 and install it as a standalone aircraft.
- Close X-Plane 12. Do not add or replace aircraft files while the simulator is running.
- Locate the active installation. Open the X-Plane 12 directory containing the simulator executable, then open its
Aircraftfolder. This matters if you have Steam and standalone copies or an older installation on another drive. Our broader X-Plane 12 aircraft installation guide explains how to identify the correct directory. - Obtain the full XP12 package. Use the Zibo project’s official distribution method and confirm that the package is for X-Plane 12, not X-Plane 11. An update or fix package is not normally a complete aircraft.
- Extract the archive first. Unpack it to a temporary location rather than trying to run the aircraft from inside the compressed file.
- Copy the aircraft folder. The finished location should be
X-Plane 12/Aircraft/B737-800X. That folder should directly contain the aircraft’s.acffile and its supporting folders, including the aircraft-localpluginsdirectory. - Start X-Plane 12 and select the Zibo aircraft. Keep Laminar Research’s default 737 installed separately; Zibo does not replace or modify it.
A mistake we see constantly is Aircraft/B737-800X/B737-800X. If opening the first folder reveals another identically named folder before you reach the .acf file, move the inner folder up one level.
Do not move Zibo’s included plugins into X-Plane’s global Resources/plugins folder. They are aircraft-specific and must remain inside B737-800X.
How do I apply a Zibo update without breaking it?
Apply an update only to the XP12 full-package version for which it was released, preserving the archive’s folder structure.
- Read the update notes. Check whether the patch is cumulative or requires a particular full package or earlier update. Do not stack unrelated fixes in numerical order unless the instructions require it.
- Back up user content. Save any liveries and documented user configuration files you want to keep. Put a complete backup outside the
Aircraftdirectory so X-Plane does not detect two Zibo installations. - Extract the update elsewhere. Open the unpacked update and identify the level containing its aircraft files and folders.
- Merge it with the existing installation. Copy those contents into
X-Plane 12/Aircraft/B737-800X, allowing matching files to be overwritten. The operation must merge with the existing folder, not create anotherB737-800Xinside it. - Restart X-Plane 12. Load the aircraft and check the version information shown by the Zibo tablet or the package’s documented version display.
On macOS, be careful with Finder’s whole-folder Replace operation: depending on how the copy is performed, it can remove destination files that are absent from a small patch. Merge the contents with a merge-capable copy operation rather than replacing the complete aircraft directory with the patch directory.
Should I update in place or perform a clean install?
Use an in-place update for a compatible incremental patch; use a clean installation after a large version jump, an unknown patch history or unexplained aircraft failures.
| Situation | Best method |
|---|---|
| First Zibo installation | Install the latest suitable full XP12 package, followed only by any required update. |
| Small compatible update | Merge the patch into the existing B737-800X folder and overwrite matching files. |
| Unknown or heavily modified installation | Move the old folder outside Aircraft, install a clean full package and test it before restoring liveries. |
| Problems immediately after patching | Reinstall from a fresh full package rather than layering more patches over mixed files. |
Do not blindly restore every old configuration file after a clean installation. A preference file from an incompatible build can recreate the fault you were trying to remove.
Why is the Zibo 737 missing or not working after installation?
The usual causes are a double-nested folder, the wrong simulator package, an incomplete extraction or files copied into a different X-Plane installation.
- Aircraft absent from the selection screen: confirm that an
.acffile sits directly insideAircraft/B737-800Xand that you launched the same X-Plane copy you modified. - Two Zibo aircraft appear: move old installations and backups completely outside the
Aircraftdirectory. - Aircraft loads with a dead cockpit or tablet: suspect mixed full-package and patch files, or an aircraft-local plugin that failed to load. Check
Log.txtin the X-Plane root for plugin errors. - Plugins are blocked on macOS: review the operating system’s security warning and approve only components obtained from the trusted package source, then restart X-Plane.
- The problem began with an X-Plane beta: confirm that the installed Zibo build declares compatibility with that simulator branch.
If the folder looks correct but the aircraft remains absent, work through our aircraft detection and folder-structure checks.
Does a Zibo update also update FMC navigation data?
No; a Zibo aircraft update does not automatically update X-Plane’s navigation database or AIRAC cycle.
If the 737 loads correctly but its FMC lacks an expected SID, STAR or waypoint, that is usually a navdata issue rather than a failed Zibo installation. Follow our guide to installing and troubleshooting SIDs and STARs in X-Plane 12 instead of reinstalling the aircraft.