Troubleshooting

Common setup, connectivity, and configuration issues for Flight Simulator First Officer (FSFO).

Use this page when something is not working as expected before contacting support.

Unless a section says otherwise, always start programs in this order: MSFS → FSUIPC7 → FSFO.

---

Copilot does not move any switches

This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.

Step 1: Verify FSUIPC7 is connected

• Open the FSUIPC7 tray icon (system tray near the clock).
• Right-click the icon and select Show.
• Confirm FSUIPC7 reports Connected and that LVARs are available.

If LVARs are missing or the menu is disabled, the WASM module is not loaded.

Step 2: Verify FSFO is connected to FSUIPC7

Before starting your flight, FSFO should display the connected FSUIPC7 version in the lower-left corner.

If no version is shown, FSFO is not connected.

Step 3: Confirm aircraft profile selection

On the Start Flight page, ensure the correct Aircraft Profile and Checklist are selected.

After starting the flight, the active aircraft profile appears in the lower-left corner.

Step 4: Reinstall FSUIPC7 if needed

If the steps above fail:

1. Close MSFS, FSFO, and FSUIPC7.
2. Reinstall the latest FSUIPC7 installer over the existing installation.
3. If problems persist, perform a clean FSUIPC7 reinstall:
   1. Uninstall FSUIPC7.
   2. Delete the FSUIPC7 install folder.
   3. Remove the FSUIPC WASM folder from the MSFS Community directory.
   4. Reboot Windows.
   5. Install the latest FSUIPC7 as Administrator.
   6. Allow the WASM module to install when prompted.

After reinstall, start programs in this order:

1. Start MSFS and load into a cockpit.
2. Start FSUIPC7 and confirm it shows Connected.
3. Start FSFO last.

Back to top

---

FSFO does not stay on top

This behavior is caused by Windows process-level restrictions.

Reasons:

• Windows prevents non-admin apps from staying above admin-level apps.
• Another application may re-assert its “Always on Top” flag after FSFO.

Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.

Workaround:

• Run FSFO and FSUIPC7 at the same permission level.
• Or disable Always-On-Top in competing applications.

Back to top

---

FSUIPC Error #12 (FSUIPC_ERR_SENDMSG)

FSFO and FSUIPC7 must run at the same permission level.

1. Right-click FSFO and FSUIPC7.
2. Select Properties → Compatibility.
3. Ensure “Run as administrator” is either enabled for both or disabled for both.
4. Restart both applications.

Back to top

---

FSUIPC Error #2

This error indicates a failed or incomplete FSUIPC connection.

Quick restart sequence

1. Close FSFO, FSUIPC7, and MSFS.
2. Reboot Windows.
3. Start MSFS and load into a cockpit.
4. Start FSUIPC7 (verify only one instance).
5. Start FSFO and click Connect.

Additional checks

• Ensure only one FSUIPC7 instance is running.
• Disable Auto-Connect in FSFO temporarily and connect manually.
• Whitelist FSFO and FSUIPC7 in antivirus or firewall software.

If unresolved, perform a clean FSUIPC7 reinstall.

Back to top

---

WASM version mismatch

Error example: “WASM version X while WAPI expects Y”.

Recommended fix:

• Reinstall the latest FSUIPC7 installer, which includes matching WASM and WAPI components.

Manual fix (advanced users):

1. Copy FSUIPC_WAPID.dll into the FSFO installation folder.
2. Replace the fsuipc-lvar-module folder in the MSFS Community directory.
3. Restart Windows and launch MSFS → FSUIPC7 → FSFO.

Back to top

---

Aircraft-specific issues

FBW A320 or Headwind A330 – MCDU not programming

Edit:

Community\fsuipc-lvar-module\FSUIPC_WASM.ini

Set:

UseAirLocForHvars=Yes

Save and restart MSFS.

Headwind A330 – FCU or MCDU not responding

Copy:

Community\fsuipc-lvar-module\modules\A320.hvar

Rename the copy to:

A330.hvar

Restart MSFS.

PMDG aircraft – enable SDK data broadcast

Edit the aircraft options file and add:

[SDK]
EnableDataBroadcast=1

Save and restart MSFS.

Back to top

---

No English speech recognizer installed

FSFO requires at least one English speech recognizer.

1. Windows Settings → Time & language → Language & region.
2. Add an English language (any variant).
3. Ensure Speech is selected.
4. Restart Windows.

After restart, FSFO should detect an en-* recognizer.

Back to top

---

Voice recognition troubleshooting

Quick checks

• Test your microphone using Windows Voice Recorder.
• Verify microphone permissions are enabled.
• Confirm the correct input device is selected.
• Disable exclusive mode in microphone advanced settings.

Accuracy tuning

• Lower Input_VoiceAccuracy if commands are missed.
• Increase it if false triggers occur.

Known conflicts

Close applications such as Discord, Teams, NVIDIA Broadcast, Voicemeeter, or audio enhancement tools while testing.

Back to top

---

No microphones found

1. Select your microphone in Windows Sound settings and verify input levels.
2. Enable microphone permissions in Privacy settings.
3. Enable and set the mic as default in Control Panel → Sound.
4. Reconnect the microphone or try a different USB port.

Back to top

---

FSFO crashes

When reporting crashes, include Windows Event Viewer logs.

1. Open Event Viewer.
2. Navigate to Windows Logs → Application.
3. Locate the error referencing FSFO.exe.
4. Copy the Details tab contents and send them to support.

Back to top

---

If your issue is not resolved after following the steps above, see Support.