Limitations: Difference between revisions

From FSFO Support Hub
Newer edit →
VisualWikitext
Created page with "= Limitations = Key constraints and setup notes for FSFO features. __NOTOC__ ---- == 1. Autopilot == Your FSFO copilot can set airspeed, heading, and altitude for all supported aircraft, except: * iFly 737: Cannot set Indicated Airspeed (IAS). :contentReference[oaicite:1]{index=1} ---- == 2. FMC, CDU, and MCDU Programming == Your FSFO copilot can enter flight-plan and performance data for most aircraft, with these limitations: === All aircraft === * Copilot do..."
 
No edit summary
Line 1: Line 1:
= Limitations =
= Limitations =


Key constraints and setup notes for FSFO features.
This page documents current functional and platform limitations of Flight Simulator First Officer (FSFO). 
These are not errors, but known constraints based on simulator, aircraft, or platform capabilities.


__NOTOC__
----
 
== Autopilot Control ==
 
FSFO can set airspeed, heading, and altitude on supported aircraft.
 
'''Exception'''
 
* '''iFly 737''' – Indicated Airspeed (IAS) cannot be set by the copilot.


----
----


== 1. Autopilot ==
== FMC / CDU / MCDU Programming ==
 
FSFO can automatically enter route and performance data for most aircraft, with the following limitations.
 
=== General limitations ===
 
* The copilot does '''not''' select SIDs, STARs, or runways.
* You must enter your SimBrief Pilot ID or username in the aircraft EFB/settings so the route can be imported.
 
=== Aircraft without MCDU programming support ===
 
These aircraft do not expose the required simulator variables.
 
* '''FBW A380'''
* '''iniBuilds A350'''
 
You can still import the flight plan using the aircraft’s EFB import function.
 
=== Aircraft without CDU programming support ===
 
* '''FSS ERJ'''
 
This aircraft provides its own internal copilot feature to populate performance data.


Your FSFO copilot can set airspeed, heading, and altitude for all supported aircraft, except:
=== Aircraft that require EFB import first ===


* iFly 737: Cannot set Indicated Airspeed (IAS). :contentReference[oaicite:1]{index=1}
For these aircraft, import the SimBrief flight plan via the EFB before starting FSFO programming.
 
* '''PMDG 737'''
* '''PMDG 777'''
* '''Aerosoft CRJ'''
 
FSFO will confirm the route has been imported before attempting CDU entries.


----
----


== 2. FMC, CDU, and MCDU Programming ==
== Speech Recognition ==
 
FSFO voice control requires an English speech recognizer installed in Windows.
 
* Default engine: '''Microsoft SAPI''' using your default microphone.
* Optional offline engine: '''Vosk''' (experimental).


Your FSFO copilot can enter flight-plan and performance data for most aircraft, with these limitations:
Currently included Vosk languages:
* English
* French
* German


=== All aircraft ===
Vosk is provided as an experimental alternative. 
Officially supported and recommended: Microsoft SAPI (English).


* Copilot does not input SIDs, STARs, or runways (departure or arrival).
----
* Enter your SimBrief Pilot ID or username in the aircraft settings or EFB so the copilot can program the route. :contentReference[oaicite:2]{index=2}


=== Aircraft with no MCDU entry support ===
== VR Support ==


* FBW A380: MCDU entries not supported (no exposed LVARs).
FSFO does not provide native VR rendering.
* iniBuilds A350: MCDU entries not supported (no exposed LVARs).


Flight plan can still be imported via the EFB’s Import function. :contentReference[oaicite:3]{index=3}
You can use FSFO in VR via the third-party tool '''OpenKneeboard'''. 
Because this is external software, compatibility and behavior may vary by system.


=== Aircraft with no CDU entry support ===
----


* FSS ERJ: CDU entries not supported (no exposed LVARs).
== FSUIPC7 Requirement ==


Includes its own copilot option to populate performance data. :contentReference[oaicite:4]{index=4}
FSFO requires '''FSUIPC7''' (including WASM and WAPI components).


=== Aircraft requiring EFB import before copilot programming ===
Requirements:
* FSUIPC7 must be installed and running
* Status must show '''Connected''' with LVARs and Events available
* FSFO will display the detected FSUIPC7 version in the lower-left corner before flight


* PMDG 737, PMDG 777, Aerosoft CRJ: Import the flight plan via the EFB before copilot programming.
Important notes:
* FSFO v6 supports '''MSFS only'''
* '''FSUIPC6, FSX, and P3D are not supported'''
* Run FSFO and FSUIPC7 at the same permission level 
  (both standard user or both administrator) to avoid connection errors


The copilot will confirm the route was imported prior to CDU programming. :contentReference[oaicite:5]{index=5}
If the copilot is not moving switches or data is not updating, verify FSUIPC7 first.


----
----


== 3. Speech Recognition ==
== Windows Version Support ==
 
* Recommended and fully tested: '''Windows 11'''
* Windows 10 reaches end of Microsoft support in '''October 2025'''
 
After that date:
* FSFO on Windows 10 is best-effort only
* OS-level compatibility fixes cannot be guaranteed
 
If remaining on Windows 10:
* Ensure English speech components are installed
* Keep audio and chipset drivers fully up to date
 
Upgrading to Windows 11 is strongly recommended for the most reliable experience.
 
----
 
== MSFS and Aircraft Betas ==
 
FSFO supports only the latest public, stable releases.
 
Not supported:
* MSFS Insider builds
* Steam beta branches
* Aircraft developer or experimental builds
 
Beta versions often change internal simulator variables, which can break FSFO flows and profiles.


FSFO relies on English phrases and requires at least one English speech recognizer installed.
If you encounter an issue while on a beta:
1. Switch back to the stable release
2. Retest the issue
3. Then report it if the problem persists


* Default: Microsoft Speech Recognition API (SAPI) using your system’s default microphone.
Compatibility updates follow official public releases, not preview or test channels.
* Optional (offline): Vosk. FSFO currently includes models for English, French, and German and may*

Revision as of 01:20, 30 January 2026

Limitations

This page documents current functional and platform limitations of Flight Simulator First Officer (FSFO). These are not errors, but known constraints based on simulator, aircraft, or platform capabilities.

Autopilot Control

FSFO can set airspeed, heading, and altitude on supported aircraft.

Exception

  • iFly 737 – Indicated Airspeed (IAS) cannot be set by the copilot.

FMC / CDU / MCDU Programming

FSFO can automatically enter route and performance data for most aircraft, with the following limitations.

General limitations

  • The copilot does not select SIDs, STARs, or runways.
  • You must enter your SimBrief Pilot ID or username in the aircraft EFB/settings so the route can be imported.

Aircraft without MCDU programming support

These aircraft do not expose the required simulator variables.

  • FBW A380
  • iniBuilds A350

You can still import the flight plan using the aircraft’s EFB import function.

Aircraft without CDU programming support

  • FSS ERJ

This aircraft provides its own internal copilot feature to populate performance data.

Aircraft that require EFB import first

For these aircraft, import the SimBrief flight plan via the EFB before starting FSFO programming.

  • PMDG 737
  • PMDG 777
  • Aerosoft CRJ

FSFO will confirm the route has been imported before attempting CDU entries.

Speech Recognition

FSFO voice control requires an English speech recognizer installed in Windows.

  • Default engine: Microsoft SAPI using your default microphone.
  • Optional offline engine: Vosk (experimental).

Currently included Vosk languages:

  • English
  • French
  • German

Vosk is provided as an experimental alternative. Officially supported and recommended: Microsoft SAPI (English).

VR Support

FSFO does not provide native VR rendering.

You can use FSFO in VR via the third-party tool OpenKneeboard. Because this is external software, compatibility and behavior may vary by system.

FSUIPC7 Requirement

FSFO requires FSUIPC7 (including WASM and WAPI components).

Requirements:

  • FSUIPC7 must be installed and running
  • Status must show Connected with LVARs and Events available
  • FSFO will display the detected FSUIPC7 version in the lower-left corner before flight

Important notes:

  • FSFO v6 supports MSFS only
  • FSUIPC6, FSX, and P3D are not supported
  • Run FSFO and FSUIPC7 at the same permission level
 (both standard user or both administrator) to avoid connection errors

If the copilot is not moving switches or data is not updating, verify FSUIPC7 first.

Windows Version Support

  • Recommended and fully tested: Windows 11
  • Windows 10 reaches end of Microsoft support in October 2025

After that date:

  • FSFO on Windows 10 is best-effort only
  • OS-level compatibility fixes cannot be guaranteed

If remaining on Windows 10:

  • Ensure English speech components are installed
  • Keep audio and chipset drivers fully up to date

Upgrading to Windows 11 is strongly recommended for the most reliable experience.

MSFS and Aircraft Betas

FSFO supports only the latest public, stable releases.

Not supported:

  • MSFS Insider builds
  • Steam beta branches
  • Aircraft developer or experimental builds

Beta versions often change internal simulator variables, which can break FSFO flows and profiles.

If you encounter an issue while on a beta: 1. Switch back to the stable release 2. Retest the issue 3. Then report it if the problem persists

Compatibility updates follow official public releases, not preview or test channels.

Retrieved from "https://flightsimfirstofficer.com/wiki/index.php?title=Limitations&oldid=22"