QuextFlight X-Plane Plugin - Windows x64
Package version 1.0.1 | Exact native binary build 20260831 | October 7, 2026
Publisher: Quext Interactive Technologies, Inc.
UNSIGNED SOFTWARE: the installer scripts and FlightCommand.xpl are not digitally signed.

REQUIREMENTS
  Windows 10/11 on an Intel/AMD x64 PC; Windows PowerShell 5.1;
  X-Plane 12.3.0 or newer in the 12 series.
  Microsoft Visual C++ v14 x64 runtime 14.44.35211 or newer must already be installed.
  Official Microsoft runtime information/download:
  https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist
  No Mac, Linux, ARM64 Windows, X-Plane 11, or older X-Plane 12 binary is included.

INSTALL
  1. Download the ZIP from flyquext.com and choose Extract All in Windows Explorer.
     Do not run the installer from inside the ZIP viewer.
  2. Close the X-Plane installation you want to update.
  3. Double-click "Install QuextFlight X-Plane Plugin.cmd".
  4. Select the X-Plane root folder containing X-Plane.exe and Resources\plugins.
     The installer verifies the version, architecture, prerequisites and payload.
     It installs to Resources\plugins\FlightCommand\win_x64\FlightCommand.xpl.
  5. Start X-Plane normally yourself. In its Log.txt, look for a Loaded line for
     FlightCommand.xpl and "[FlightCommand] Plugin started.".

  If your installation folder is not writable by your Windows account, this
  installer reports the permission error. It does not request elevation, change
  permissions, install prerequisites, change the firewall, or launch X-Plane.
  Managed execution policies may prevent unsigned scripts from running. Follow
  your administrator's policy; do not change machine-wide security settings.

  Command-line alternative (from the extracted folder):
    powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\quextflight-plugin-manager.ps1 -Action Install -XPlanePath "D:\X-Plane 12"
  ExecutionPolicy Bypass applies only to this one PowerShell process.

CONNECT YOUR IPAD
  Connect the Windows PC and iPad to the same trusted local network. Wi-Fi must
  be enabled on the iPad; the PC may use Ethernet on the same LAN. An isolated
  guest network, VPN, separate subnets, or router client isolation can prevent
  discovery. This plugin needs no Node.js bridge or cloud service.
  In QuextFlight choose X-Plane as the position source. Allow iPad Local Network
  access if prompted. The app advertises FLIGHTCOMMAND_BEACON on UDP 49042.
  The plugin learns the iPad address and sends UTF-8 JSON telemetry to UDP 49042
  at 20 Hz. Broadcast is a fallback. The existing legacy beacon remains accepted.
  Confirm fresh simulator position and time appear in QuextFlight. Restore your
  intended position source after simulator use.

  The same existing plugin supports route transfer, approach/direct-to handling,
  simulator flight guidance and weather sync sent by compatible QuextFlight builds.
  Those commands can alter simulator position, FMS, autopilot settings or weather.
  Use a trusted LAN and apply any simulator changes deliberately. This is for
  simulator use. Aircraft-specific autopilots and installed navdata can affect
  command results; check the simulator and app acknowledgements.

UPGRADE AND UNINSTALL
  Upgrades keep the existing flightcommand.cfg, screen images, custom assets and
  other files in FlightCommand. The previous complete folder is backed up first.
  A recognized legacy AviateTelemetry folder is also moved to an inactive backup
  on installation, preventing duplicate telemetry plugins from remaining active.
  Backups live outside Resources\plugins:
    <X-Plane>\.quextflight-plugin-backups\<timestamp-and-unique-id>\
  The installer reports the exact backup folder. Keep it for recovery.
  Uninstall by closing the selected X-Plane and running
  "Uninstall QuextFlight X-Plane Plugin.cmd" from this extracted download, then
  selecting that X-Plane root. An installed launcher is also provided at
  <X-Plane>\.quextflight-plugin-backups\uninstaller\
  Uninstall moves the ENTIRE FlightCommand folder into an inactive backup;
  it does not delete settings, user data, other plugins or prior backups. It does
  not automatically re-enable AviateTelemetry.
  To restore a previous version with X-Plane closed, move the current FlightCommand
  folder somewhere outside Resources\plugins, then copy the chosen backup's
  FlightCommand folder back into Resources\plugins. Retain the backup. Avoid
  restoring both FlightCommand and AviateTelemetry at the same time.

TROUBLESHOOTING
  Plugin absent from Log.txt: check the folder layout and X-Plane version. Missing
  MSVCP140/VCRUNTIME140 errors indicate the Microsoft x64 runtime prerequisite.
  "UDP socket is unavailable": check for another telemetry plugin/bridge already
  using UDP 49042. Close that application or disable the duplicate plugin yourself.
  No fresh telemetry: verify X-Plane is loaded, X-Plane position source is selected,
  iPad Local Network permission is allowed, and both devices share the same LAN.
  Review your existing firewall/security rules for X-Plane local UDP 49042 traffic.
  The installer does not create firewall rules. If rules must be changed, decide
  that separately with your Windows/network administrator; do not disable the
  firewall as a troubleshooting shortcut.
  Fixed iPad address: with X-Plane closed, edit flightcommand.cfg; set destination
  to the iPad's LAN IP and broadcast=0. Keep port=49042. Discovery normally avoids
  this manual step. Custom settings are preserved by subsequent installs.
  Virtual cockpit iPad overlay: excluded from the public package; disabled on a
  fresh install. Previously installed local overlay files/settings are preserved.
  For help, include X-Plane version, package version, relevant [FlightCommand] log
  lines and the app's connection status at https://flyquext.com/support/.

VERIFICATION AND TEST COVERAGE
  SHA256SUMS.txt lists every distributed file except itself. After extraction,
  Get-FileHash -Algorithm SHA256 .\FlightCommand\win_x64\FlightCommand.xpl
  can be compared with package-manifest.json and the published checksum file.
  This package copies the exact installed FlightCommand.xpl without rebuilding it.
  Its SHA-256 matches the August 31 Release build and distribution copy:
  5e546ccaef50b43775faecc51101d75aec074bc02dcfdb62a924596a71b935b5
  The plugin retains its internal FlightCommand name/signature for client compatibility.
  Installer install/upgrade/uninstall, backup, rollback, corruption rejection and
  path validation are tested in a disposable folder. Dave's existing installed
  FlightCommand binary loaded in X-Plane 12.4.3 per the existing simulator log.
  The publisher reports live telemetry working with this installed binary. A fresh
  simulator/iPad session was not run during packaging. X-Plane
  12.3.0 is the verified API minimum, not a separately executed simulator test.
  Current app 1.0.4 build 51 was reported working; no live app/simulator install or
  flight-guidance acceptance test was performed for this package. The exact historical
  source snapshot for this August 31 binary was not retained in the inspected files;
  the original build/install record identifies the source project and binary hash.
  Current synchronized C++ source is newer. The previously published package 1.0.0
  is an untested rebuild and is not the recommended match for the installed version.
  The native binary matches the working installation byte-for-byte; fresh default
  configuration omits the optional marketing cockpit overlay. Network settings
  retain the installed defaults. Existing configurations/assets survive upgrades.

LEGAL AND CONTENTS
  Use is governed by the applicable QuextFlight EULA: https://flyquext.com/eula.php.
  See THIRD-PARTY-NOTICES.txt. This download contains only the native Windows plugin,
  configuration, package metadata and installer/help files. It includes no X-Plane
  executable, SDK headers/libraries, aircraft, navdata, charts, marketing images,
  screen capture, Node bridge, or Microsoft runtime installer.
