X-Plane 737NG Maintenance Toolkit

Cross-platform desktop app for Zibo and LevelUp 737NG maintenance tasks. It manages aircraft and VNAV packages, explicit optional patches, X-Plane-wide tools, verified liveries and conservative view maintenance for supported aircraft variants.

This repository is the public development home for the app. The architecture keeps package content, aircraft patching, and application updates separate.

Release version: 0.21.0

Includes catalog-controlled maintenance groups and configurable startup update notifications.

• Download the latest stable release
• Read the user manual
• Use the prepared X-Plane.org listing

• X-Plane 12. X-Plane 11 is not supported.
• Zibo 737-800X 2K and 4K variants.
• LevelUp 737-600, 737-700, 737-800, 737-900 and 737-900ER.
• Windows x64.
• macOS arm64 (Apple silicon).
• macOS x64 (Intel 64-bit).
• Linux x64.

Aircraft detection is structural. A folder name alone is not accepted as proof of a supported installation.

Choose one normal-use artifact from the latest GitHub Release:

On Windows or macOS, run the setup package or extract the portable ZIP and start the app from the extracted folder. On Linux, make the AppImage executable and run it:

chmod +x XPlane737NGMaintenanceToolkit-stable-linux-x64.AppImage
./XPlane737NGMaintenanceToolkit-stable-linux-x64.AppImage

Current public packages are unsigned. Platform signing and notarization belong to the release policy for later signed distribution.

• Windows may display a SmartScreen warning.
• macOS may block the unsigned, non-notarized build.
• Linux AppImage builds are not separately signed.

Verify downloaded artifacts against SHA256SUMS.txt on the release page. If a verified macOS download is blocked, follow Apple's documented Privacy & Security "Open Anyway" process.

VeloPack-managed installations check for stable Toolkit updates in the background. When an update is available, the app offers a cancellable verified download followed by an explicitly confirmed restart. Aircraft, VNAV, patch, tool, resource and livery updates remain separate from Toolkit application updates.

1. Close X-Plane.
2. Start the Toolkit and use Auto-detect, or browse to an X-Plane, Aircraft, Zibo or LevelUp folder.
3. Select the required detected product when more than one is available.
4. Click Scan selected folder.
5. Use the main Update action and review each confirmation before files are changed.

The Advanced tab contains detailed review, recovery and diagnostic controls. The Settings tab contains backup, cache, offline-package and diagnostics directories. Aircraft and patch releases are checked automatically after startup for the detected product, without installing anything. Disable Check aircraft and patch releases at startup in Settings to use manual checks only.

Hardware configurations on Start copies the saved hardware configuration between detected Zibo and LevelUp variants within one X-Plane installation. Find configurations, choose an existing source, select destinations, and click Copy selected. Close X-Plane first. Restore last hardware copy restores the previous files and removes files created by the copy; subsequent edits are protected. Zibo 2K/4K and multiple installations of the same aircraft variant share their corresponding configuration in Output/preferences.

This toolkit is provided as-is, without warranty of any kind. It is an independent community tool and is not an official X-Plane, Zibo or LevelUp product unless explicitly stated otherwise.

The app displays this distinction on every screen. Before it installs, updates or repairs independent packages in a Zibo aircraft, its confirmation dialog requires a separate acknowledgement. For Toolkit support, use the MTK Discord server or the comments on the Toolkit project page. Optimized XLua has its own project page. Official Zibo support does not cover those changes.

The toolkit can modify aircraft installation files after validation and backup. Users should keep their own backups and use the tool at their own risk.

Current capabilities:

• It can detect likely Zibo and LevelUp aircraft folders.
• It can scan a manually selected folder.
• It explicitly detects LevelUp port/no-Lua installs as not applicable to the Lua patch package.
• It parses the current v1 package manifest format for LevelUp and Zibo VNAV table packages.
• It classifies hook state in B738.a_fms.lua.
• It shows component status, findings and planned changes.
• It can apply Quick View 0 to the ACF default view after creating a backup.
• It can adapt X-Plane quick views after an ACF CG change after creating a backup.
• It can optionally adapt a matching X-Camera_<acf-stem>.csv file when one is present.
• For LevelUp installations, it can copy every Quick View from one selected variant to all other variants in the same aircraft folder. Each target is corrected for its ACF CG. A separate confirmation controls whether the transferred Quick View 0 also becomes each target's Default Viewpoint.
• It can create and restore dedicated config backups for root-level aircraft preferences, camera CSVs, cfg files and toolkit metadata.
• It can install, update, repair and uninstall manifest-owned VNAV Lua hooks and payload files after validation and backup.
• It supports explicit optional schema-v2 patch packages through the same transaction engine. Optional packages are never folded into the automatic aircraft/VNAV update flow and require a separate user confirmation.
• The bundled catalog offers the LevelUp FANS CDU package as an explicit, optional LevelUp-only patch. Its manifest, payload hashes and supported source structures are validated before any aircraft file is changed.
• It ships a versioned trusted package catalog and checks immutable catalog-v* GitHub Releases for newer package metadata. A remote catalog is used only after schema and minimum Toolkit version validation; the last valid cache and bundled catalog remain fallbacks. The Start page filters managed content and optional patches by the selected Zibo or LevelUp product. Trusted optional entries can resolve their latest stable GitHub Release directly; manual package-folder selection remains an Advanced fallback.
• It offers optional aircraft components and X-Plane-wide tools for compatible detected products. Optimized XLua is managed separately for each selected Zibo or LevelUp aircraft at plugins/xlua, while preserving the complete aircraft-owned scripts tree. YAL is available for both products at Resources/plugins/YAL; YAL HoppieHelper is also available for both products at Resources/plugins/YAL_HoppieHelper, matching its published release manifest. YANSH is available for both products at Resources/plugins/YANSH from Olivier Butler's verified stable release manifest.
• It offers optional XLinSpeak on Linux x64 at Resources/plugins/XLinSpeak. Piper, a voice model and audio output configuration must be provided separately. Platform-specific tools are shown and installed only on supported systems.
• It offers the optional 737NG Realbench Logger for both products as a verified X-Plane-root overlay. The Toolkit owns only the declared DataRefMonitor runtime, profile and preference files; unrelated profiles and generated logs under Output/DataRefMonitor are preserved during install, repair and restore.
• Stable and Beta channels are selected independently per optional component or tool and from app and aircraft updates. Release manifests, GitHub asset digests, archives and every payload SHA-256 must agree before install, update or repair.
• Component and tool updates preserve manifest-declared configuration and output paths plus local unowned files, create generation backups and provide guarded restore.
• It offers verified product resources independently from aircraft updates. The LevelUp 737NG Paintkit can be downloaded from its official public release and safely extracted into a user-selected directory outside X-Plane.
• It can install, update, verify, explicitly repair and remove catalog-listed livery packages for the selected aircraft. Livery state is recorded per aircraft folder; unmanaged directories and locally changed managed liveries are never overwritten by a normal install or update.
• GitHub optional-package archives are selected by an explicit asset pattern, checked against GitHub's published size and SHA-256 digest, and safely reduced to the declared manifest and payload files in the local cache.
• Declarative optional packages may use only built-in exact-text, OBJ8, bounded sparse-byte and PNG-region operations. Downloaded packages cannot execute scripts inside the toolkit.
• It can restore the latest recorded backup generation for the selected aircraft variant.
• Before a VNAV write action it tries to refresh package-manifest.txt and payload files from the package GitHub Release assets. The bundled manifest and local/offline package directories are fallback sources.
• It can review Zibo upstream baseline/cumulative package plans, import exact matching aircraft update ZIPs into a local cache, download direct ZIP sources when available or use the official BitTorrent metadata, review cached ZIP contents in the background, then confirm and apply cached packages with backups, rollback and restore support.
• It can read the authorized public LevelUp release index, select either the exact full aircraft package or the matching cumulative patch, verify the published manifest/archive hashes, and use the same review and transactional update path. Manual LevelUp manifest/archive import remains available as an offline fallback.
• It can install a new Zibo 737-800X or LevelUp 737NG Series into an unused direct child folder of a selected X-Plane 12 Aircraft directory. The app plans the complete release, validates every package in an external staging folder, verifies the expected product structure and only then activates the new aircraft folder. It never overlays a fresh install onto an existing destination.
• LevelUp fresh installs can download the exact verified full package from the authorized public release index. Zibo fresh installs use the official full-baseline plus latest-cumulative-patch plan. The Toolkit can download the exact archives through the feed's .zip.torrent metadata, with cancellation, live peer/rate progress, torrent piece verification and archive validation.
• Package import, download and pre-write validation are cancellable. Once the confirmed aircraft write transaction starts, it completes or rolls back.
• The main Update action checks aircraft and VNAV package state in one user flow. A validated offline LevelUp package remains active when Update is clicked and is not replaced by an unavailable online release check. The flow can continue with VNAV-only maintenance when no aircraft update is available or required.
• The main Update action is hidden after the app has established that neither an aircraft-package action nor a safe VNAV action is available.
• Aircraft and VNAV writes remain separate confirmed transactions with independent backup, rollback and restore state.
• It distinguishes full aircraft updates, which include a full baseline ZIP, from incremental updates, which apply only the latest cumulative patch ZIP for the same baseline. Full updates build and validate a clean staged aircraft image, migrate only protected preferences and local liveries, retain the complete previous directory and activate the new baseline by transactional directory exchange.
• A verified aircraft-scoped component such as Optimized XLua is retained inside the same incremental or full-baseline aircraft transaction. Unknown or locally modified component binaries block the aircraft update until the component is repaired.
• The UI follows the operating system's light or dark appearance.

Review remains available for planned changes before write actions. Real write actions are limited to manifest-owned VNAV content, explicitly selected declarative patch packages, view-maintenance files and explicitly applied cached aircraft update packages. For Zibo, a direct ZIP is attempted first; if the feed exposes .zip.torrent metadata and no direct archive is available, the Toolkit uses an embedded BitTorrent client with DHT, PEX and tracker fallbacks. The user must confirm P2P networking because peers can see the public IP address and the client may upload package pieces while downloading. LevelUp uses explicit GitHub Release assets described by its public release index. Manual import remains available as an offline fallback.

dotnet build LevelUp.NavTableUpdater.slnx

dotnet test tests/LevelUp.NavTableUpdater.Core.Tests/LevelUp.NavTableUpdater.Core.Tests.csproj

dotnet run --project src/LevelUp.NavTableUpdater.App/LevelUp.NavTableUpdater.App.csproj

The app requires a usable desktop GUI session.

For offline or development package testing, set XPLANE_737NG_PACKAGE_DIR to a folder containing package-manifest.txt and all manifest payload files. GitHub Release assets remain the preferred package source for normal use.

• User Manual
• Product Specification
• CI/CD Preparation
• Zibo ACF CG Catalog Builder
• LevelUp ACF CG History
• Directory Tool-Package Migrations

• .NET 10.
• Avalonia UI.
• VeloPack SDK startup hook via VelopackApp.Build().Run().
• Manifest-driven package support for LevelUp and Zibo VNAV content.
• Generic transactional content-patch engine with managed VNAV and explicit opt-in lifecycle policies.
• Product-scoped trusted content catalog with secure GitHub Release package provisioning, immutable remote catalog releases, last-known-good caching and a bundled fallback for optional declarative patches.
• Product-gated aircraft components and X-Plane-wide tool packages with separate Stable/Beta release channels and transactional install/update/repair/restore.
• Optional tool-package dependencies with minimum-version checks, transitive planning, one explicit confirmation and dependent-safe restore/downgrade guards.
• File-wise X-Plane-root overlay packages for tools whose declared runtime files span multiple simulator directories without claiming generated data.
• Aircraft detection and install-state analysis.
• Real backup-backed View Utility operations.
• VeloPack packaging workflow.
• GitHub Release publishing path for VeloPack app artifacts.
• Real VNAV Lua patch writes for manifest-owned hooks and payloads.
• GitHub Release manifest/payload loading with local/offline fallback.

The app references the Velopack NuGet package and calls VelopackApp.Build().Run() at the start of Program.Main, before Avalonia is initialized. That is the required application-side hook for install/update lifecycle handling.

The app creates a VeloPack UpdateManager backed by the public GitHub Releases source. Managed installations check the package channel in the background, show an Update/OK popup when a newer stable version is available, and retain the banner for progress or a later update. Update downloads and verifies the selected VeloPack package with progress/cancellation and applies it only after explicit restart confirmation. An update failure never blocks normal maintenance functions. Startup checks can be disabled in Settings; a manual check remains available. This remains separate from aircraft-package, VNAV-content, optional-patch, tool and resource update sources.

Packaging is available through the manual VeloPack GitHub Actions workflow. The workflow produces Windows, macOS and Linux VeloPack artifacts for the selected release channel.

This app is licensed under the MIT License. See LICENSE.