support

Tip: Include your FSFO logfile in your message for faster help. Your log.txt is located here: Go to FSFO > Click Settings > Click Open User Data Folder (Activation and Simbrief section) > Open UserData Folder.

1) Autopilot

Your FSFO copilot can set airspeed, heading, and altitude for all supported aircraft, except:

• iFly 737 — Cannot set Indicated Airspeed (IAS).

2) FMC/CDU/MCDU Programming

Your FSFO copilot can enter flight-plan and performance data for most aircraft, with these limitations:

• FBW A380 — MCDU entries not supported (no exposed LVARs).
• iniBuilds A350 — MCDU entries not supported (no exposed LVARs).
  ✔ Flight plan can be imported via the EFB’s Import function.
• FSS ERJ — CDU entries not supported (no exposed LVARs).
  ✔ Includes its own copilot option to populate performance data.
• PMDG 737 / 777 / Aerosoft CRJ — Import the flight plan via the EFB before copilot programming.
  ℹ The copilot will confirm that the route was imported prior to CDU programming.

3) Speech Recognition

Requirement: FSFO relies on English phrases and needs at least one English speech recognizer installed.

• Default: Microsoft Speech Recognition API (SAPI) using your system’s default microphone.
• Optional (offline): Vosk — open-source, offline recognition with 20+ languages. FSFO currently includes models for English, French, and German and may add more based on demand.

4) VR Support

• FSFO does not natively support VR and we don’t provide direct VR support at this time.
• You can use FSFO in VR via the third-party tool OpenKneeboard.

5) FSUIPC7 Requirement

FSFO relies on FSUIPC7 (WASM + WAPI) to read/write simulator variables and events.

• Required: FSUIPC7 must be installed, running, and show Connected with LVARs/Events available.
• Compatibility: FSUIPC6/FSX/P3D are not supported for FSFO V6 (MSFS only).
• Permissions: Run FSFO and FSUIPC7 at the same elevation (both as admin, or both standard) to avoid Error #12.
• Verify link: FSFO shows the detected FSUIPC7 version in the lower-left corner before flight.

6) Windows Support (Windows 10 End-of-Life)

• Tested/Recommended: Windows 11.
• Windows 10: Microsoft ends support in October 2025. After that, FSFO will be best-effort on Windows 10; we can’t guarantee compatibility or workarounds for OS-level issues.
• Our guidance: For the most reliable experience (speech packs, drivers, security updates), we recommend upgrading to Windows 11.

7) MSFS & Aircraft Betas (Not Supported)

• FSFO supports the latest public/stable release of MSFS and stable aircraft builds.
• We do not support MSFS Insider/Steam beta branches or aircraft Dev/Experimental/Beta channels.
• Betas frequently change LVAR/HVAR/Event names and behaviors, which can break FSFO profiles and flows.
• If you encounter an issue on a beta, please switch back to the stable release and retest before opening a ticket.
• Compatibility updates follow official releases—not preview or test builds.

Copilot doesn’t move any switches

1. Confirm FSUIPC7 is connected: open the FSUIPC7 tray icon → Show → verify it says Connected and lists LVARs/Events.
2. Confirm FSFO ↔ FSUIPC7 link: before starting a flight, FSFO’s lower-left corner should show the FSUIPC7 version (e.g., 7.5.04).
3. Select the correct aircraft profile: on the Start Flight page, pick the right Aircraft Profile and Checklist; the active profile shows bottom-left after start.

FSUIPC/WASM version mismatch (e.g., “WASM is X, WAPI expects Y”)

1. Close FSFO, MSFS, and FSUIPC7.
2. Download the latest FSUIPC7 package (WASM + WAPI) from the official site.
3. From the ZIPs, copy FSUIPC_WAPID.dll into your FSFO_V6 installation folder (same folder as FSFO_V6.exe).
4. Copy the fsuipc-lvar-module folder into your MSFS Community folder (overwrite when prompted).
5. Restart Windows, then launch MSFS → FSUIPC7 → FSFO in that order.

FSFO Does Not Stay On Top

1. There are two main reasons FSFO may not stay on top:
   • Integrity-level isolation. Windows won’t allow a non-admin (medium-integrity) process to keep its window above an elevated (high-integrity) one.
   • Competing “Always on Top” flags. If another app sets its topmost flag after FSFO, it will override FSFO’s topmost status.
2. Restarting FSFO will reapply its topmost attribute, but it still can’t float above any admin-elevated window unless you run FSFO as administrator (or disable the conflicting app’s “Always on Top”).

FSUIPC Error #12 – FSUIPC_ERR_SENDMSG

FSUIPC7 and FSFO must run at the same permission level.

1. Right-click FSFO_V6.exe → Properties → Compatibility → match “Run as administrator” with FSUIPC7 (both On, or both Off).
2. Do the same for FSUIPC7.exe. Then restart both apps.

Aircraft-specific setup

• FBW A320 / Headwind A330 – MCDU not programming
  Community → fsuipc-lvar-module → open FSUIPC_WASM.ini → set UseAirLocForHvars=Yes → save → restart MSFS.
• Headwind A330 – FCU/MCDU not responding
  Community → fsuipc-lvar-module\modules → copy A320.hvar → rename to A330.hvar → restart MSFS.
• PMDG (737/777) – enable SDK data broadcast
  Users\<You>\AppData\Local\Packages\MicrosoftFlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-738\work\737_options.ini Add: [SDK] EnableDataBroadcast=1

“No English speech recognizer is installed”

1. Windows 11: Settings → Time & language → Language & region → Add a language → choose an English variant (US/UK/AU/IN/CA) → ensure Language pack and Speech are checked → Install → Restart.
2. If English is listed: … → Language options → under Speech, click Download.
3. Windows 10: wording differs slightly—add English and include the Speech component.
4. Re-launch FSFO and confirm an en-* recognizer (e.g., en-US, en-GB) is detected.

Voice recognition – quick checks

1. Mic works? Test with Windows Voice Recorder. If it can’t record, fix mic/permissions first.
2. Permissions: Settings → Privacy & security → Microphone → On (global + “Let desktop apps…”).
3. Correct input: Settings → System → Sound → Input → pick your mic and verify the meter moves.
4. Exclusive mode: Control Panel → Sound → Recording → Mic → Properties → Advanced → uncheck “Allow applications to take exclusive control” (test).
5. Accuracy tuning: If commands are missed, lower Input_VoiceAccuracy from 0.50 → 0.45. If false triggers, raise to 0.55–0.60.
6. Conflicts: Close voice apps/routers (Teams/Discord/Zoom, Voicemeeter, NVIDIA Broadcast, Nahimic, Sonic Studio).
7. Sample rate: Try 44.1k/16-bit or 48k/16-bit in the mic’s Advanced tab; reboot after driver or language-pack changes.

“No microphones found”

• Settings → System → Sound → Input → select your mic and speak (meter should move).
• Settings → Privacy & security → Microphone → turn On both toggles.
• Control Panel → Sound → Recording → right-click mic → Enable → Set as Default. (Optionally uncheck Exclusive Mode while testing.)
• Re-plug or unmute the mic; try a different USB port (USB 2.0 on rear IO preferred for USB mics).

FSFO crashes – what to send

1. Open Event Viewer → Windows Logs → Application.
2. Find the Error that references FSFO.exe. Click Details.
3. Copy the entire details text and email it with a brief description of what you were doing.

Tip: After any change to FSUIPC7, speech packs, or mic settings, fully close FSFO and MSFS, then reboot before re-testing.