Getting Started
Flight Code-X requires X-Plane 12 and follows X-Plane 12's minimum system requirements. Consult the current X-Plane 12 system requirements for hardware, graphics-driver, and operating-system requirements. Note for Linux we test on Ubuntu 22.04 and not every available distro your specific setup may need some tweaking.
In this manual, `<X-Plane>` means your X-Plane installation folder. Flight Code-X is installed within: <X-Plane>/Resources/plugins/FlightCodeX/
Runtime loads as an X-Plane plugin. Studio is in the plugin's `studio` folder. The launch paths used by Runtime are:
Flight Code-X requires X-Plane 12 and follows X-Plane 12's minimum system requirements. Consult the current X-Plane 12 system requirements for hardware, graphics-driver, and operating-system requirements. Note for Linux we test on Ubuntu 22.04 and not every available distro your specific setup may need some tweaking.
In this manual, `<X-Plane>` means your X-Plane installation folder. Flight Code-X is installed within: <X-Plane>/Resources/plugins/FlightCodeX/
Runtime loads as an X-Plane plugin. Studio is in the plugin's `studio` folder. The launch paths used by Runtime are:
Platform |
Studio application in `FlightCodeX/studio/` |
Linux |
`FlightCodeX-studio` |
Configure |
`FlightCodeX-studio.app` |
Generate |
`FlightCodeX-studio.exe` |
You can also use Start Studio in the Flight Code-X plugin menu. Keep the
installed folder structure intact so Studio can locate the product data and
X-Plane installation.
Install Flight Code-X
The installer sets up Studio, Runtime, and the supplied demop scenarios in your
chosen X-Plane 12 installation. An internet connection is needed for its
component downloads.
1. Download the Flight Code-X installer ZIP for your operating system from
the Flight Code-X download page. Use the package for the release you intend
to install.
2. Unpack the ZIP into your X-Plane 12 installation folder, then run the
extracted installer application. Extract the archive first; do not run the
application from inside the ZIP.
3. In X-Plane install directory, select the installation you want to use.
Check the full path, especially if you have more than one X-Plane copy.
Select the X-Plane folder itself, not its `Resources/plugins` subfolder.
4. Enter your license key in Key, or leave it blank to use the demo.
You can manage your license later using the controls in the next section.
5. Select Install Flight Code-X. For a blank key, the installer asks you
to acknowledge demo installation; select Understand to continue.
6. Wait for installation to complete. The **Studio**, **Runtime**, and
Scenarios indicators show progress; Pending means the work has not
completed. When installation succeeds, select Finish Install you can also start X-Plane
or the Studio directly and the install will finish.
7. Start X-Plane 12 and open its Flight Code-X plugin menu. Use Start Studio
to begin authoring, or launch Studio from the platform-specific path above.
Installed product files are under
`<X-Plane>/Resources/plugins/FlightCodeX/`. Unpacking the installer ZIP is the
preparation step; the installer then downloads and installs the components.
If installation reports Error, read the accompanying message before
continuing. If the intended X-Plane installation is not listed, check that
you are selecting the correct X-Plane 12 folder; use Custom location...
when available. If selection remains unavailable, contact support with the
message and operating system, keeping your license key out of screenshots.
License activation and management
License management validates access to Flight Code-X and provides the controls
for changing a key or unregistering a machine.
Licences are limited to activation of two machines at a time.
Options and Settings
In Studio, open Help → Licence Manager. The window contains License Key,
Validate, Unregister, and Close. Runtime license window is available
through Licence in the plugin menu.
Enter a key and select Validate. Studio reports validation success or failure.
Close discards an unsubmitted change to the displayed key. Unregister performs
a machine-unregistration operation; it is not the same as closing the window.
Important Notes
Demo access can have limits. Studio's demo generation limit is 20 nodes;
Runtime can stop a scenario when the demo session time has exceeded
30 minutes of total scenario run time. Consult
the displayed access status when controls are unavailable. Keep license keys
out of shared projects, screenshots, and support attachments.
The 30 minutes of elapsed time while a scenario is
loaded, accumulated within the plugin session. X-Plane pause does not suspend
that budget, and stopping/reloading a scenario does not create a new allowance.
Open, generate, and run
Use File → Open in Studio to open a `.simp` project. Select resources in
the scenario pane or nodes on the canvas to inspect their properties.
File → Save saves authoring changes; File → Generate saves the project
and attempts to produce its Runtime files. Read any System Message errors and
wait for Generation complete before treating the result as ready to run.
Runtime looks beneath the plugin's `scenarios` folder. A runnable scenario uses
a folder and generated files with matching names, for example:
scenarios/
Example/
Example.simp
Example.simc
Example.sims
assets/
The `.simp` file is for editing; Runtime discovers the `.simc`/`.sims` pair.
In the Runtime scenario selector, use Refresh after adding generated files,
select a scenario, and choose Load. The scenario author determines its
starting conditions and subsequent flow.
installed folder structure intact so Studio can locate the product data and
X-Plane installation.
Install Flight Code-X
The installer sets up Studio, Runtime, and the supplied demop scenarios in your
chosen X-Plane 12 installation. An internet connection is needed for its
component downloads.
1. Download the Flight Code-X installer ZIP for your operating system from
the Flight Code-X download page. Use the package for the release you intend
to install.
2. Unpack the ZIP into your X-Plane 12 installation folder, then run the
extracted installer application. Extract the archive first; do not run the
application from inside the ZIP.
3. In X-Plane install directory, select the installation you want to use.
Check the full path, especially if you have more than one X-Plane copy.
Select the X-Plane folder itself, not its `Resources/plugins` subfolder.
4. Enter your license key in Key, or leave it blank to use the demo.
You can manage your license later using the controls in the next section.
5. Select Install Flight Code-X. For a blank key, the installer asks you
to acknowledge demo installation; select Understand to continue.
6. Wait for installation to complete. The **Studio**, **Runtime**, and
Scenarios indicators show progress; Pending means the work has not
completed. When installation succeeds, select Finish Install you can also start X-Plane
or the Studio directly and the install will finish.
7. Start X-Plane 12 and open its Flight Code-X plugin menu. Use Start Studio
to begin authoring, or launch Studio from the platform-specific path above.
Installed product files are under
`<X-Plane>/Resources/plugins/FlightCodeX/`. Unpacking the installer ZIP is the
preparation step; the installer then downloads and installs the components.
If installation reports Error, read the accompanying message before
continuing. If the intended X-Plane installation is not listed, check that
you are selecting the correct X-Plane 12 folder; use Custom location...
when available. If selection remains unavailable, contact support with the
message and operating system, keeping your license key out of screenshots.
License activation and management
License management validates access to Flight Code-X and provides the controls
for changing a key or unregistering a machine.
Licences are limited to activation of two machines at a time.
Options and Settings
In Studio, open Help → Licence Manager. The window contains License Key,
Validate, Unregister, and Close. Runtime license window is available
through Licence in the plugin menu.
Enter a key and select Validate. Studio reports validation success or failure.
Close discards an unsubmitted change to the displayed key. Unregister performs
a machine-unregistration operation; it is not the same as closing the window.
Important Notes
Demo access can have limits. Studio's demo generation limit is 20 nodes;
Runtime can stop a scenario when the demo session time has exceeded
30 minutes of total scenario run time. Consult
the displayed access status when controls are unavailable. Keep license keys
out of shared projects, screenshots, and support attachments.
The 30 minutes of elapsed time while a scenario is
loaded, accumulated within the plugin session. X-Plane pause does not suspend
that budget, and stopping/reloading a scenario does not create a new allowance.
Open, generate, and run
Use File → Open in Studio to open a `.simp` project. Select resources in
the scenario pane or nodes on the canvas to inspect their properties.
File → Save saves authoring changes; File → Generate saves the project
and attempts to produce its Runtime files. Read any System Message errors and
wait for Generation complete before treating the result as ready to run.
Runtime looks beneath the plugin's `scenarios` folder. A runnable scenario uses
a folder and generated files with matching names, for example:
scenarios/
Example/
Example.simp
Example.simc
Example.sims
assets/
The `.simp` file is for editing; Runtime discovers the `.simc`/`.sims` pair.
In the Runtime scenario selector, use Refresh after adding generated files,
select a scenario, and choose Load. The scenario author determines its
starting conditions and subsequent flow.
Studio also provides Generate and Load and Start X-Plane. Generation
and simulator loading are distinct operations: an unsuccessful generation must
be resolved before a new generated scenario can be loaded.
Find your files and outputs
Projects and generated scenarios normally live beneath `scenarios`. Individual
scenario assets can live in that scenario's `assets` folder; shared assets can
live under `scenarios/assets`. Keep referenced aircraft and other X-Plane assets
installed at the paths the scenario expects.
Run outputs are grouped beneath `scenario output`, by scenario and run.
Product diagnostic logs are in `logs`. See [Files and Assets](06-files-assets.md)
for exact naming, purpose, and sharing requirements.
and simulator loading are distinct operations: an unsuccessful generation must
be resolved before a new generated scenario can be loaded.
Find your files and outputs
Projects and generated scenarios normally live beneath `scenarios`. Individual
scenario assets can live in that scenario's `assets` folder; shared assets can
live under `scenarios/assets`. Keep referenced aircraft and other X-Plane assets
installed at the paths the scenario expects.
Run outputs are grouped beneath `scenario output`, by scenario and run.
Product diagnostic logs are in `logs`. See [Files and Assets](06-files-assets.md)
for exact naming, purpose, and sharing requirements.