FSFO Support Hub - User contributions [en]

Release Notes

2026-03-28T15:20:43Z

Kingm56: /* Version 6.0.17.0 */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.16.0
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----

== <span>Version 6.1.0.0</span> ==

==== Added ====

* Career Mode Simulation
* Ray Munich's German region pack (it's named German, the default was renamed to German2)
* Wait_For_AGL option
* Wait_For_MSL option.

==== Fixed ====

* Resolved the AGL issue with the User AutoFlows option
* PMDG 737 weather radar not responding to the OFF command
* Fenix A320 incorrectly asking to connect the GPU when the command was to disconnect it while using SAPI
* Missing “Gear Up” callout during takeoff
* Multiple spelling errors on the First Officer and Captain .wav files
* Missing crew (flight attendant) wav files from Ray Munich's regions (sound files)
* User AutoFlow no longer triggers when merely crossing a runway; the aircraft must now be within 800 feet of the runway threshold.
* Lights AutoFlow no longer triggers simply from turning on the landing lights; the aircraft must now be within 800 feet of the runway threshold.
* Reduced runway confirmation distance from 1,500 feet to 750 feet from the runway threshold to reduce false readings.
* Issue where the approach briefing could read non-whole-number values for the approach course.
* Issue where cabin service could start and then stop immediately.
* Issue on the SOPs page where the program could ask you to confirm stopping a flow even when no flow was running.
* IniBuilds A350 Nav light being reported as Off, when it was still On
* RAAS issue where inaccurate "On Taxiway" calls when tailwinds caused IAS to exceed the threshold.
* New Altitude was not set when the aircraft was within 5nm of Top of Descent

==== Changed ====

* Updated the v-speed sync method; registered V-speeds must now be above 100 knots
* Increased the fuel management penalty from 25% to 35%
* On the SOP Controls page, VATSIM and weather information will now be displayed in the Alerts box whenever a checklist or flow is not running.
* Voice command Wipers On will result in a middle vice high setting
* Flight Attendants will now announce they are starting cabin services
* Log Book has been removed; it's now under Career Mode
* There's no more Post Flight Page; you'll now go to the Flight Plan page and click the End Flight button

== <span>Version 6.0.16.0</span> ==

==== Fixed ====

* Erroneous “Fired” message box that appeared at the end of the Shutdown Flow
* Issue where deboarding was announced before shutdown was complete
* Erroneous “Check the Flaps” callout on landing in the Fenix A320
* Issue where user-defined airborne triggers were not working

==== Changed ====

* Brakes are no longer required for the "stabilized" call; however, the Lineup/Takeoff Flow and Checklist must still be completed

== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Default NavData contained the incorrect Runway Heading
* Gear Up was not call on Takeoff
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* GSX Deboarding failed to correctly sync
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)
* Smart/Light Auto Flows - Boarding most also be completed before the Before Start will start

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.
* Checklist/Briefing - Will no longer be on a timer; simply say ready for the checklist or ready for the briefing when ready, press ctrl+alt, or your bypass key

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Career Mode User Guide

2026-03-28T04:24:49Z

Kingm56: /* Schedule Generation */

= FSFO Career Mode User Guide =

This page explains how Career Mode works in FSFO, including pilot progression, schedules, training, scoring, fatigue, and the permanent flight log.

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Career Mode uses a local database to track your pilot profile, your active schedule, and your long-term flight history.
</div>

<span id="top"></span>

__TOC__

----

== Overview ==

Career Mode is built around three main areas:

* '''Pilot Profile'''
Your pilot's name, company, rank, tier, balance, location, type ratings, score, errors, contract legs, and training status

* '''Current Schedule'''
Your active scheduled legs

* '''Flight Log'''
Your permanent flight history and performance record

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#eef3fb; border-left:4px solid #1f4fa3;">
Use Career Mode if you want persistent progression across multiple flights instead of isolated one-off sessions.
</div>

[[#top|Back to top]]

----

== Getting Started ==

To begin using Career Mode:

# Open the '''Career Dashboard'''
# Click '''Rebuild Database''' the first time you use Career Mode
# Enter your pilot name
# Select a company
# Optionally select a type rating
# Click '''Apply Company'''

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c;">
Once accepted, your pilot profile is created and Career Mode begins tracking your progress.
</div>

[[#top|Back to top]]

----

== Career Dashboard ==

The Career Dashboard includes the following major functions:

* '''Rebuild Database'''
Creates or recreates the local career database

* '''Apply Company'''
Applies for a company and creates your pilot profile if needed

* '''Apply Type Rating'''
Starts type-rating training

* '''Generate Schedule'''
Builds your current schedule

* '''Load Stats'''
Refreshes pilot statistics

* '''Save Options'''
Saves career settings

* '''Flight Log'''
Opens the permanent flight history window

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
<strong>NOTE:</strong> The current <strong>Show Contract</strong> button is not implemented yet.
</div>

[[#top|Back to top]]

----

== Career Options ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These options affect how schedules are generated, when flights count toward progression, and whether readiness checks can block a flight.
</div>

* '''Start from last airport'''
Requires you to begin your next career flight from your saved current location. If enabled, FSFO checks that you are within 10 NM of the pilot's stored airport before the flight is considered ready.

* '''Fatal crash starts over'''
If enabled, a fatal crash can end your current career and force you to start over.

* '''Must fly scheduled flight'''
Only credits career progress when you complete the next pending scheduled leg in order. If enabled and you do not fly the correct leg, the flight can still be logged, but it will not advance total legs, average score, balance, rank, or career tier.

* '''Passenger comfort'''
Enables passenger-comfort rules so smoother, better-managed flights matter more to your career results.

* '''Can be fired'''
Enables the career rule that allows poor performance or major failures to put your employment at risk.

* '''Enable fatigue'''
Turns on fatigue tracking. If enabled, FSFO checks recent workload and can block career-flight readiness when fatigue rises above the allowed threshold.

* '''Schedule based on rank'''
Automatically builds schedules using the pilot's current rank and tier to determine the maximum leg distance. If a full schedule cannot be built within that cap, FSFO falls back to the full eligible route set.

* '''Must have type rating'''
Requires the pilot to hold the appropriate type rating before operating aircraft that need one.

* '''Lock schedule until complete'''
Prevents generating a new schedule while an existing schedule still has incomplete legs.

* '''Application based on rank'''
Makes company applications depend on your current rank, including tier eligibility and hiring probability. It also enforces the rejection cooldown for repeat applications.

[[#top|Back to top]]

----

== Companies and Company Tiers ==

Companies are loaded from ''Airlines.cfg''. Each airline has a tier. That tier affects hiring rules, contract leg requirements, and pay scaling.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current contract-leg requirements by company tier:

Tier 1 = 30 legs
Tier 2 = 60 legs
Tier 3 = 90 legs
Tier 4 = 120 legs
Tier 5 = 150 legs
</pre>
</div>

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If you leave a company before satisfying the required legs, Career Mode can apply a contract-break penalty.
</div>

[[#top|Back to top]]

----

== Ranks ==

Career Mode uses a five-rank system:

* '''Rank 1''' - Cadet
* '''Rank 2''' - Second Officer
* '''Rank 3''' - First Officer
* '''Rank 4''' - Captain
* '''Rank 5''' - Senior Captain

Your rank affects:

* the maximum leg distance used in automatic scheduling
* your bidding advantage when schedules are generated
* which companies you can apply to if rank-based hiring is enabled
* your promotion eligibility
* your pay multiplier through Career Tier

[[#top|Back to top]]

----

== How Promotions Work ==

Promotions are based on two things:

* '''Total Legs'''
* '''Average Score'''

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
<strong>Requirement:</strong> Your <strong>Average Score</strong> must be at least <strong>92.0</strong> before any promotion is possible.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
Promotion thresholds:

50 total legs = Second Officer
125 total legs = First Officer
200 total legs = Captain
350 total legs = Senior Captain
</pre>
</div>

If your flight is not credited toward progression, it will not count toward promotion.

[[#top|Back to top]]

----

== Career Tier and Pay ==

Career Tier increases with promotion. Pay is recalculated using a tier multiplier.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
Current pay multipliers:

Tier 1 = 1.00x
Tier 2 = 1.04x
Tier 3 = 1.08x
Tier 4 = 1.12x
Tier 5 = 1.16x
</pre>
</div>

When you are promoted, FSFO updates:

* your rank
* your career tier
* your pay per hour

[[#top|Back to top]]

----

== Company Applications ==

If '''Application based on rank''' is enabled, not every pilot can freely join every airline tier.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current hiring chances:

Cadet
- Tier 1 = 100%

Second Officer
- Tier 1 = 100%
- Tier 2 = 50%

First Officer
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 50%

Captain
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 75%

Senior Captain
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 95%
</pre>
</div>

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If you are rejected by the same company, FSFO enforces a 7-day wait before trying again.
</div>

[[#top|Back to top]]

----

== Type Ratings and Training ==

Use '''Apply Type Rating''' after you have joined a company.

Type rating requests will be blocked if:

* no pilot profile exists
* the pilot is not currently employed by a company
* the pilot is already in training
* the pilot already holds that type rating

Two training paths are available:

* '''Private Training'''
Costs money immediately

* '''Company Training'''
Extends contract legs instead of charging the balance directly

Training duration and costs depend on the type rating group.

[[#top|Back to top]]

----

== Schedule Generation ==

Schedules are built from your route data and filtered by:

* current airline
* rank
* type rating, if type-rating enforcement is enabled
* current location and preferred airport logic

If '''Schedule Based On Rank''' s enabled, FSFO automatically applies a maximum leg distance by rank:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>Rank 1 = 750 NM
Rank 2 = 1500 NM
Rank 3 = 4000 NM
Rank 4 = 8000 NM
Rank 5 = 10000 NM</pre>
</div>

FSFO first tries to build a schedule using that cap. If it cannot build a full schedule, it falls back to the full eligible route pool.

If '''Schedule based on rank''' is disabled, the Max NM value entered by the user is enforced strictly.

If '''Lock schedule until complete''' is enabled, FSFO will not generate a new schedule while an incomplete schedule already exists.

[[#top|Back to top]]

----

== Schedule Bidding System ==

Lets you request specific route segments when generating a Career Mode schedule. Enter your bids in the '''Route Bid''' box using directional airport pairs separated by commas, for example: <code>KBOS-KBGR,KBGR-KDEN</code>. Bids are '''directional only''', so <code>KBOS-KBGR</code> is different from <code>KBGR-KBOS</code>. FSFO applies bids '''in the order entered''', and each bid must maintain schedule continuity — the next bid must depart from the airport where the previous leg ended, otherwise the remaining bid is wasted..

If '''Schedule Based On Rank''' is enabled, each bid leg is awarded based on the pilot’s current rank:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current rank-based bid chances:

Rank 1 = 20%
Rank 2 = 40%
Rank 3 = 60%
Rank 4 = 80%
Rank 5 = 90%
</pre>
</div>

If '''Schedule Based On Rank''' is disabled, FSFO will try to honor the requested bid exactly as entered, but only if it can still build a continuous schedule from the pilot’s current location.

[[#top|Back to top]]

----

== Preferred Airport ==

You can set a preferred airport for a company. FSFO uses that airport when generating schedules and gives preference to routes that end there, especially near the end of a generated trip.

[[#top|Back to top]]

----

== Route Map ==

After a schedule is generated, FSFO can build a route map from the loaded schedule legs and open it externally.

[[#top|Back to top]]

----

== When a Flight Counts Toward Progression ==

A flight does not automatically count toward career progression.

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If <strong>Must fly scheduled flight</strong> is enabled, the flight must complete the <strong>next pending leg in order</strong>.
</div>

FSFO compares:

* the actual flight number
* the actual departure airport
* the actual arrival airport

For the leg to count, the pilot must:

* start at the correct airport
* arrive at the correct airport
* match the next pending scheduled leg

If the flight does not meet that requirement:

* it can still be logged
* it will not increase Total Legs
* it will not update Average Score
* it will not reduce Contract Remaining Legs
* it will not update Balance
* it will not trigger promotion

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c;">
If the next scheduled leg is completed correctly, it is marked <strong>COMPLETED</strong>. If that was the final remaining leg, the schedule is cleared.
</div>

[[#top|Back to top]]

----

== Flying a Career Flight ==

Before flight, FSFO captures:

* company
* flight number
* aircraft
* departure airport
* arrival airport

During flight, Career Mode monitors multiple operational and scoring categories.

Examples include:

* pitch exceedance
* bank exceedance
* G-force exceedance
* IAS exceedance
* taxi-speed exceedance
* light misuse
* fuel-management failures
* landing-performance issues

These events affect the total score and increment the appropriate error counters.

[[#top|Back to top]]

----

== Landing Score ==

Landing Score is based on:

* vertical speed
* G-force
* distance from the runway threshold

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
When runway data is available, the current weighting is:

Vertical speed = 40%
G-force = 30%
Touchdown distance = 30%
</pre>
</div>

If runway threshold data is unavailable, the distance portion is redistributed proportionally between vertical speed and G-force.

[[#top|Back to top]]

----

== Total Score and Qualification ==

Career Mode stores both:

* '''Landing Score'''
* '''Total Score'''

A flight is currently marked '''Qualified for Progression''' when the total score meets the system's qualification rule. The flight log stores that qualification result along with pay, fines, and error counts.

[[#top|Back to top]]

----

== Fatigue ==

If '''Enable fatigue''' is turned on, FSFO calculates fatigue from your recent workload using both:

* number of legs
* block hours

It evaluates three rolling workload windows:

* '''Last 24 hours'''
* '''Last 72 hours'''
* '''Last 7 days'''

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current formula:

Acute Load = max(legs in last 24h / 3.5, block hours in last 24h / 7)
Short Load = max(legs in last 72h / 7, block hours in last 72h / 16)
Weekly Load = max(legs in last 7d / 14, block hours in last 7d / 32)
</pre>
</div>

Each load is clamped from 0 to 1.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>Final fatigue:

Fatigue = (Acute Load × 50) + (Short Load × 30) + (Weekly Load × 20)</pre>
</div>

The result is capped at 100 and rounded to the nearest whole percent.

Career Mode readiness fails if fatigue is greater than or equal to 75%.

[[#top|Back to top]]

----

== Flight Log ==

The Flight Log is the permanent history of your career flights.

Each flight log entry stores:

* date
* company
* flight number
* aircraft
* from airport
* to airport
* block time
* landing score
* total score
* landing rate
* landing G
* block fuel
* critical/configuration/lights/speed error counts
* qualification result
* pay earned
* fines paid

Use the Flight Log window to review your performance over time.

[[#top|Back to top]]

----

== Notes ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Quick reference notes for current Career Mode behavior.
</div>

* Career Mode currently supports one local pilot profile
* The current schedule stores only the active trip
* The flight log is the permanent historical record
* The current '''Show Contract''' button is not implemented yet

[[#top|Back to top]]

----

== Troubleshooting ==

=== "PilotProfile was not found" ===

<div style="margin:0.4em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
Create or rebuild the database, then apply to a company.
</div>

=== No schedule was generated ===

Check that:

* ''routes.csv'' exists
* the file format is valid
* routes match the current airline
* type-rating rules are not filtering everything out
* the requested leg count is realistic for the route pool

=== My flight did not count toward progression ===

If '''Must fly scheduled flight''' is enabled, verify that:

* you flew the next pending leg in order
* you started at the scheduled departure airport
* you arrived at the scheduled arrival airport
* the flight number matched when required

=== I cannot generate a new schedule ===

If '''Lock schedule until complete''' is enabled, finish the current schedule first or turn that option off.

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
For additional setup help, see [[Getting Started]]. For general problem solving, see [[Troubleshooting]].
</div>

[[Category:User Guide]]
[[Category:Career Mode]]

Career Mode User Guide

2026-03-28T03:31:29Z

Kingm56: /* Fatigue */

= FSFO Career Mode User Guide =

This page explains how Career Mode works in FSFO, including pilot progression, schedules, training, scoring, fatigue, and the permanent flight log.

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Career Mode uses a local database to track your pilot profile, your active schedule, and your long-term flight history.
</div>

<span id="top"></span>

__TOC__

----

== Overview ==

Career Mode is built around three main areas:

* '''Pilot Profile'''
Your pilot's name, company, rank, tier, balance, location, type ratings, score, errors, contract legs, and training status

* '''Current Schedule'''
Your active scheduled legs

* '''Flight Log'''
Your permanent flight history and performance record

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#eef3fb; border-left:4px solid #1f4fa3;">
Use Career Mode if you want persistent progression across multiple flights instead of isolated one-off sessions.
</div>

[[#top|Back to top]]

----

== Getting Started ==

To begin using Career Mode:

# Open the '''Career Dashboard'''
# Click '''Rebuild Database''' the first time you use Career Mode
# Enter your pilot name
# Select a company
# Optionally select a type rating
# Click '''Apply Company'''

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c;">
Once accepted, your pilot profile is created and Career Mode begins tracking your progress.
</div>

[[#top|Back to top]]

----

== Career Dashboard ==

The Career Dashboard includes the following major functions:

* '''Rebuild Database'''
Creates or recreates the local career database

* '''Apply Company'''
Applies for a company and creates your pilot profile if needed

* '''Apply Type Rating'''
Starts type-rating training

* '''Generate Schedule'''
Builds your current schedule

* '''Load Stats'''
Refreshes pilot statistics

* '''Save Options'''
Saves career settings

* '''Flight Log'''
Opens the permanent flight history window

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
<strong>NOTE:</strong> The current <strong>Show Contract</strong> button is not implemented yet.
</div>

[[#top|Back to top]]

----

== Career Options ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These options affect how schedules are generated, when flights count toward progression, and whether readiness checks can block a flight.
</div>

* '''Start from last airport'''
Requires you to begin your next career flight from your saved current location. If enabled, FSFO checks that you are within 10 NM of the pilot's stored airport before the flight is considered ready.

* '''Fatal crash starts over'''
If enabled, a fatal crash can end your current career and force you to start over.

* '''Must fly scheduled flight'''
Only credits career progress when you complete the next pending scheduled leg in order. If enabled and you do not fly the correct leg, the flight can still be logged, but it will not advance total legs, average score, balance, rank, or career tier.

* '''Passenger comfort'''
Enables passenger-comfort rules so smoother, better-managed flights matter more to your career results.

* '''Can be fired'''
Enables the career rule that allows poor performance or major failures to put your employment at risk.

* '''Enable fatigue'''
Turns on fatigue tracking. If enabled, FSFO checks recent workload and can block career-flight readiness when fatigue rises above the allowed threshold.

* '''Schedule based on rank'''
Automatically builds schedules using the pilot's current rank and tier to determine the maximum leg distance. If a full schedule cannot be built within that cap, FSFO falls back to the full eligible route set.

* '''Must have type rating'''
Requires the pilot to hold the appropriate type rating before operating aircraft that need one.

* '''Lock schedule until complete'''
Prevents generating a new schedule while an existing schedule still has incomplete legs.

* '''Application based on rank'''
Makes company applications depend on your current rank, including tier eligibility and hiring probability. It also enforces the rejection cooldown for repeat applications.

[[#top|Back to top]]

----

== Companies and Company Tiers ==

Companies are loaded from ''Airlines.cfg''. Each airline has a tier. That tier affects hiring rules, contract leg requirements, and pay scaling.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current contract-leg requirements by company tier:

Tier 1 = 30 legs
Tier 2 = 60 legs
Tier 3 = 90 legs
Tier 4 = 120 legs
Tier 5 = 150 legs
</pre>
</div>

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If you leave a company before satisfying the required legs, Career Mode can apply a contract-break penalty.
</div>

[[#top|Back to top]]

----

== Ranks ==

Career Mode uses a five-rank system:

* '''Rank 1''' - Cadet
* '''Rank 2''' - Second Officer
* '''Rank 3''' - First Officer
* '''Rank 4''' - Captain
* '''Rank 5''' - Senior Captain

Your rank affects:

* the maximum leg distance used in automatic scheduling
* your bidding advantage when schedules are generated
* which companies you can apply to if rank-based hiring is enabled
* your promotion eligibility
* your pay multiplier through Career Tier

[[#top|Back to top]]

----

== How Promotions Work ==

Promotions are based on two things:

* '''Total Legs'''
* '''Average Score'''

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
<strong>Requirement:</strong> Your <strong>Average Score</strong> must be at least <strong>92.0</strong> before any promotion is possible.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
Promotion thresholds:

50 total legs = Second Officer
125 total legs = First Officer
200 total legs = Captain
350 total legs = Senior Captain
</pre>
</div>

If your flight is not credited toward progression, it will not count toward promotion.

[[#top|Back to top]]

----

== Career Tier and Pay ==

Career Tier increases with promotion. Pay is recalculated using a tier multiplier.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
Current pay multipliers:

Tier 1 = 1.00x
Tier 2 = 1.04x
Tier 3 = 1.08x
Tier 4 = 1.12x
Tier 5 = 1.16x
</pre>
</div>

When you are promoted, FSFO updates:

* your rank
* your career tier
* your pay per hour

[[#top|Back to top]]

----

== Company Applications ==

If '''Application based on rank''' is enabled, not every pilot can freely join every airline tier.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current hiring chances:

Cadet
- Tier 1 = 100%

Second Officer
- Tier 1 = 100%
- Tier 2 = 50%

First Officer
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 50%

Captain
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 75%

Senior Captain
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 95%
</pre>
</div>

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If you are rejected by the same company, FSFO enforces a 7-day wait before trying again.
</div>

[[#top|Back to top]]

----

== Type Ratings and Training ==

Use '''Apply Type Rating''' after you have joined a company.

Type rating requests will be blocked if:

* no pilot profile exists
* the pilot is not currently employed by a company
* the pilot is already in training
* the pilot already holds that type rating

Two training paths are available:

* '''Private Training'''
Costs money immediately

* '''Company Training'''
Extends contract legs instead of charging the balance directly

Training duration and costs depend on the type rating group.

[[#top|Back to top]]

----

== Schedule Generation ==

Schedules are built from your route data and filtered by:

* current airline
* rank
* type rating, if type-rating enforcement is enabled
* current location and preferred airport logic

If '''Schedule Based On Rank''' s enabled, FSFO automatically applies a maximum leg distance by rank:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>Rank 1 = 350 NM
Rank 2 = 650 NM
Rank 3 = 1100 NM
Rank 4 = 1800 NM
Rank 5 = 3000 NM</pre>
</div>

FSFO first tries to build a schedule using that cap. If it cannot build a full schedule, it falls back to the full eligible route pool.

If '''Schedule based on rank''' is disabled, the Max NM value entered by the user is enforced strictly.

If '''Lock schedule until complete''' is enabled, FSFO will not generate a new schedule while an incomplete schedule already exists.

[[#top|Back to top]]

----

== Schedule Bidding System ==

Lets you request specific route segments when generating a Career Mode schedule. Enter your bids in the '''Route Bid''' box using directional airport pairs separated by commas, for example: <code>KBOS-KBGR,KBGR-KDEN</code>. Bids are '''directional only''', so <code>KBOS-KBGR</code> is different from <code>KBGR-KBOS</code>. FSFO applies bids '''in the order entered''', and each bid must maintain schedule continuity — the next bid must depart from the airport where the previous leg ended, otherwise the remaining bid is wasted..

If '''Schedule Based On Rank''' is enabled, each bid leg is awarded based on the pilot’s current rank:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current rank-based bid chances:

Rank 1 = 20%
Rank 2 = 40%
Rank 3 = 60%
Rank 4 = 80%
Rank 5 = 90%
</pre>
</div>

If '''Schedule Based On Rank''' is disabled, FSFO will try to honor the requested bid exactly as entered, but only if it can still build a continuous schedule from the pilot’s current location.

[[#top|Back to top]]

----

== Preferred Airport ==

You can set a preferred airport for a company. FSFO uses that airport when generating schedules and gives preference to routes that end there, especially near the end of a generated trip.

[[#top|Back to top]]

----

== Route Map ==

After a schedule is generated, FSFO can build a route map from the loaded schedule legs and open it externally.

[[#top|Back to top]]

----

== When a Flight Counts Toward Progression ==

A flight does not automatically count toward career progression.

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If <strong>Must fly scheduled flight</strong> is enabled, the flight must complete the <strong>next pending leg in order</strong>.
</div>

FSFO compares:

* the actual flight number
* the actual departure airport
* the actual arrival airport

For the leg to count, the pilot must:

* start at the correct airport
* arrive at the correct airport
* match the next pending scheduled leg

If the flight does not meet that requirement:

* it can still be logged
* it will not increase Total Legs
* it will not update Average Score
* it will not reduce Contract Remaining Legs
* it will not update Balance
* it will not trigger promotion

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c;">
If the next scheduled leg is completed correctly, it is marked <strong>COMPLETED</strong>. If that was the final remaining leg, the schedule is cleared.
</div>

[[#top|Back to top]]

----

== Flying a Career Flight ==

Before flight, FSFO captures:

* company
* flight number
* aircraft
* departure airport
* arrival airport

During flight, Career Mode monitors multiple operational and scoring categories.

Examples include:

* pitch exceedance
* bank exceedance
* G-force exceedance
* IAS exceedance
* taxi-speed exceedance
* light misuse
* fuel-management failures
* landing-performance issues

These events affect the total score and increment the appropriate error counters.

[[#top|Back to top]]

----

== Landing Score ==

Landing Score is based on:

* vertical speed
* G-force
* distance from the runway threshold

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
When runway data is available, the current weighting is:

Vertical speed = 40%
G-force = 30%
Touchdown distance = 30%
</pre>
</div>

If runway threshold data is unavailable, the distance portion is redistributed proportionally between vertical speed and G-force.

[[#top|Back to top]]

----

== Total Score and Qualification ==

Career Mode stores both:

* '''Landing Score'''
* '''Total Score'''

A flight is currently marked '''Qualified for Progression''' when the total score meets the system's qualification rule. The flight log stores that qualification result along with pay, fines, and error counts.

[[#top|Back to top]]

----

== Fatigue ==

If '''Enable fatigue''' is turned on, FSFO calculates fatigue from your recent workload using both:

* number of legs
* block hours

It evaluates three rolling workload windows:

* '''Last 24 hours'''
* '''Last 72 hours'''
* '''Last 7 days'''

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current formula:

Acute Load = max(legs in last 24h / 3.5, block hours in last 24h / 7)
Short Load = max(legs in last 72h / 7, block hours in last 72h / 16)
Weekly Load = max(legs in last 7d / 14, block hours in last 7d / 32)
</pre>
</div>

Each load is clamped from 0 to 1.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>Final fatigue:

Fatigue = (Acute Load × 50) + (Short Load × 30) + (Weekly Load × 20)</pre>
</div>

The result is capped at 100 and rounded to the nearest whole percent.

Career Mode readiness fails if fatigue is greater than or equal to 75%.

[[#top|Back to top]]

----

== Flight Log ==

The Flight Log is the permanent history of your career flights.

Each flight log entry stores:

* date
* company
* flight number
* aircraft
* from airport
* to airport
* block time
* landing score
* total score
* landing rate
* landing G
* block fuel
* critical/configuration/lights/speed error counts
* qualification result
* pay earned
* fines paid

Use the Flight Log window to review your performance over time.

[[#top|Back to top]]

----

== Notes ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Quick reference notes for current Career Mode behavior.
</div>

* Career Mode currently supports one local pilot profile
* The current schedule stores only the active trip
* The flight log is the permanent historical record
* The current '''Show Contract''' button is not implemented yet

[[#top|Back to top]]

----

== Troubleshooting ==

=== "PilotProfile was not found" ===

<div style="margin:0.4em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
Create or rebuild the database, then apply to a company.
</div>

=== No schedule was generated ===

Check that:

* ''routes.csv'' exists
* the file format is valid
* routes match the current airline
* type-rating rules are not filtering everything out
* the requested leg count is realistic for the route pool

=== My flight did not count toward progression ===

If '''Must fly scheduled flight''' is enabled, verify that:

* you flew the next pending leg in order
* you started at the scheduled departure airport
* you arrived at the scheduled arrival airport
* the flight number matched when required

=== I cannot generate a new schedule ===

If '''Lock schedule until complete''' is enabled, finish the current schedule first or turn that option off.

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
For additional setup help, see [[Getting Started]]. For general problem solving, see [[Troubleshooting]].
</div>

[[Category:User Guide]]
[[Category:Career Mode]]

Career Mode User Guide

2026-03-28T03:30:49Z

Kingm56: /* Fatigue */

= FSFO Career Mode User Guide =

This page explains how Career Mode works in FSFO, including pilot progression, schedules, training, scoring, fatigue, and the permanent flight log.

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Career Mode uses a local database to track your pilot profile, your active schedule, and your long-term flight history.
</div>

<span id="top"></span>

__TOC__

----

== Overview ==

Career Mode is built around three main areas:

* '''Pilot Profile'''
Your pilot's name, company, rank, tier, balance, location, type ratings, score, errors, contract legs, and training status

* '''Current Schedule'''
Your active scheduled legs

* '''Flight Log'''
Your permanent flight history and performance record

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#eef3fb; border-left:4px solid #1f4fa3;">
Use Career Mode if you want persistent progression across multiple flights instead of isolated one-off sessions.
</div>

[[#top|Back to top]]

----

== Getting Started ==

To begin using Career Mode:

# Open the '''Career Dashboard'''
# Click '''Rebuild Database''' the first time you use Career Mode
# Enter your pilot name
# Select a company
# Optionally select a type rating
# Click '''Apply Company'''

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c;">
Once accepted, your pilot profile is created and Career Mode begins tracking your progress.
</div>

[[#top|Back to top]]

----

== Career Dashboard ==

The Career Dashboard includes the following major functions:

* '''Rebuild Database'''
Creates or recreates the local career database

* '''Apply Company'''
Applies for a company and creates your pilot profile if needed

* '''Apply Type Rating'''
Starts type-rating training

* '''Generate Schedule'''
Builds your current schedule

* '''Load Stats'''
Refreshes pilot statistics

* '''Save Options'''
Saves career settings

* '''Flight Log'''
Opens the permanent flight history window

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
<strong>NOTE:</strong> The current <strong>Show Contract</strong> button is not implemented yet.
</div>

[[#top|Back to top]]

----

== Career Options ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These options affect how schedules are generated, when flights count toward progression, and whether readiness checks can block a flight.
</div>

* '''Start from last airport'''
Requires you to begin your next career flight from your saved current location. If enabled, FSFO checks that you are within 10 NM of the pilot's stored airport before the flight is considered ready.

* '''Fatal crash starts over'''
If enabled, a fatal crash can end your current career and force you to start over.

* '''Must fly scheduled flight'''
Only credits career progress when you complete the next pending scheduled leg in order. If enabled and you do not fly the correct leg, the flight can still be logged, but it will not advance total legs, average score, balance, rank, or career tier.

* '''Passenger comfort'''
Enables passenger-comfort rules so smoother, better-managed flights matter more to your career results.

* '''Can be fired'''
Enables the career rule that allows poor performance or major failures to put your employment at risk.

* '''Enable fatigue'''
Turns on fatigue tracking. If enabled, FSFO checks recent workload and can block career-flight readiness when fatigue rises above the allowed threshold.

* '''Schedule based on rank'''
Automatically builds schedules using the pilot's current rank and tier to determine the maximum leg distance. If a full schedule cannot be built within that cap, FSFO falls back to the full eligible route set.

* '''Must have type rating'''
Requires the pilot to hold the appropriate type rating before operating aircraft that need one.

* '''Lock schedule until complete'''
Prevents generating a new schedule while an existing schedule still has incomplete legs.

* '''Application based on rank'''
Makes company applications depend on your current rank, including tier eligibility and hiring probability. It also enforces the rejection cooldown for repeat applications.

[[#top|Back to top]]

----

== Companies and Company Tiers ==

Companies are loaded from ''Airlines.cfg''. Each airline has a tier. That tier affects hiring rules, contract leg requirements, and pay scaling.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current contract-leg requirements by company tier:

Tier 1 = 30 legs
Tier 2 = 60 legs
Tier 3 = 90 legs
Tier 4 = 120 legs
Tier 5 = 150 legs
</pre>
</div>

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If you leave a company before satisfying the required legs, Career Mode can apply a contract-break penalty.
</div>

[[#top|Back to top]]

----

== Ranks ==

Career Mode uses a five-rank system:

* '''Rank 1''' - Cadet
* '''Rank 2''' - Second Officer
* '''Rank 3''' - First Officer
* '''Rank 4''' - Captain
* '''Rank 5''' - Senior Captain

Your rank affects:

* the maximum leg distance used in automatic scheduling
* your bidding advantage when schedules are generated
* which companies you can apply to if rank-based hiring is enabled
* your promotion eligibility
* your pay multiplier through Career Tier

[[#top|Back to top]]

----

== How Promotions Work ==

Promotions are based on two things:

* '''Total Legs'''
* '''Average Score'''

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
<strong>Requirement:</strong> Your <strong>Average Score</strong> must be at least <strong>92.0</strong> before any promotion is possible.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
Promotion thresholds:

50 total legs = Second Officer
125 total legs = First Officer
200 total legs = Captain
350 total legs = Senior Captain
</pre>
</div>

If your flight is not credited toward progression, it will not count toward promotion.

[[#top|Back to top]]

----

== Career Tier and Pay ==

Career Tier increases with promotion. Pay is recalculated using a tier multiplier.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
Current pay multipliers:

Tier 1 = 1.00x
Tier 2 = 1.04x
Tier 3 = 1.08x
Tier 4 = 1.12x
Tier 5 = 1.16x
</pre>
</div>

When you are promoted, FSFO updates:

* your rank
* your career tier
* your pay per hour

[[#top|Back to top]]

----

== Company Applications ==

If '''Application based on rank''' is enabled, not every pilot can freely join every airline tier.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current hiring chances:

Cadet
- Tier 1 = 100%

Second Officer
- Tier 1 = 100%
- Tier 2 = 50%

First Officer
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 50%

Captain
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 75%

Senior Captain
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 95%
</pre>
</div>

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If you are rejected by the same company, FSFO enforces a 7-day wait before trying again.
</div>

[[#top|Back to top]]

----

== Type Ratings and Training ==

Use '''Apply Type Rating''' after you have joined a company.

Type rating requests will be blocked if:

* no pilot profile exists
* the pilot is not currently employed by a company
* the pilot is already in training
* the pilot already holds that type rating

Two training paths are available:

* '''Private Training'''
Costs money immediately

* '''Company Training'''
Extends contract legs instead of charging the balance directly

Training duration and costs depend on the type rating group.

[[#top|Back to top]]

----

== Schedule Generation ==

Schedules are built from your route data and filtered by:

* current airline
* rank
* type rating, if type-rating enforcement is enabled
* current location and preferred airport logic

If '''Schedule Based On Rank''' s enabled, FSFO automatically applies a maximum leg distance by rank:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>Rank 1 = 350 NM
Rank 2 = 650 NM
Rank 3 = 1100 NM
Rank 4 = 1800 NM
Rank 5 = 3000 NM</pre>
</div>

FSFO first tries to build a schedule using that cap. If it cannot build a full schedule, it falls back to the full eligible route pool.

If '''Schedule based on rank''' is disabled, the Max NM value entered by the user is enforced strictly.

If '''Lock schedule until complete''' is enabled, FSFO will not generate a new schedule while an incomplete schedule already exists.

[[#top|Back to top]]

----

== Schedule Bidding System ==

Lets you request specific route segments when generating a Career Mode schedule. Enter your bids in the '''Route Bid''' box using directional airport pairs separated by commas, for example: <code>KBOS-KBGR,KBGR-KDEN</code>. Bids are '''directional only''', so <code>KBOS-KBGR</code> is different from <code>KBGR-KBOS</code>. FSFO applies bids '''in the order entered''', and each bid must maintain schedule continuity — the next bid must depart from the airport where the previous leg ended, otherwise the remaining bid is wasted..

If '''Schedule Based On Rank''' is enabled, each bid leg is awarded based on the pilot’s current rank:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current rank-based bid chances:

Rank 1 = 20%
Rank 2 = 40%
Rank 3 = 60%
Rank 4 = 80%
Rank 5 = 90%
</pre>
</div>

If '''Schedule Based On Rank''' is disabled, FSFO will try to honor the requested bid exactly as entered, but only if it can still build a continuous schedule from the pilot’s current location.

[[#top|Back to top]]

----

== Preferred Airport ==

You can set a preferred airport for a company. FSFO uses that airport when generating schedules and gives preference to routes that end there, especially near the end of a generated trip.

[[#top|Back to top]]

----

== Route Map ==

After a schedule is generated, FSFO can build a route map from the loaded schedule legs and open it externally.

[[#top|Back to top]]

----

== When a Flight Counts Toward Progression ==

A flight does not automatically count toward career progression.

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If <strong>Must fly scheduled flight</strong> is enabled, the flight must complete the <strong>next pending leg in order</strong>.
</div>

FSFO compares:

* the actual flight number
* the actual departure airport
* the actual arrival airport

For the leg to count, the pilot must:

* start at the correct airport
* arrive at the correct airport
* match the next pending scheduled leg

If the flight does not meet that requirement:

* it can still be logged
* it will not increase Total Legs
* it will not update Average Score
* it will not reduce Contract Remaining Legs
* it will not update Balance
* it will not trigger promotion

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c;">
If the next scheduled leg is completed correctly, it is marked <strong>COMPLETED</strong>. If that was the final remaining leg, the schedule is cleared.
</div>

[[#top|Back to top]]

----

== Flying a Career Flight ==

Before flight, FSFO captures:

* company
* flight number
* aircraft
* departure airport
* arrival airport

During flight, Career Mode monitors multiple operational and scoring categories.

Examples include:

* pitch exceedance
* bank exceedance
* G-force exceedance
* IAS exceedance
* taxi-speed exceedance
* light misuse
* fuel-management failures
* landing-performance issues

These events affect the total score and increment the appropriate error counters.

[[#top|Back to top]]

----

== Landing Score ==

Landing Score is based on:

* vertical speed
* G-force
* distance from the runway threshold

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
When runway data is available, the current weighting is:

Vertical speed = 40%
G-force = 30%
Touchdown distance = 30%
</pre>
</div>

If runway threshold data is unavailable, the distance portion is redistributed proportionally between vertical speed and G-force.

[[#top|Back to top]]

----

== Total Score and Qualification ==

Career Mode stores both:

* '''Landing Score'''
* '''Total Score'''

A flight is currently marked '''Qualified for Progression''' when the total score meets the system's qualification rule. The flight log stores that qualification result along with pay, fines, and error counts.

[[#top|Back to top]]

----

== Fatigue ==

If '''Enable fatigue''' is turned on, FSFO calculates fatigue from your recent workload using both:

* number of legs
* block hours

It evaluates three rolling workload windows:

* '''Last 24 hours'''
* '''Last 72 hours'''
* '''Last 7 days'''

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current formula:

Acute Load = max(legs in last 24h / 3.5, block hours in last 24h / 7)
Short Load = max(legs in last 72h / 7, block hours in last 72h / 16)
Weekly Load = max(legs in last 7d / 14, block hours in last 7d / 32)
</pre>
</div>

Each load is clamped from 0 to 1.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>Final fatigue:

Fatigue = (Acute Load × 50) + (Short Load × 30) + (Weekly Load × 20)</pre>
</div>

The result is capped at 100 and rounded to the nearest whole percent.

If fatigue is above the allowed limit, Career Mode readiness should fail until workload decreases.

[[#top|Back to top]]

----

== Flight Log ==

The Flight Log is the permanent history of your career flights.

Each flight log entry stores:

* date
* company
* flight number
* aircraft
* from airport
* to airport
* block time
* landing score
* total score
* landing rate
* landing G
* block fuel
* critical/configuration/lights/speed error counts
* qualification result
* pay earned
* fines paid

Use the Flight Log window to review your performance over time.

[[#top|Back to top]]

----

== Notes ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Quick reference notes for current Career Mode behavior.
</div>

* Career Mode currently supports one local pilot profile
* The current schedule stores only the active trip
* The flight log is the permanent historical record
* The current '''Show Contract''' button is not implemented yet

[[#top|Back to top]]

----

== Troubleshooting ==

=== "PilotProfile was not found" ===

<div style="margin:0.4em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
Create or rebuild the database, then apply to a company.
</div>

=== No schedule was generated ===

Check that:

* ''routes.csv'' exists
* the file format is valid
* routes match the current airline
* type-rating rules are not filtering everything out
* the requested leg count is realistic for the route pool

=== My flight did not count toward progression ===

If '''Must fly scheduled flight''' is enabled, verify that:

* you flew the next pending leg in order
* you started at the scheduled departure airport
* you arrived at the scheduled arrival airport
* the flight number matched when required

=== I cannot generate a new schedule ===

If '''Lock schedule until complete''' is enabled, finish the current schedule first or turn that option off.

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
For additional setup help, see [[Getting Started]]. For general problem solving, see [[Troubleshooting]].
</div>

[[Category:User Guide]]
[[Category:Career Mode]]

Career Mode User Guide

2026-03-27T15:06:42Z

Kingm56: /* Schedule Generation */

= FSFO Career Mode User Guide =

This page explains how Career Mode works in FSFO, including pilot progression, schedules, training, scoring, fatigue, and the permanent flight log.

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Career Mode uses a local database to track your pilot profile, your active schedule, and your long-term flight history.
</div>

<span id="top"></span>

__TOC__

----

== Overview ==

Career Mode is built around three main areas:

* '''Pilot Profile'''
Your pilot's name, company, rank, tier, balance, location, type ratings, score, errors, contract legs, and training status

* '''Current Schedule'''
Your active scheduled legs

* '''Flight Log'''
Your permanent flight history and performance record

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#eef3fb; border-left:4px solid #1f4fa3;">
Use Career Mode if you want persistent progression across multiple flights instead of isolated one-off sessions.
</div>

[[#top|Back to top]]

----

== Getting Started ==

To begin using Career Mode:

# Open the '''Career Dashboard'''
# Click '''Rebuild Database''' the first time you use Career Mode
# Enter your pilot name
# Select a company
# Optionally select a type rating
# Click '''Apply Company'''

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c;">
Once accepted, your pilot profile is created and Career Mode begins tracking your progress.
</div>

[[#top|Back to top]]

----

== Career Dashboard ==

The Career Dashboard includes the following major functions:

* '''Rebuild Database'''
Creates or recreates the local career database

* '''Apply Company'''
Applies for a company and creates your pilot profile if needed

* '''Apply Type Rating'''
Starts type-rating training

* '''Generate Schedule'''
Builds your current schedule

* '''Load Stats'''
Refreshes pilot statistics

* '''Save Options'''
Saves career settings

* '''Flight Log'''
Opens the permanent flight history window

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
<strong>NOTE:</strong> The current <strong>Show Contract</strong> button is not implemented yet.
</div>

[[#top|Back to top]]

----

== Career Options ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These options affect how schedules are generated, when flights count toward progression, and whether readiness checks can block a flight.
</div>

* '''Start from last airport'''
Requires you to begin your next career flight from your saved current location. If enabled, FSFO checks that you are within 10 NM of the pilot's stored airport before the flight is considered ready.

* '''Fatal crash starts over'''
If enabled, a fatal crash can end your current career and force you to start over.

* '''Must fly scheduled flight'''
Only credits career progress when you complete the next pending scheduled leg in order. If enabled and you do not fly the correct leg, the flight can still be logged, but it will not advance total legs, average score, balance, rank, or career tier.

* '''Passenger comfort'''
Enables passenger-comfort rules so smoother, better-managed flights matter more to your career results.

* '''Can be fired'''
Enables the career rule that allows poor performance or major failures to put your employment at risk.

* '''Enable fatigue'''
Turns on fatigue tracking. If enabled, FSFO checks recent workload and can block career-flight readiness when fatigue rises above the allowed threshold.

* '''Schedule based on rank'''
Automatically builds schedules using the pilot's current rank and tier to determine the maximum leg distance. If a full schedule cannot be built within that cap, FSFO falls back to the full eligible route set.

* '''Must have type rating'''
Requires the pilot to hold the appropriate type rating before operating aircraft that need one.

* '''Lock schedule until complete'''
Prevents generating a new schedule while an existing schedule still has incomplete legs.

* '''Application based on rank'''
Makes company applications depend on your current rank, including tier eligibility and hiring probability. It also enforces the rejection cooldown for repeat applications.

[[#top|Back to top]]

----

== Companies and Company Tiers ==

Companies are loaded from ''Airlines.cfg''. Each airline has a tier. That tier affects hiring rules, contract leg requirements, and pay scaling.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current contract-leg requirements by company tier:

Tier 1 = 30 legs
Tier 2 = 60 legs
Tier 3 = 90 legs
Tier 4 = 120 legs
Tier 5 = 150 legs
</pre>
</div>

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If you leave a company before satisfying the required legs, Career Mode can apply a contract-break penalty.
</div>

[[#top|Back to top]]

----

== Ranks ==

Career Mode uses a five-rank system:

* '''Rank 1''' - Cadet
* '''Rank 2''' - Second Officer
* '''Rank 3''' - First Officer
* '''Rank 4''' - Captain
* '''Rank 5''' - Senior Captain

Your rank affects:

* the maximum leg distance used in automatic scheduling
* your bidding advantage when schedules are generated
* which companies you can apply to if rank-based hiring is enabled
* your promotion eligibility
* your pay multiplier through Career Tier

[[#top|Back to top]]

----

== How Promotions Work ==

Promotions are based on two things:

* '''Total Legs'''
* '''Average Score'''

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
<strong>Requirement:</strong> Your <strong>Average Score</strong> must be at least <strong>92.0</strong> before any promotion is possible.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
Promotion thresholds:

50 total legs = Second Officer
125 total legs = First Officer
200 total legs = Captain
350 total legs = Senior Captain
</pre>
</div>

If your flight is not credited toward progression, it will not count toward promotion.

[[#top|Back to top]]

----

== Career Tier and Pay ==

Career Tier increases with promotion. Pay is recalculated using a tier multiplier.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
Current pay multipliers:

Tier 1 = 1.00x
Tier 2 = 1.04x
Tier 3 = 1.08x
Tier 4 = 1.12x
Tier 5 = 1.16x
</pre>
</div>

When you are promoted, FSFO updates:

* your rank
* your career tier
* your pay per hour

[[#top|Back to top]]

----

== Company Applications ==

If '''Application based on rank''' is enabled, not every pilot can freely join every airline tier.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current hiring chances:

Cadet
- Tier 1 = 100%

Second Officer
- Tier 1 = 100%
- Tier 2 = 50%

First Officer
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 50%

Captain
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 75%

Senior Captain
- Tier 1 = 100%
- Tier 2 = 100%
- Tier 3 = 95%
</pre>
</div>

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If you are rejected by the same company, FSFO enforces a 7-day wait before trying again.
</div>

[[#top|Back to top]]

----

== Type Ratings and Training ==

Use '''Apply Type Rating''' after you have joined a company.

Type rating requests will be blocked if:

* no pilot profile exists
* the pilot is not currently employed by a company
* the pilot is already in training
* the pilot already holds that type rating

Two training paths are available:

* '''Private Training'''
Costs money immediately

* '''Company Training'''
Extends contract legs instead of charging the balance directly

Training duration and costs depend on the type rating group.

[[#top|Back to top]]

----

== Schedule Generation ==

Schedules are built from your route data and filtered by:

* current airline
* rank
* type rating, if type-rating enforcement is enabled
* current location and preferred airport logic

If '''Schedule Based On Rank''' s enabled, FSFO automatically applies a maximum leg distance by rank:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>Rank 1 = 350 NM
Rank 2 = 650 NM
Rank 3 = 1100 NM
Rank 4 = 1800 NM
Rank 5 = 3000 NM</pre>
</div>

FSFO first tries to build a schedule using that cap. If it cannot build a full schedule, it falls back to the full eligible route pool.

If '''Schedule based on rank''' is disabled, the Max NM value entered by the user is enforced strictly.

If '''Lock schedule until complete''' is enabled, FSFO will not generate a new schedule while an incomplete schedule already exists.

[[#top|Back to top]]

----

== Schedule Bidding System ==

Lets you request specific route segments when generating a Career Mode schedule. Enter your bids in the '''Route Bid''' box using directional airport pairs separated by commas, for example: <code>KBOS-KBGR,KBGR-KDEN</code>. Bids are '''directional only''', so <code>KBOS-KBGR</code> is different from <code>KBGR-KBOS</code>. FSFO applies bids '''in the order entered''', and each bid must maintain schedule continuity — the next bid must depart from the airport where the previous leg ended, otherwise the remaining bid is wasted..

If '''Schedule Based On Rank''' is enabled, each bid leg is awarded based on the pilot’s current rank:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current rank-based bid chances:

Rank 1 = 20%
Rank 2 = 40%
Rank 3 = 60%
Rank 4 = 80%
Rank 5 = 90%
</pre>
</div>

If '''Schedule Based On Rank''' is disabled, FSFO will try to honor the requested bid exactly as entered, but only if it can still build a continuous schedule from the pilot’s current location.

[[#top|Back to top]]

----

== Preferred Airport ==

You can set a preferred airport for a company. FSFO uses that airport when generating schedules and gives preference to routes that end there, especially near the end of a generated trip.

[[#top|Back to top]]

----

== Route Map ==

After a schedule is generated, FSFO can build a route map from the loaded schedule legs and open it externally.

[[#top|Back to top]]

----

== When a Flight Counts Toward Progression ==

A flight does not automatically count toward career progression.

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
If <strong>Must fly scheduled flight</strong> is enabled, the flight must complete the <strong>next pending leg in order</strong>.
</div>

FSFO compares:

* the actual flight number
* the actual departure airport
* the actual arrival airport

For the leg to count, the pilot must:

* start at the correct airport
* arrive at the correct airport
* match the next pending scheduled leg

If the flight does not meet that requirement:

* it can still be logged
* it will not increase Total Legs
* it will not update Average Score
* it will not reduce Contract Remaining Legs
* it will not update Balance
* it will not trigger promotion

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c;">
If the next scheduled leg is completed correctly, it is marked <strong>COMPLETED</strong>. If that was the final remaining leg, the schedule is cleared.
</div>

[[#top|Back to top]]

----

== Flying a Career Flight ==

Before flight, FSFO captures:

* company
* flight number
* aircraft
* departure airport
* arrival airport

During flight, Career Mode monitors multiple operational and scoring categories.

Examples include:

* pitch exceedance
* bank exceedance
* G-force exceedance
* IAS exceedance
* taxi-speed exceedance
* light misuse
* fuel-management failures
* landing-performance issues

These events affect the total score and increment the appropriate error counters.

[[#top|Back to top]]

----

== Landing Score ==

Landing Score is based on:

* vertical speed
* G-force
* distance from the runway threshold

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
When runway data is available, the current weighting is:

Vertical speed = 40%
G-force = 30%
Touchdown distance = 30%
</pre>
</div>

If runway threshold data is unavailable, the distance portion is redistributed proportionally between vertical speed and G-force.

[[#top|Back to top]]

----

== Total Score and Qualification ==

Career Mode stores both:

* '''Landing Score'''
* '''Total Score'''

A flight is currently marked '''Qualified for Progression''' when the total score meets the system's qualification rule. The flight log stores that qualification result along with pay, fines, and error counts.

[[#top|Back to top]]

----

== Fatigue ==

If '''Enable fatigue''' is turned on, FSFO calculates fatigue from your recent workload using both:

* number of legs
* block hours

It evaluates three rolling workload windows:

* '''Last 24 hours'''
* '''Last 72 hours'''
* '''Last 7 days'''

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
Current formula:

Acute Load = max(legs in last 24h / 4, block hours in last 24h / 8)
Short Load = max(legs in last 72h / 8, block hours in last 72h / 18)
Weekly Load = max(legs in last 7d / 16, block hours in last 7d / 35)
</pre>
</div>

Each load is clamped from 0 to 1.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
Final fatigue:

Fatigue = (Acute Load × 50) + (Short Load × 30) + (Weekly Load × 20)
</pre>
</div>

The result is capped at 100 and rounded to the nearest whole percent.

If fatigue is above the allowed limit, Career Mode readiness should fail until workload decreases.

[[#top|Back to top]]

----

== Flight Log ==

The Flight Log is the permanent history of your career flights.

Each flight log entry stores:

* date
* company
* flight number
* aircraft
* from airport
* to airport
* block time
* landing score
* total score
* landing rate
* landing G
* block fuel
* critical/configuration/lights/speed error counts
* qualification result
* pay earned
* fines paid

Use the Flight Log window to review your performance over time.

[[#top|Back to top]]

----

== Notes ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Quick reference notes for current Career Mode behavior.
</div>

* Career Mode currently supports one local pilot profile
* The current schedule stores only the active trip
* The flight log is the permanent historical record
* The current '''Show Contract''' button is not implemented yet

[[#top|Back to top]]

----

== Troubleshooting ==

=== "PilotProfile was not found" ===

<div style="margin:0.4em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
Create or rebuild the database, then apply to a company.
</div>

=== No schedule was generated ===

Check that:

* ''routes.csv'' exists
* the file format is valid
* routes match the current airline
* type-rating rules are not filtering everything out
* the requested leg count is realistic for the route pool

=== My flight did not count toward progression ===

If '''Must fly scheduled flight''' is enabled, verify that:

* you flew the next pending leg in order
* you started at the scheduled departure airport
* you arrived at the scheduled arrival airport
* the flight number matched when required

=== I cannot generate a new schedule ===

If '''Lock schedule until complete''' is enabled, finish the current schedule first or turn that option off.

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
For additional setup help, see [[Getting Started]]. For general problem solving, see [[Troubleshooting]].
</div>

[[Category:User Guide]]
[[Category:Career Mode]]

Troubleshooting

2026-03-26T17:10:54Z

Kingm56: /* Step 5: Reinstall FSUIPC7 if needed */

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

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this page when something is not working as expected before contacting support.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Unless a section says otherwise, always start programs in this order: <strong>MSFS → FSUIPC7 → FSFO</strong>.
</div>

<span id="top"></span>
----

== Copilot does not move any switches ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.
</div>

=== 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.

[[File:FSUIPC7_Connected_Lvars.png|600x600px|FSUIPC7 showing connected state and available LVARs]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If the LVARs are missing (0 Lvars); please go to Step 4

If the menu is disabled (WASM is missing), please go to Step 5
</div>

=== Step 2: Verify FSFO is connected to FSUIPC7 ===

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

[[File:FSFO_FSUIPC_Status.png|450x450px|FSFO showing FSUIPC7 version in the status bar]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If no version is shown, FSFO is not connected.
</div>

=== 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.

[[File:FSFO_Aircraft_Profile.png|450x450px|Aircraft profile selection on Start Flight page]]

=== Step 4: LVARs fail to load: ===

# Make sure MSFS is fully loaded into the cockpit before starting FSFO.
# Confirm FSUIPC7 shows Connected to the simulator (step 1).
# If you are using a complex aircraft, give it extra time to finish loading its systems.
# Start FSFO '''AFTER''' FSUIPC7 is already connected.
# If the issue continues, close everything and restart in this order:
## Start MSFS and load into the cockpit.
## Start FSUIPC7 and confirm it shows Connected WITH LVARS LOADED (step 1) .
## Start FSFO last.

If the LVARs still do not load, adjust the FSUIPC WASM scan settings (last resort):

# Close MSFS, FSUIPC7, and FSFO.
# Open the FSUIPC_WASM.ini file in the WASM persistence/work folder.
# Do not edit the copy in the Community folder.
# Set the following values:
## LvarScanDelay=15 //Increase as needed...start with 15
## LvarScanFrequency=0

After saving the file, restart in this order:

# Start MSFS and load into the cockpit.
# Start FSUIPC7 and confirm it shows Connected.
# Start FSFO last.

LVARs still fail to load, check whether the FSUIPC WASM module crashed (move to step 5)
What these edits do:

* LvarScanDelay=15 gives the aircraft more time to finish initializing before FSUIPC scans for LVARs.
* LvarScanFrequency=0 disables repeated rescans, which can help if the WASM is unstable or LVARs stop updating.

=== Step 5: Reinstall FSUIPC7 if needed ===

If the steps above fail:

# Close MSFS, FSFO, and FSUIPC7.
# Reinstall the latest FSUIPC7 installer over the existing installation.
# If problems persist, perform a clean FSUIPC7 reinstall:
## Uninstall FSUIPC7.
## Delete the FSUIPC7 install folder.
### This is the directory you installed FSUIPC7.
## Remove the FSUIPC WASM folder from the MSFS Community directory.
### *\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\fsuipc-lvar-module
## Reboot Windows.
## Download the latest FSUIPC7 from here: https://fsuipc.com/fsuipc7/
## Unzip and Install the FSUIPC7.
### Right-Click Install_FSUIPC7.exe and select "Run as administrator."
### Ensure you select the sims you use - MSFS2020 and/or MSFS2024 (see picture below)
### Ensure the WASM module is selected (see picture below)!

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
After reinstall, start programs in this order:
<ol>
<li>Start MSFS and load into a cockpit.</li>
<li>Start FSUIPC7 and confirm it shows Connected.</li>
<li>Start FSFO last.</li>
</ol>
</div>
[[File:Fsuipc7Setup.png|center|thumb|800x800px]]

[[Troubleshooting#top|Back to top]]
----

== FSFO does not stay on top ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This behavior is caused by Windows process-level restrictions.
</div>

Reasons:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.
</div>

Workaround:

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #12 (FSUIPC_ERR_SENDMSG) ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
FSFO and FSUIPC7 must run at the same permission level.
</div>

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #2 ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This error indicates a failed or incomplete FSUIPC connection.
</div>

=== Common Cause ===

* FSUIPC7 is not running
* More than one FSUIPC7 instance is open
* Antivirus or firewall is blocking communication
* FSUIPC7 was installed in a protected folder
* FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

=== Quick Restart Sequence ===

# Close FSFO, FSUIPC7, and MSFS.
# Reboot Windows.
# Start MSFS and load fully into a cockpit.
# Start FSUIPC7 and confirm it is running.
# Start FSFO and click Connect.

=== Additional Checks ===

# Ensure only one instance of FSUIPC7 is running (review your system tray).
# Disable Auto-Connect in FSFO temporarily and connect manually.
# Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
# Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

=== Installation Checks ===

* Do not install FSUIPC7 inside Program Files or other protected Windows folders.
* Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
* If needed, reinstall FSUIPC7 and then restart the PC.
* After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
* If unresolved, perform a clean FSUIPC7 reinstall.

[[Troubleshooting#top|Back to top]]
----

== WASM version mismatch ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Error example: “WASM version X while WAPI expects Y”.
</div>

Recommended fix:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Manual fix (advanced users):
</div>

# Close FSFO, MSFS and FSUIPC7
# Go to www.fsuipc.com
# Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
# Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
# Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
# Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
# Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

[[Troubleshooting#top|Back to top]]
----

== <big>Aircraft-specific issues</big> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These issues apply only to specific aircraft or families.
</div>

=== FBW A320 or Headwind A330 – MCDU not programming ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Edit:
<pre>
Community\fsuipc-lvar-module\FSUIPC_WASM.ini
</pre>
Set:
<pre>
UseAirLocForHvars=Yes
</pre>
Save and restart MSFS.
</div>

----

=== Headwind A330 – FCU or MCDU not responding ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Copy:
<pre>
Community\fsuipc-lvar-module\modules\A320.hvar
</pre>
Rename the copy to:
<pre>
A330.hvar
</pre>
Restart MSFS.
</div>

----

=== PMDG aircraft – Enable SDK Data Broadcast ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<strong>Important:</strong> The aircraft must be loaded past the <strong>Ready to Fly</strong> screen at least once before these files exist.
</div>

# Exit Microsoft Flight Simulator.
# Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

==== MSFS 2020 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

==== MSFS 2024 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

# Open the <code>{aircraft_name}_Options.ini</code> file in a text editor such as Notepad.
# Add the following lines to the very end of the file:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
</pre>
</div>

# Save the file and restart Microsoft Flight Simulator.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
''Where <code>{username}</code> is your Windows username and <code>{aircraft_name}</code> is the specific PMDG aircraft you are using (for example, <code>737</code>).''
</div>

[[Troubleshooting#top|Back to top]]
----

== No English speech recognizer installed ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.
</div>

If English is not installed:

# Open Settings > Time & language > Language & region.
# Click Add a language.
# Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
# Select the English language > Next.
# Ensure Language pack and Speech are checked → Install.
# Restart Windows.

After restart, FSFO should detect an <code>en-*</code> recognizer.

If English is already listed or installed:

# Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
# Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

[[Troubleshooting#top|Back to top]]
----

== Voice recognition troubleshooting ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this section for microphone, permissions, and recognition accuracy problems.
</div>

'''Basic Checks:'''
* Microphone works?
** Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

* Privacy permissions (Windows 11):
** Settings > Privacy & security > Microphone
*** Microphone access: On
*** Let desktop apps access your microphone: On

* Correct input device
** Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

* No “exclusive mode” lock
** Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
*** Uncheck Allow applications to take exclusive control (as a test)

* Reasonable gain
** In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

'''English Speech Pack Installed (required):'''
* FSFO relies on English phrases. At least one English speech recognizer must be installed.
** Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
** Your Windows display language can be anything; only the English speech component is required.

'''Accuracy Tuning'''
* Lower <code>Input_VoiceAccuracy</code> if commands are missed.
* Increase it if false triggers occur.
* To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

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

[[Troubleshooting#top|Back to top]]
----

== No microphones found ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use these steps if FSFO shows no available input devices.
</div>

* '''Confirm Windows can see your mic'''
** Windows Settings > System > Sound > Input
** Select your microphone under Choose a device for speaking or recording
** Speak and verify the input level meter moves.
* '''Allow microphone permissions'''
** Windows Settings > Privacy & security > Microphone
** Turn ON:
*** Microphone access
*** Let apps access your microphone
*** Let desktop apps access your microphone
* '''Enable it in Control Panel (and set default)'''
** Open Control Panel > Sound > Recording
** Right-click your microphone > Enable
** Right-click it again > Set as Default Device
** (Optional) Set as Default Communication Device too.
* '''Basic Hardware Checks'''
** Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
** Unplug and replug, try a different USB port (avoid hubs while testing).
** If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

[[Troubleshooting#top|Back to top]]
----

== FSFO crashes ==

[[File:EventView.png|left|thumb|186x186px]]

<div style="margin-left:200px; margin-bottom:0.6em; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>When reporting crashes, include Windows Event Viewer logs.</strong>
</div>

# Type Event Viewer in the Windows Search Bar
# Click on the Event Viewer App
# Expand Windows Log > Expand Application
# Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
# Click The Details Tab, Copy and Email the contents to support

[[Troubleshooting#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
If your issue is not resolved after following the steps above, see [[Support]].
</div>

Troubleshooting

2026-03-26T17:05:52Z

Kingm56: /* Step 3: Confirm aircraft profile selection */

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

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this page when something is not working as expected before contacting support.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Unless a section says otherwise, always start programs in this order: <strong>MSFS → FSUIPC7 → FSFO</strong>.
</div>

<span id="top"></span>
----

== Copilot does not move any switches ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.
</div>

=== 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.

[[File:FSUIPC7_Connected_Lvars.png|600x600px|FSUIPC7 showing connected state and available LVARs]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If the LVARs are missing (0 Lvars); please go to Step 4

If the menu is disabled (WASM is missing), please go to Step 5
</div>

=== Step 2: Verify FSFO is connected to FSUIPC7 ===

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

[[File:FSFO_FSUIPC_Status.png|450x450px|FSFO showing FSUIPC7 version in the status bar]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If no version is shown, FSFO is not connected.
</div>

=== 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.

[[File:FSFO_Aircraft_Profile.png|450x450px|Aircraft profile selection on Start Flight page]]

=== Step 4: LVARs fail to load: ===

# Make sure MSFS is fully loaded into the cockpit before starting FSFO.
# Confirm FSUIPC7 shows Connected to the simulator (step 1).
# If you are using a complex aircraft, give it extra time to finish loading its systems.
# Start FSFO '''AFTER''' FSUIPC7 is already connected.
# If the issue continues, close everything and restart in this order:
## Start MSFS and load into the cockpit.
## Start FSUIPC7 and confirm it shows Connected WITH LVARS LOADED (step 1) .
## Start FSFO last.

If the LVARs still do not load, adjust the FSUIPC WASM scan settings (last resort):

# Close MSFS, FSUIPC7, and FSFO.
# Open the FSUIPC_WASM.ini file in the WASM persistence/work folder.
# Do not edit the copy in the Community folder.
# Set the following values:
## LvarScanDelay=15 //Increase as needed...start with 15
## LvarScanFrequency=0

After saving the file, restart in this order:

# Start MSFS and load into the cockpit.
# Start FSUIPC7 and confirm it shows Connected.
# Start FSFO last.

LVARs still fail to load, check whether the FSUIPC WASM module crashed (move to step 5)
What these edits do:

* LvarScanDelay=15 gives the aircraft more time to finish initializing before FSUIPC scans for LVARs.
* LvarScanFrequency=0 disables repeated rescans, which can help if the WASM is unstable or LVARs stop updating.

=== Step 5: Reinstall FSUIPC7 if needed ===

If the steps above fail:

# Close MSFS, FSFO, and FSUIPC7.
# Reinstall the latest FSUIPC7 installer over the existing installation.
# If problems persist, perform a clean FSUIPC7 reinstall:
## Uninstall FSUIPC7.
## Delete the FSUIPC7 install folder.
## Remove the FSUIPC WASM folder from the MSFS Community directory.
## Reboot Windows.
## Download the latest FSUIPC7 from here: https://fsuipc.com/fsuipc7/
## Unzip and Install the FSUIPC7 as Administrator.
### Right-Click Install_FSUIPC7.exe and select "Run as administrator."
### Ensure you select the sims you use - MSFS2020 and/or MSFS2024 (see picture below)
### Ensure the WASM module is selected (see picture below)!

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
After reinstall, start programs in this order:
<ol>
<li>Start MSFS and load into a cockpit.</li>
<li>Start FSUIPC7 and confirm it shows Connected.</li>
<li>Start FSFO last.</li>
</ol>
</div>
[[File:Fsuipc7Setup.png|center|thumb|800x800px]]

[[Troubleshooting#top|Back to top]]
----

== FSFO does not stay on top ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This behavior is caused by Windows process-level restrictions.
</div>

Reasons:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.
</div>

Workaround:

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #12 (FSUIPC_ERR_SENDMSG) ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
FSFO and FSUIPC7 must run at the same permission level.
</div>

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #2 ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This error indicates a failed or incomplete FSUIPC connection.
</div>

=== Common Cause ===

* FSUIPC7 is not running
* More than one FSUIPC7 instance is open
* Antivirus or firewall is blocking communication
* FSUIPC7 was installed in a protected folder
* FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

=== Quick Restart Sequence ===

# Close FSFO, FSUIPC7, and MSFS.
# Reboot Windows.
# Start MSFS and load fully into a cockpit.
# Start FSUIPC7 and confirm it is running.
# Start FSFO and click Connect.

=== Additional Checks ===

# Ensure only one instance of FSUIPC7 is running (review your system tray).
# Disable Auto-Connect in FSFO temporarily and connect manually.
# Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
# Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

=== Installation Checks ===

* Do not install FSUIPC7 inside Program Files or other protected Windows folders.
* Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
* If needed, reinstall FSUIPC7 and then restart the PC.
* After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
* If unresolved, perform a clean FSUIPC7 reinstall.

[[Troubleshooting#top|Back to top]]
----

== WASM version mismatch ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Error example: “WASM version X while WAPI expects Y”.
</div>

Recommended fix:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Manual fix (advanced users):
</div>

# Close FSFO, MSFS and FSUIPC7
# Go to www.fsuipc.com
# Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
# Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
# Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
# Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
# Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

[[Troubleshooting#top|Back to top]]
----

== <big>Aircraft-specific issues</big> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These issues apply only to specific aircraft or families.
</div>

=== FBW A320 or Headwind A330 – MCDU not programming ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Edit:
<pre>
Community\fsuipc-lvar-module\FSUIPC_WASM.ini
</pre>
Set:
<pre>
UseAirLocForHvars=Yes
</pre>
Save and restart MSFS.
</div>

----

=== Headwind A330 – FCU or MCDU not responding ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Copy:
<pre>
Community\fsuipc-lvar-module\modules\A320.hvar
</pre>
Rename the copy to:
<pre>
A330.hvar
</pre>
Restart MSFS.
</div>

----

=== PMDG aircraft – Enable SDK Data Broadcast ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<strong>Important:</strong> The aircraft must be loaded past the <strong>Ready to Fly</strong> screen at least once before these files exist.
</div>

# Exit Microsoft Flight Simulator.
# Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

==== MSFS 2020 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

==== MSFS 2024 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

# Open the <code>{aircraft_name}_Options.ini</code> file in a text editor such as Notepad.
# Add the following lines to the very end of the file:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
</pre>
</div>

# Save the file and restart Microsoft Flight Simulator.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
''Where <code>{username}</code> is your Windows username and <code>{aircraft_name}</code> is the specific PMDG aircraft you are using (for example, <code>737</code>).''
</div>

[[Troubleshooting#top|Back to top]]
----

== No English speech recognizer installed ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.
</div>

If English is not installed:

# Open Settings > Time & language > Language & region.
# Click Add a language.
# Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
# Select the English language > Next.
# Ensure Language pack and Speech are checked → Install.
# Restart Windows.

After restart, FSFO should detect an <code>en-*</code> recognizer.

If English is already listed or installed:

# Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
# Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

[[Troubleshooting#top|Back to top]]
----

== Voice recognition troubleshooting ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this section for microphone, permissions, and recognition accuracy problems.
</div>

'''Basic Checks:'''
* Microphone works?
** Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

* Privacy permissions (Windows 11):
** Settings > Privacy & security > Microphone
*** Microphone access: On
*** Let desktop apps access your microphone: On

* Correct input device
** Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

* No “exclusive mode” lock
** Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
*** Uncheck Allow applications to take exclusive control (as a test)

* Reasonable gain
** In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

'''English Speech Pack Installed (required):'''
* FSFO relies on English phrases. At least one English speech recognizer must be installed.
** Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
** Your Windows display language can be anything; only the English speech component is required.

'''Accuracy Tuning'''
* Lower <code>Input_VoiceAccuracy</code> if commands are missed.
* Increase it if false triggers occur.
* To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

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

[[Troubleshooting#top|Back to top]]
----

== No microphones found ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use these steps if FSFO shows no available input devices.
</div>

* '''Confirm Windows can see your mic'''
** Windows Settings > System > Sound > Input
** Select your microphone under Choose a device for speaking or recording
** Speak and verify the input level meter moves.
* '''Allow microphone permissions'''
** Windows Settings > Privacy & security > Microphone
** Turn ON:
*** Microphone access
*** Let apps access your microphone
*** Let desktop apps access your microphone
* '''Enable it in Control Panel (and set default)'''
** Open Control Panel > Sound > Recording
** Right-click your microphone > Enable
** Right-click it again > Set as Default Device
** (Optional) Set as Default Communication Device too.
* '''Basic Hardware Checks'''
** Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
** Unplug and replug, try a different USB port (avoid hubs while testing).
** If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

[[Troubleshooting#top|Back to top]]
----

== FSFO crashes ==

[[File:EventView.png|left|thumb|186x186px]]

<div style="margin-left:200px; margin-bottom:0.6em; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>When reporting crashes, include Windows Event Viewer logs.</strong>
</div>

# Type Event Viewer in the Windows Search Bar
# Click on the Event Viewer App
# Expand Windows Log > Expand Application
# Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
# Click The Details Tab, Copy and Email the contents to support

[[Troubleshooting#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
If your issue is not resolved after following the steps above, see [[Support]].
</div>

Troubleshooting

2026-03-26T17:05:26Z

Kingm56: /* Step 3: Confirm aircraft profile selection */

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

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this page when something is not working as expected before contacting support.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Unless a section says otherwise, always start programs in this order: <strong>MSFS → FSUIPC7 → FSFO</strong>.
</div>

<span id="top"></span>
----

== Copilot does not move any switches ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.
</div>

=== 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.

[[File:FSUIPC7_Connected_Lvars.png|600x600px|FSUIPC7 showing connected state and available LVARs]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If the LVARs are missing (0 Lvars); please go to Step 4

If the menu is disabled (WASM is missing), please go to Step 5
</div>

=== Step 2: Verify FSFO is connected to FSUIPC7 ===

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

[[File:FSFO_FSUIPC_Status.png|450x450px|FSFO showing FSUIPC7 version in the status bar]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If no version is shown, FSFO is not connected.
</div>

=== 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.

[[File:FSFO_Aircraft_Profile.png|450x450px|Aircraft profile selection on Start Flight page]]

=== Step 4: LVARs fail to load: ===

# Make sure MSFS is fully loaded into the cockpit before starting FSFO.
# Confirm FSUIPC7 shows Connected to the simulator (step 1).
# If you are using a complex aircraft, give it extra time to finish loading its systems.
# Start FSFO '''AFTER''' FSUIPC7 is already connected.
# If the issue continues, close everything and restart in this order:
## Start MSFS and load into the cockpit.
## Start FSUIPC7 and confirm it shows Connected WITH LVARS LOADED (step 1) .
## Start FSFO last.

If the LVARs still do not load, adjust the FSUIPC WASM scan settings (last resort):

# Close MSFS, FSUIPC7, and FSFO.
# Open the FSUIPC_WASM.ini file in the WASM persistence/work folder.
# Do not edit the copy in the Community folder.
# Set the following values:
## LvarScanDelay=15 //Increase as needed...start with 15
## LvarScanFrequency=0

After saving the file, restart in this order:

# Start MSFS and load into the cockpit.
# Start FSUIPC7 and confirm it shows Connected.
# Start FSFO last.

LVARs still fail to load, check whether the FSUIPC WASM module crashed (move to step 5)
What these edits do:

* LvarScanDelay=15 gives the aircraft more time to finish initializing before FSUIPC scans for LVARs.
* LvarScanFrequency=0 disables repeated rescans, which can help if the WASM is unstable or LVARs stop updating.

=== Step 5: Reinstall FSUIPC7 if needed ===

If the steps above fail:

# Close MSFS, FSFO, and FSUIPC7.
# Reinstall the latest FSUIPC7 installer over the existing installation.
# If problems persist, perform a clean FSUIPC7 reinstall:
## Uninstall FSUIPC7.
## Delete the FSUIPC7 install folder.
## Remove the FSUIPC WASM folder from the MSFS Community directory.
## Reboot Windows.
## Download the latest FSUIPC7 from here: https://fsuipc.com/fsuipc7/
## Unzip and Install the FSUIPC7 as Administrator.
### Right-Click Install_FSUIPC7.exe and select "Run as administrator."
### Ensure you select the sims you use - MSFS2020 and/or MSFS2024 (see picture below)
### Ensure the WASM module is selected (see picture below)!

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
After reinstall, start programs in this order:
<ol>
<li>Start MSFS and load into a cockpit.</li>
<li>Start FSUIPC7 and confirm it shows Connected.</li>
<li>Start FSFO last.</li>
</ol>
</div>
[[File:Fsuipc7Setup.png|center|thumb|600x600px]]

[[Troubleshooting#top|Back to top]]
----

== FSFO does not stay on top ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This behavior is caused by Windows process-level restrictions.
</div>

Reasons:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.
</div>

Workaround:

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #12 (FSUIPC_ERR_SENDMSG) ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
FSFO and FSUIPC7 must run at the same permission level.
</div>

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #2 ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This error indicates a failed or incomplete FSUIPC connection.
</div>

=== Common Cause ===

* FSUIPC7 is not running
* More than one FSUIPC7 instance is open
* Antivirus or firewall is blocking communication
* FSUIPC7 was installed in a protected folder
* FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

=== Quick Restart Sequence ===

# Close FSFO, FSUIPC7, and MSFS.
# Reboot Windows.
# Start MSFS and load fully into a cockpit.
# Start FSUIPC7 and confirm it is running.
# Start FSFO and click Connect.

=== Additional Checks ===

# Ensure only one instance of FSUIPC7 is running (review your system tray).
# Disable Auto-Connect in FSFO temporarily and connect manually.
# Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
# Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

=== Installation Checks ===

* Do not install FSUIPC7 inside Program Files or other protected Windows folders.
* Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
* If needed, reinstall FSUIPC7 and then restart the PC.
* After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
* If unresolved, perform a clean FSUIPC7 reinstall.

[[Troubleshooting#top|Back to top]]
----

== WASM version mismatch ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Error example: “WASM version X while WAPI expects Y”.
</div>

Recommended fix:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Manual fix (advanced users):
</div>

# Close FSFO, MSFS and FSUIPC7
# Go to www.fsuipc.com
# Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
# Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
# Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
# Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
# Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

[[Troubleshooting#top|Back to top]]
----

== <big>Aircraft-specific issues</big> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These issues apply only to specific aircraft or families.
</div>

=== FBW A320 or Headwind A330 – MCDU not programming ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Edit:
<pre>
Community\fsuipc-lvar-module\FSUIPC_WASM.ini
</pre>
Set:
<pre>
UseAirLocForHvars=Yes
</pre>
Save and restart MSFS.
</div>

----

=== Headwind A330 – FCU or MCDU not responding ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Copy:
<pre>
Community\fsuipc-lvar-module\modules\A320.hvar
</pre>
Rename the copy to:
<pre>
A330.hvar
</pre>
Restart MSFS.
</div>

----

=== PMDG aircraft – Enable SDK Data Broadcast ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<strong>Important:</strong> The aircraft must be loaded past the <strong>Ready to Fly</strong> screen at least once before these files exist.
</div>

# Exit Microsoft Flight Simulator.
# Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

==== MSFS 2020 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

==== MSFS 2024 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

# Open the <code>{aircraft_name}_Options.ini</code> file in a text editor such as Notepad.
# Add the following lines to the very end of the file:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
</pre>
</div>

# Save the file and restart Microsoft Flight Simulator.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
''Where <code>{username}</code> is your Windows username and <code>{aircraft_name}</code> is the specific PMDG aircraft you are using (for example, <code>737</code>).''
</div>

[[Troubleshooting#top|Back to top]]
----

== No English speech recognizer installed ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.
</div>

If English is not installed:

# Open Settings > Time & language > Language & region.
# Click Add a language.
# Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
# Select the English language > Next.
# Ensure Language pack and Speech are checked → Install.
# Restart Windows.

After restart, FSFO should detect an <code>en-*</code> recognizer.

If English is already listed or installed:

# Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
# Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

[[Troubleshooting#top|Back to top]]
----

== Voice recognition troubleshooting ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this section for microphone, permissions, and recognition accuracy problems.
</div>

'''Basic Checks:'''
* Microphone works?
** Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

* Privacy permissions (Windows 11):
** Settings > Privacy & security > Microphone
*** Microphone access: On
*** Let desktop apps access your microphone: On

* Correct input device
** Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

* No “exclusive mode” lock
** Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
*** Uncheck Allow applications to take exclusive control (as a test)

* Reasonable gain
** In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

'''English Speech Pack Installed (required):'''
* FSFO relies on English phrases. At least one English speech recognizer must be installed.
** Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
** Your Windows display language can be anything; only the English speech component is required.

'''Accuracy Tuning'''
* Lower <code>Input_VoiceAccuracy</code> if commands are missed.
* Increase it if false triggers occur.
* To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

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

[[Troubleshooting#top|Back to top]]
----

== No microphones found ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use these steps if FSFO shows no available input devices.
</div>

* '''Confirm Windows can see your mic'''
** Windows Settings > System > Sound > Input
** Select your microphone under Choose a device for speaking or recording
** Speak and verify the input level meter moves.
* '''Allow microphone permissions'''
** Windows Settings > Privacy & security > Microphone
** Turn ON:
*** Microphone access
*** Let apps access your microphone
*** Let desktop apps access your microphone
* '''Enable it in Control Panel (and set default)'''
** Open Control Panel > Sound > Recording
** Right-click your microphone > Enable
** Right-click it again > Set as Default Device
** (Optional) Set as Default Communication Device too.
* '''Basic Hardware Checks'''
** Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
** Unplug and replug, try a different USB port (avoid hubs while testing).
** If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

[[Troubleshooting#top|Back to top]]
----

== FSFO crashes ==

[[File:EventView.png|left|thumb|186x186px]]

<div style="margin-left:200px; margin-bottom:0.6em; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>When reporting crashes, include Windows Event Viewer logs.</strong>
</div>

# Type Event Viewer in the Windows Search Bar
# Click on the Event Viewer App
# Expand Windows Log > Expand Application
# Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
# Click The Details Tab, Copy and Email the contents to support

[[Troubleshooting#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
If your issue is not resolved after following the steps above, see [[Support]].
</div>

Troubleshooting

2026-03-26T17:04:37Z

Kingm56: /* Step 5: Reinstall FSUIPC7 if needed */

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

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this page when something is not working as expected before contacting support.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Unless a section says otherwise, always start programs in this order: <strong>MSFS → FSUIPC7 → FSFO</strong>.
</div>

<span id="top"></span>
----

== Copilot does not move any switches ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.
</div>

=== 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.

[[File:FSUIPC7_Connected_Lvars.png|600x600px|FSUIPC7 showing connected state and available LVARs]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If the LVARs are missing (0 Lvars); please go to Step 4

If the menu is disabled (WASM is missing), please go to Step 5
</div>

=== Step 2: Verify FSFO is connected to FSUIPC7 ===

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

[[File:FSFO_FSUIPC_Status.png|450x450px|FSFO showing FSUIPC7 version in the status bar]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If no version is shown, FSFO is not connected.
</div>

=== 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.

[[File:FSFO_Aircraft_Profile.png|450x450px|Aircraft profile selection on Start Flight page]]

=== Step 4: LVARs fail to load: ===

# Make sure MSFS is fully loaded into the cockpit before starting FSFO.
# Confirm FSUIPC7 shows Connected to the simulator (step 1).
# If you are using a complex aircraft, give it extra time to finish loading its systems.
# Start FSFO '''AFTER''' FSUIPC7 is already connected.
# If the issue continues, close everything and restart in this order:
## Start MSFS and load into the cockpit.
## Start FSUIPC7 and confirm it shows Connected WITH LVARS LOADED (step 1) .
## Start FSFO last.

If the LVARs still do not load, adjust the FSUIPC WASM scan settings (last resort):

# Close MSFS, FSUIPC7, and FSFO.
# Open the FSUIPC_WASM.ini file in the WASM persistence/work folder.
# Do not edit the copy in the Community folder.
# Set the following values:
## LvarScanDelay=15 //Increase as needed...start with 15
## LvarScanFrequency=0

After saving the file, restart in this order:

# Start MSFS and load into the cockpit.
# Start FSUIPC7 and confirm it shows Connected.
# Start FSFO last.

LVARs still fail to load, check whether the FSUIPC WASM module crashed (move to step 5)
What these edits do:

* LvarScanDelay=15 gives the aircraft more time to finish initializing before FSUIPC scans for LVARs.
* LvarScanFrequency=0 disables repeated rescans, which can help if the WASM is unstable or LVARs stop updating.

=== Step 5: Reinstall FSUIPC7 if needed ===

If the steps above fail:

# Close MSFS, FSFO, and FSUIPC7.
# Reinstall the latest FSUIPC7 installer over the existing installation.
# If problems persist, perform a clean FSUIPC7 reinstall:
## Uninstall FSUIPC7.
## Delete the FSUIPC7 install folder.
## Remove the FSUIPC WASM folder from the MSFS Community directory.
## Reboot Windows.
## Download the latest FSUIPC7 from here: https://fsuipc.com/fsuipc7/
## Unzip and Install the FSUIPC7 as Administrator.
### Right-Click Install_FSUIPC7.exe and select "Run as administrator."
### Ensure you select the sims you use - MSFS2020 and/or MSFS2024 (see picture below)
### Ensure the WASM module is selected (see picture below)!

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
After reinstall, start programs in this order:
<ol>
<li>Start MSFS and load into a cockpit.</li>
<li>Start FSUIPC7 and confirm it shows Connected.</li>
<li>Start FSFO last.</li>
</ol>
</div>
[[File:Fsuipc7Setup.png|center|thumb]]

[[Troubleshooting#top|Back to top]]
----

== FSFO does not stay on top ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This behavior is caused by Windows process-level restrictions.
</div>

Reasons:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.
</div>

Workaround:

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #12 (FSUIPC_ERR_SENDMSG) ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
FSFO and FSUIPC7 must run at the same permission level.
</div>

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #2 ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This error indicates a failed or incomplete FSUIPC connection.
</div>

=== Common Cause ===

* FSUIPC7 is not running
* More than one FSUIPC7 instance is open
* Antivirus or firewall is blocking communication
* FSUIPC7 was installed in a protected folder
* FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

=== Quick Restart Sequence ===

# Close FSFO, FSUIPC7, and MSFS.
# Reboot Windows.
# Start MSFS and load fully into a cockpit.
# Start FSUIPC7 and confirm it is running.
# Start FSFO and click Connect.

=== Additional Checks ===

# Ensure only one instance of FSUIPC7 is running (review your system tray).
# Disable Auto-Connect in FSFO temporarily and connect manually.
# Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
# Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

=== Installation Checks ===

* Do not install FSUIPC7 inside Program Files or other protected Windows folders.
* Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
* If needed, reinstall FSUIPC7 and then restart the PC.
* After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
* If unresolved, perform a clean FSUIPC7 reinstall.

[[Troubleshooting#top|Back to top]]
----

== WASM version mismatch ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Error example: “WASM version X while WAPI expects Y”.
</div>

Recommended fix:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Manual fix (advanced users):
</div>

# Close FSFO, MSFS and FSUIPC7
# Go to www.fsuipc.com
# Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
# Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
# Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
# Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
# Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

[[Troubleshooting#top|Back to top]]
----

== <big>Aircraft-specific issues</big> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These issues apply only to specific aircraft or families.
</div>

=== FBW A320 or Headwind A330 – MCDU not programming ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Edit:
<pre>
Community\fsuipc-lvar-module\FSUIPC_WASM.ini
</pre>
Set:
<pre>
UseAirLocForHvars=Yes
</pre>
Save and restart MSFS.
</div>

----

=== Headwind A330 – FCU or MCDU not responding ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Copy:
<pre>
Community\fsuipc-lvar-module\modules\A320.hvar
</pre>
Rename the copy to:
<pre>
A330.hvar
</pre>
Restart MSFS.
</div>

----

=== PMDG aircraft – Enable SDK Data Broadcast ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<strong>Important:</strong> The aircraft must be loaded past the <strong>Ready to Fly</strong> screen at least once before these files exist.
</div>

# Exit Microsoft Flight Simulator.
# Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

==== MSFS 2020 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

==== MSFS 2024 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

# Open the <code>{aircraft_name}_Options.ini</code> file in a text editor such as Notepad.
# Add the following lines to the very end of the file:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
</pre>
</div>

# Save the file and restart Microsoft Flight Simulator.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
''Where <code>{username}</code> is your Windows username and <code>{aircraft_name}</code> is the specific PMDG aircraft you are using (for example, <code>737</code>).''
</div>

[[Troubleshooting#top|Back to top]]
----

== No English speech recognizer installed ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.
</div>

If English is not installed:

# Open Settings > Time & language > Language & region.
# Click Add a language.
# Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
# Select the English language > Next.
# Ensure Language pack and Speech are checked → Install.
# Restart Windows.

After restart, FSFO should detect an <code>en-*</code> recognizer.

If English is already listed or installed:

# Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
# Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

[[Troubleshooting#top|Back to top]]
----

== Voice recognition troubleshooting ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this section for microphone, permissions, and recognition accuracy problems.
</div>

'''Basic Checks:'''
* Microphone works?
** Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

* Privacy permissions (Windows 11):
** Settings > Privacy & security > Microphone
*** Microphone access: On
*** Let desktop apps access your microphone: On

* Correct input device
** Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

* No “exclusive mode” lock
** Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
*** Uncheck Allow applications to take exclusive control (as a test)

* Reasonable gain
** In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

'''English Speech Pack Installed (required):'''
* FSFO relies on English phrases. At least one English speech recognizer must be installed.
** Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
** Your Windows display language can be anything; only the English speech component is required.

'''Accuracy Tuning'''
* Lower <code>Input_VoiceAccuracy</code> if commands are missed.
* Increase it if false triggers occur.
* To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

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

[[Troubleshooting#top|Back to top]]
----

== No microphones found ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use these steps if FSFO shows no available input devices.
</div>

* '''Confirm Windows can see your mic'''
** Windows Settings > System > Sound > Input
** Select your microphone under Choose a device for speaking or recording
** Speak and verify the input level meter moves.
* '''Allow microphone permissions'''
** Windows Settings > Privacy & security > Microphone
** Turn ON:
*** Microphone access
*** Let apps access your microphone
*** Let desktop apps access your microphone
* '''Enable it in Control Panel (and set default)'''
** Open Control Panel > Sound > Recording
** Right-click your microphone > Enable
** Right-click it again > Set as Default Device
** (Optional) Set as Default Communication Device too.
* '''Basic Hardware Checks'''
** Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
** Unplug and replug, try a different USB port (avoid hubs while testing).
** If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

[[Troubleshooting#top|Back to top]]
----

== FSFO crashes ==

[[File:EventView.png|left|thumb|186x186px]]

<div style="margin-left:200px; margin-bottom:0.6em; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>When reporting crashes, include Windows Event Viewer logs.</strong>
</div>

# Type Event Viewer in the Windows Search Bar
# Click on the Event Viewer App
# Expand Windows Log > Expand Application
# Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
# Click The Details Tab, Copy and Email the contents to support

[[Troubleshooting#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
If your issue is not resolved after following the steps above, see [[Support]].
</div>

File:Fsuipc7Setup.png

2026-03-26T17:04:17Z

Kingm56:

FSUIPC7 Setup

Troubleshooting

2026-03-26T17:02:00Z

Kingm56: /* Step 5: Reinstall FSUIPC7 if needed */

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

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this page when something is not working as expected before contacting support.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Unless a section says otherwise, always start programs in this order: <strong>MSFS → FSUIPC7 → FSFO</strong>.
</div>

<span id="top"></span>
----

== Copilot does not move any switches ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.
</div>

=== 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.

[[File:FSUIPC7_Connected_Lvars.png|600x600px|FSUIPC7 showing connected state and available LVARs]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If the LVARs are missing (0 Lvars); please go to Step 4

If the menu is disabled (WASM is missing), please go to Step 5
</div>

=== Step 2: Verify FSFO is connected to FSUIPC7 ===

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

[[File:FSFO_FSUIPC_Status.png|450x450px|FSFO showing FSUIPC7 version in the status bar]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If no version is shown, FSFO is not connected.
</div>

=== 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.

[[File:FSFO_Aircraft_Profile.png|450x450px|Aircraft profile selection on Start Flight page]]

=== Step 4: LVARs fail to load: ===

# Make sure MSFS is fully loaded into the cockpit before starting FSFO.
# Confirm FSUIPC7 shows Connected to the simulator (step 1).
# If you are using a complex aircraft, give it extra time to finish loading its systems.
# Start FSFO '''AFTER''' FSUIPC7 is already connected.
# If the issue continues, close everything and restart in this order:
## Start MSFS and load into the cockpit.
## Start FSUIPC7 and confirm it shows Connected WITH LVARS LOADED (step 1) .
## Start FSFO last.

If the LVARs still do not load, adjust the FSUIPC WASM scan settings (last resort):

# Close MSFS, FSUIPC7, and FSFO.
# Open the FSUIPC_WASM.ini file in the WASM persistence/work folder.
# Do not edit the copy in the Community folder.
# Set the following values:
## LvarScanDelay=15 //Increase as needed...start with 15
## LvarScanFrequency=0

After saving the file, restart in this order:

# Start MSFS and load into the cockpit.
# Start FSUIPC7 and confirm it shows Connected.
# Start FSFO last.

LVARs still fail to load, check whether the FSUIPC WASM module crashed (move to step 5)
What these edits do:

* LvarScanDelay=15 gives the aircraft more time to finish initializing before FSUIPC scans for LVARs.
* LvarScanFrequency=0 disables repeated rescans, which can help if the WASM is unstable or LVARs stop updating.

=== Step 5: Reinstall FSUIPC7 if needed ===

If the steps above fail:

# Close MSFS, FSFO, and FSUIPC7.
# Reinstall the latest FSUIPC7 installer over the existing installation.
# If problems persist, perform a clean FSUIPC7 reinstall:
## Uninstall FSUIPC7.
## Delete the FSUIPC7 install folder.
## Remove the FSUIPC WASM folder from the MSFS Community directory.
## Reboot Windows.
## Download the latest FSUIPC7 from here: https://fsuipc.com/fsuipc7/
## Unzip and Install the FSUIPC7 as Administrator.
### Right-Click Install_FSUIPC7.exe and select "Run as administrator."
### Ensure you select the sims you use - MSFS2020 and/or MSFS2024 (see picture below)
### Ensure the WASM module is selected (see picture below)!

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
After reinstall, start programs in this order:
<ol>
<li>Start MSFS and load into a cockpit.</li>
<li>Start FSUIPC7 and confirm it shows Connected.</li>
<li>Start FSFO last.</li>
</ol>
</div>
[[File:Select The Correct Sims.png|left|thumb]]

[[File:Setup2.png|left|thumb]]

[[Troubleshooting#top|Back to top]]
----

== FSFO does not stay on top ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This behavior is caused by Windows process-level restrictions.
</div>

Reasons:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.
</div>

Workaround:

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #12 (FSUIPC_ERR_SENDMSG) ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
FSFO and FSUIPC7 must run at the same permission level.
</div>

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #2 ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This error indicates a failed or incomplete FSUIPC connection.
</div>

=== Common Cause ===

* FSUIPC7 is not running
* More than one FSUIPC7 instance is open
* Antivirus or firewall is blocking communication
* FSUIPC7 was installed in a protected folder
* FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

=== Quick Restart Sequence ===

# Close FSFO, FSUIPC7, and MSFS.
# Reboot Windows.
# Start MSFS and load fully into a cockpit.
# Start FSUIPC7 and confirm it is running.
# Start FSFO and click Connect.

=== Additional Checks ===

# Ensure only one instance of FSUIPC7 is running (review your system tray).
# Disable Auto-Connect in FSFO temporarily and connect manually.
# Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
# Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

=== Installation Checks ===

* Do not install FSUIPC7 inside Program Files or other protected Windows folders.
* Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
* If needed, reinstall FSUIPC7 and then restart the PC.
* After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
* If unresolved, perform a clean FSUIPC7 reinstall.

[[Troubleshooting#top|Back to top]]
----

== WASM version mismatch ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Error example: “WASM version X while WAPI expects Y”.
</div>

Recommended fix:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Manual fix (advanced users):
</div>

# Close FSFO, MSFS and FSUIPC7
# Go to www.fsuipc.com
# Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
# Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
# Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
# Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
# Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

[[Troubleshooting#top|Back to top]]
----

== <big>Aircraft-specific issues</big> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These issues apply only to specific aircraft or families.
</div>

=== FBW A320 or Headwind A330 – MCDU not programming ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Edit:
<pre>
Community\fsuipc-lvar-module\FSUIPC_WASM.ini
</pre>
Set:
<pre>
UseAirLocForHvars=Yes
</pre>
Save and restart MSFS.
</div>

----

=== Headwind A330 – FCU or MCDU not responding ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Copy:
<pre>
Community\fsuipc-lvar-module\modules\A320.hvar
</pre>
Rename the copy to:
<pre>
A330.hvar
</pre>
Restart MSFS.
</div>

----

=== PMDG aircraft – Enable SDK Data Broadcast ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<strong>Important:</strong> The aircraft must be loaded past the <strong>Ready to Fly</strong> screen at least once before these files exist.
</div>

# Exit Microsoft Flight Simulator.
# Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

==== MSFS 2020 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

==== MSFS 2024 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

# Open the <code>{aircraft_name}_Options.ini</code> file in a text editor such as Notepad.
# Add the following lines to the very end of the file:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
</pre>
</div>

# Save the file and restart Microsoft Flight Simulator.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
''Where <code>{username}</code> is your Windows username and <code>{aircraft_name}</code> is the specific PMDG aircraft you are using (for example, <code>737</code>).''
</div>

[[Troubleshooting#top|Back to top]]
----

== No English speech recognizer installed ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.
</div>

If English is not installed:

# Open Settings > Time & language > Language & region.
# Click Add a language.
# Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
# Select the English language > Next.
# Ensure Language pack and Speech are checked → Install.
# Restart Windows.

After restart, FSFO should detect an <code>en-*</code> recognizer.

If English is already listed or installed:

# Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
# Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

[[Troubleshooting#top|Back to top]]
----

== Voice recognition troubleshooting ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this section for microphone, permissions, and recognition accuracy problems.
</div>

'''Basic Checks:'''
* Microphone works?
** Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

* Privacy permissions (Windows 11):
** Settings > Privacy & security > Microphone
*** Microphone access: On
*** Let desktop apps access your microphone: On

* Correct input device
** Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

* No “exclusive mode” lock
** Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
*** Uncheck Allow applications to take exclusive control (as a test)

* Reasonable gain
** In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

'''English Speech Pack Installed (required):'''
* FSFO relies on English phrases. At least one English speech recognizer must be installed.
** Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
** Your Windows display language can be anything; only the English speech component is required.

'''Accuracy Tuning'''
* Lower <code>Input_VoiceAccuracy</code> if commands are missed.
* Increase it if false triggers occur.
* To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

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

[[Troubleshooting#top|Back to top]]
----

== No microphones found ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use these steps if FSFO shows no available input devices.
</div>

* '''Confirm Windows can see your mic'''
** Windows Settings > System > Sound > Input
** Select your microphone under Choose a device for speaking or recording
** Speak and verify the input level meter moves.
* '''Allow microphone permissions'''
** Windows Settings > Privacy & security > Microphone
** Turn ON:
*** Microphone access
*** Let apps access your microphone
*** Let desktop apps access your microphone
* '''Enable it in Control Panel (and set default)'''
** Open Control Panel > Sound > Recording
** Right-click your microphone > Enable
** Right-click it again > Set as Default Device
** (Optional) Set as Default Communication Device too.
* '''Basic Hardware Checks'''
** Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
** Unplug and replug, try a different USB port (avoid hubs while testing).
** If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

[[Troubleshooting#top|Back to top]]
----

== FSFO crashes ==

[[File:EventView.png|left|thumb|186x186px]]

<div style="margin-left:200px; margin-bottom:0.6em; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>When reporting crashes, include Windows Event Viewer logs.</strong>
</div>

# Type Event Viewer in the Windows Search Bar
# Click on the Event Viewer App
# Expand Windows Log > Expand Application
# Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
# Click The Details Tab, Copy and Email the contents to support

[[Troubleshooting#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
If your issue is not resolved after following the steps above, see [[Support]].
</div>

Troubleshooting

2026-03-26T17:01:34Z

Kingm56: /* Step 3: Confirm aircraft profile selection */

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

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this page when something is not working as expected before contacting support.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Unless a section says otherwise, always start programs in this order: <strong>MSFS → FSUIPC7 → FSFO</strong>.
</div>

<span id="top"></span>
----

== Copilot does not move any switches ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.
</div>

=== 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.

[[File:FSUIPC7_Connected_Lvars.png|600x600px|FSUIPC7 showing connected state and available LVARs]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If the LVARs are missing (0 Lvars); please go to Step 4

If the menu is disabled (WASM is missing), please go to Step 5
</div>

=== Step 2: Verify FSFO is connected to FSUIPC7 ===

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

[[File:FSFO_FSUIPC_Status.png|450x450px|FSFO showing FSUIPC7 version in the status bar]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If no version is shown, FSFO is not connected.
</div>

=== 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.

[[File:FSFO_Aircraft_Profile.png|450x450px|Aircraft profile selection on Start Flight page]]

=== Step 4: LVARs fail to load: ===

# Make sure MSFS is fully loaded into the cockpit before starting FSFO.
# Confirm FSUIPC7 shows Connected to the simulator (step 1).
# If you are using a complex aircraft, give it extra time to finish loading its systems.
# Start FSFO '''AFTER''' FSUIPC7 is already connected.
# If the issue continues, close everything and restart in this order:
## Start MSFS and load into the cockpit.
## Start FSUIPC7 and confirm it shows Connected WITH LVARS LOADED (step 1) .
## Start FSFO last.

If the LVARs still do not load, adjust the FSUIPC WASM scan settings (last resort):

# Close MSFS, FSUIPC7, and FSFO.
# Open the FSUIPC_WASM.ini file in the WASM persistence/work folder.
# Do not edit the copy in the Community folder.
# Set the following values:
## LvarScanDelay=15 //Increase as needed...start with 15
## LvarScanFrequency=0

After saving the file, restart in this order:

# Start MSFS and load into the cockpit.
# Start FSUIPC7 and confirm it shows Connected.
# Start FSFO last.

LVARs still fail to load, check whether the FSUIPC WASM module crashed (move to step 5)
What these edits do:

* LvarScanDelay=15 gives the aircraft more time to finish initializing before FSUIPC scans for LVARs.
* LvarScanFrequency=0 disables repeated rescans, which can help if the WASM is unstable or LVARs stop updating.

=== Step 5: Reinstall FSUIPC7 if needed ===

If the steps above fail:

# Close MSFS, FSFO, and FSUIPC7.
# Reinstall the latest FSUIPC7 installer over the existing installation.
# If problems persist, perform a clean FSUIPC7 reinstall:
## Uninstall FSUIPC7.
## Delete the FSUIPC7 install folder.
## Remove the FSUIPC WASM folder from the MSFS Community directory.
## Reboot Windows.
## Download the latest FSUIPC7 from here: https://fsuipc.com/fsuipc7/
## Unzip and Install the FSUIPC7 as Administrator.
### Right-Click Install_FSUIPC7.exe and select "Run as administrator."
### Ensure you select the sims you use - MSFS2020 and/or MSFS2024 (see picture below)
### Ensure the WASM module is selected (see picture below)!

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
After reinstall, start programs in this order:
<ol>
<li>Start MSFS and load into a cockpit.</li>
<li>Start FSUIPC7 and confirm it shows Connected.</li>
<li>Start FSFO last.</li>
</ol>
</div>
[[File:Select The Correct Sims.png|left|thumb]]

[[File:Setup2.png|left|thumb]]

[[Troubleshooting#top|Back to top]]
----

== FSFO does not stay on top ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This behavior is caused by Windows process-level restrictions.
</div>

Reasons:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.
</div>

Workaround:

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #12 (FSUIPC_ERR_SENDMSG) ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
FSFO and FSUIPC7 must run at the same permission level.
</div>

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #2 ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This error indicates a failed or incomplete FSUIPC connection.
</div>

=== Common Cause ===

* FSUIPC7 is not running
* More than one FSUIPC7 instance is open
* Antivirus or firewall is blocking communication
* FSUIPC7 was installed in a protected folder
* FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

=== Quick Restart Sequence ===

# Close FSFO, FSUIPC7, and MSFS.
# Reboot Windows.
# Start MSFS and load fully into a cockpit.
# Start FSUIPC7 and confirm it is running.
# Start FSFO and click Connect.

=== Additional Checks ===

# Ensure only one instance of FSUIPC7 is running (review your system tray).
# Disable Auto-Connect in FSFO temporarily and connect manually.
# Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
# Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

=== Installation Checks ===

* Do not install FSUIPC7 inside Program Files or other protected Windows folders.
* Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
* If needed, reinstall FSUIPC7 and then restart the PC.
* After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
* If unresolved, perform a clean FSUIPC7 reinstall.

[[Troubleshooting#top|Back to top]]
----

== WASM version mismatch ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Error example: “WASM version X while WAPI expects Y”.
</div>

Recommended fix:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Manual fix (advanced users):
</div>

# Close FSFO, MSFS and FSUIPC7
# Go to www.fsuipc.com
# Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
# Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
# Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
# Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
# Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

[[Troubleshooting#top|Back to top]]
----

== <big>Aircraft-specific issues</big> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These issues apply only to specific aircraft or families.
</div>

=== FBW A320 or Headwind A330 – MCDU not programming ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Edit:
<pre>
Community\fsuipc-lvar-module\FSUIPC_WASM.ini
</pre>
Set:
<pre>
UseAirLocForHvars=Yes
</pre>
Save and restart MSFS.
</div>

----

=== Headwind A330 – FCU or MCDU not responding ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Copy:
<pre>
Community\fsuipc-lvar-module\modules\A320.hvar
</pre>
Rename the copy to:
<pre>
A330.hvar
</pre>
Restart MSFS.
</div>

----

=== PMDG aircraft – Enable SDK Data Broadcast ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<strong>Important:</strong> The aircraft must be loaded past the <strong>Ready to Fly</strong> screen at least once before these files exist.
</div>

# Exit Microsoft Flight Simulator.
# Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

==== MSFS 2020 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

==== MSFS 2024 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

# Open the <code>{aircraft_name}_Options.ini</code> file in a text editor such as Notepad.
# Add the following lines to the very end of the file:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
</pre>
</div>

# Save the file and restart Microsoft Flight Simulator.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
''Where <code>{username}</code> is your Windows username and <code>{aircraft_name}</code> is the specific PMDG aircraft you are using (for example, <code>737</code>).''
</div>

[[Troubleshooting#top|Back to top]]
----

== No English speech recognizer installed ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.
</div>

If English is not installed:

# Open Settings > Time & language > Language & region.
# Click Add a language.
# Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
# Select the English language > Next.
# Ensure Language pack and Speech are checked → Install.
# Restart Windows.

After restart, FSFO should detect an <code>en-*</code> recognizer.

If English is already listed or installed:

# Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
# Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

[[Troubleshooting#top|Back to top]]
----

== Voice recognition troubleshooting ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this section for microphone, permissions, and recognition accuracy problems.
</div>

'''Basic Checks:'''
* Microphone works?
** Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

* Privacy permissions (Windows 11):
** Settings > Privacy & security > Microphone
*** Microphone access: On
*** Let desktop apps access your microphone: On

* Correct input device
** Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

* No “exclusive mode” lock
** Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
*** Uncheck Allow applications to take exclusive control (as a test)

* Reasonable gain
** In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

'''English Speech Pack Installed (required):'''
* FSFO relies on English phrases. At least one English speech recognizer must be installed.
** Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
** Your Windows display language can be anything; only the English speech component is required.

'''Accuracy Tuning'''
* Lower <code>Input_VoiceAccuracy</code> if commands are missed.
* Increase it if false triggers occur.
* To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

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

[[Troubleshooting#top|Back to top]]
----

== No microphones found ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use these steps if FSFO shows no available input devices.
</div>

* '''Confirm Windows can see your mic'''
** Windows Settings > System > Sound > Input
** Select your microphone under Choose a device for speaking or recording
** Speak and verify the input level meter moves.
* '''Allow microphone permissions'''
** Windows Settings > Privacy & security > Microphone
** Turn ON:
*** Microphone access
*** Let apps access your microphone
*** Let desktop apps access your microphone
* '''Enable it in Control Panel (and set default)'''
** Open Control Panel > Sound > Recording
** Right-click your microphone > Enable
** Right-click it again > Set as Default Device
** (Optional) Set as Default Communication Device too.
* '''Basic Hardware Checks'''
** Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
** Unplug and replug, try a different USB port (avoid hubs while testing).
** If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

[[Troubleshooting#top|Back to top]]
----

== FSFO crashes ==

[[File:EventView.png|left|thumb|186x186px]]

<div style="margin-left:200px; margin-bottom:0.6em; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>When reporting crashes, include Windows Event Viewer logs.</strong>
</div>

# Type Event Viewer in the Windows Search Bar
# Click on the Event Viewer App
# Expand Windows Log > Expand Application
# Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
# Click The Details Tab, Copy and Email the contents to support

[[Troubleshooting#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
If your issue is not resolved after following the steps above, see [[Support]].
</div>

Troubleshooting

2026-03-26T17:01:16Z

Kingm56: /* Step 5: Reinstall FSUIPC7 if needed */

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

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this page when something is not working as expected before contacting support.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Unless a section says otherwise, always start programs in this order: <strong>MSFS → FSUIPC7 → FSFO</strong>.
</div>

<span id="top"></span>
----

== Copilot does not move any switches ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.
</div>

=== 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.

[[File:FSUIPC7_Connected_Lvars.png|600x600px|FSUIPC7 showing connected state and available LVARs]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If the LVARs are missing (0 Lvars); please go to Step 4

If the menu is disabled (WASM is missing), please go to Step 5
</div>

=== Step 2: Verify FSFO is connected to FSUIPC7 ===

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

[[File:FSFO_FSUIPC_Status.png|450x450px|FSFO showing FSUIPC7 version in the status bar]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If no version is shown, FSFO is not connected.
</div>

=== 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.

[[File:FSFO_Aircraft_Profile.png|450x450px|Aircraft profile selection on Start Flight page]]

=== Step 4: LVARs fail to load: ===

# Make sure MSFS is fully loaded into the cockpit before starting FSFO.
# Confirm FSUIPC7 shows Connected to the simulator (step 1).
# If you are using a complex aircraft, give it extra time to finish loading its systems.
# Start FSFO '''AFTER''' FSUIPC7 is already connected.
# If the issue continues, close everything and restart in this order:
## Start MSFS and load into the cockpit.
## Start FSUIPC7 and confirm it shows Connected WITH LVARS LOADED (step 1) .
## Start FSFO last.

If the LVARs still do not load, adjust the FSUIPC WASM scan settings (last resort):

# Close MSFS, FSUIPC7, and FSFO.
# Open the FSUIPC_WASM.ini file in the WASM persistence/work folder.
# Do not edit the copy in the Community folder.
# Set the following values:
## LvarScanDelay=15 //Increase as needed...start with 15
## LvarScanFrequency=0

After saving the file, restart in this order:

# Start MSFS and load into the cockpit.
# Start FSUIPC7 and confirm it shows Connected.
# Start FSFO last.

LVARs still fail to load, check whether the FSUIPC WASM module crashed (move to step 5)
What these edits do:

* LvarScanDelay=15 gives the aircraft more time to finish initializing before FSUIPC scans for LVARs.
* LvarScanFrequency=0 disables repeated rescans, which can help if the WASM is unstable or LVARs stop updating.

=== Step 5: Reinstall FSUIPC7 if needed ===

If the steps above fail:

# Close MSFS, FSFO, and FSUIPC7.
# Reinstall the latest FSUIPC7 installer over the existing installation.
# If problems persist, perform a clean FSUIPC7 reinstall:
## Uninstall FSUIPC7.
## Delete the FSUIPC7 install folder.
## Remove the FSUIPC WASM folder from the MSFS Community directory.
## Reboot Windows.
## Download the latest FSUIPC7 from here: https://fsuipc.com/fsuipc7/
## Unzip and Install the FSUIPC7 as Administrator.
### Right-Click Install_FSUIPC7.exe and select "Run as administrator."
### Ensure you select the sims you use - MSFS2020 and/or MSFS2024 (see picture below)
### Ensure the WASM module is selected (see picture below)!

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
After reinstall, start programs in this order:
<ol>
<li>Start MSFS and load into a cockpit.</li>
<li>Start FSUIPC7 and confirm it shows Connected.</li>
<li>Start FSFO last.</li>
</ol>
</div>
[[File:Select The Correct Sims.png|left|thumb]]

[[File:Setup2.png|left|thumb]]

[[Troubleshooting#top|Back to top]]
----

== FSFO does not stay on top ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This behavior is caused by Windows process-level restrictions.
</div>

Reasons:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.
</div>

Workaround:

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #12 (FSUIPC_ERR_SENDMSG) ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
FSFO and FSUIPC7 must run at the same permission level.
</div>

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #2 ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This error indicates a failed or incomplete FSUIPC connection.
</div>

=== Common Cause ===

* FSUIPC7 is not running
* More than one FSUIPC7 instance is open
* Antivirus or firewall is blocking communication
* FSUIPC7 was installed in a protected folder
* FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

=== Quick Restart Sequence ===

# Close FSFO, FSUIPC7, and MSFS.
# Reboot Windows.
# Start MSFS and load fully into a cockpit.
# Start FSUIPC7 and confirm it is running.
# Start FSFO and click Connect.

=== Additional Checks ===

# Ensure only one instance of FSUIPC7 is running (review your system tray).
# Disable Auto-Connect in FSFO temporarily and connect manually.
# Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
# Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

=== Installation Checks ===

* Do not install FSUIPC7 inside Program Files or other protected Windows folders.
* Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
* If needed, reinstall FSUIPC7 and then restart the PC.
* After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
* If unresolved, perform a clean FSUIPC7 reinstall.

[[Troubleshooting#top|Back to top]]
----

== WASM version mismatch ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Error example: “WASM version X while WAPI expects Y”.
</div>

Recommended fix:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Manual fix (advanced users):
</div>

# Close FSFO, MSFS and FSUIPC7
# Go to www.fsuipc.com
# Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
# Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
# Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
# Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
# Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

[[Troubleshooting#top|Back to top]]
----

== <big>Aircraft-specific issues</big> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These issues apply only to specific aircraft or families.
</div>

=== FBW A320 or Headwind A330 – MCDU not programming ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Edit:
<pre>
Community\fsuipc-lvar-module\FSUIPC_WASM.ini
</pre>
Set:
<pre>
UseAirLocForHvars=Yes
</pre>
Save and restart MSFS.
</div>

----

=== Headwind A330 – FCU or MCDU not responding ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Copy:
<pre>
Community\fsuipc-lvar-module\modules\A320.hvar
</pre>
Rename the copy to:
<pre>
A330.hvar
</pre>
Restart MSFS.
</div>

----

=== PMDG aircraft – Enable SDK Data Broadcast ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<strong>Important:</strong> The aircraft must be loaded past the <strong>Ready to Fly</strong> screen at least once before these files exist.
</div>

# Exit Microsoft Flight Simulator.
# Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

==== MSFS 2020 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

==== MSFS 2024 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

# Open the <code>{aircraft_name}_Options.ini</code> file in a text editor such as Notepad.
# Add the following lines to the very end of the file:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
</pre>
</div>

# Save the file and restart Microsoft Flight Simulator.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
''Where <code>{username}</code> is your Windows username and <code>{aircraft_name}</code> is the specific PMDG aircraft you are using (for example, <code>737</code>).''
</div>

[[Troubleshooting#top|Back to top]]
----

== No English speech recognizer installed ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.
</div>

If English is not installed:

# Open Settings > Time & language > Language & region.
# Click Add a language.
# Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
# Select the English language > Next.
# Ensure Language pack and Speech are checked → Install.
# Restart Windows.

After restart, FSFO should detect an <code>en-*</code> recognizer.

If English is already listed or installed:

# Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
# Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

[[Troubleshooting#top|Back to top]]
----

== Voice recognition troubleshooting ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this section for microphone, permissions, and recognition accuracy problems.
</div>

'''Basic Checks:'''
* Microphone works?
** Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

* Privacy permissions (Windows 11):
** Settings > Privacy & security > Microphone
*** Microphone access: On
*** Let desktop apps access your microphone: On

* Correct input device
** Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

* No “exclusive mode” lock
** Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
*** Uncheck Allow applications to take exclusive control (as a test)

* Reasonable gain
** In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

'''English Speech Pack Installed (required):'''
* FSFO relies on English phrases. At least one English speech recognizer must be installed.
** Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
** Your Windows display language can be anything; only the English speech component is required.

'''Accuracy Tuning'''
* Lower <code>Input_VoiceAccuracy</code> if commands are missed.
* Increase it if false triggers occur.
* To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

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

[[Troubleshooting#top|Back to top]]
----

== No microphones found ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use these steps if FSFO shows no available input devices.
</div>

* '''Confirm Windows can see your mic'''
** Windows Settings > System > Sound > Input
** Select your microphone under Choose a device for speaking or recording
** Speak and verify the input level meter moves.
* '''Allow microphone permissions'''
** Windows Settings > Privacy & security > Microphone
** Turn ON:
*** Microphone access
*** Let apps access your microphone
*** Let desktop apps access your microphone
* '''Enable it in Control Panel (and set default)'''
** Open Control Panel > Sound > Recording
** Right-click your microphone > Enable
** Right-click it again > Set as Default Device
** (Optional) Set as Default Communication Device too.
* '''Basic Hardware Checks'''
** Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
** Unplug and replug, try a different USB port (avoid hubs while testing).
** If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

[[Troubleshooting#top|Back to top]]
----

== FSFO crashes ==

[[File:EventView.png|left|thumb|186x186px]]

<div style="margin-left:200px; margin-bottom:0.6em; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>When reporting crashes, include Windows Event Viewer logs.</strong>
</div>

# Type Event Viewer in the Windows Search Bar
# Click on the Event Viewer App
# Expand Windows Log > Expand Application
# Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
# Click The Details Tab, Copy and Email the contents to support

[[Troubleshooting#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
If your issue is not resolved after following the steps above, see [[Support]].
</div>

File:Setup2.png

2026-03-26T16:59:30Z

Kingm56:

Ensure you select the WASM module

File:Select The Correct Sims.png

2026-03-26T16:56:44Z

Kingm56:

Select The Correct Sims

Career Mode User Guide

2026-03-25T15:04:01Z

Kingm56: /* Career Options */

= FSFO Career Mode User Guide =

== Overview ==
Career Mode adds a persistent pilot progression system to FSFO. It uses a local database to track your pilot profile, your active schedule, and your permanent flight history.

The system is built around three main areas:
* '''Pilot Profile''' - your pilot's name, company, rank, tier, balance, location, type ratings, score, errors, contract legs, and training status
* '''Current Schedule''' - your active scheduled legs
* '''Flight Log''' - your permanent flight history and performance record

== Getting Started ==
# Open the '''Career Dashboard'''
# Click '''Rebuild Database''' the first time you use Career Mode
# Enter your pilot name
# Select a company
# Optionally select a type rating
# Click '''Apply Company'''

Once accepted, your pilot profile is created and Career Mode will begin tracking your progress.

== Career Dashboard ==
The Career Dashboard includes the following major functions:
* '''Rebuild Database''' - creates or recreates the local career database
* '''Apply Company''' - applies for a company and creates your pilot profile if needed
* '''Apply Type Rating''' - starts type-rating training
* '''Generate Schedule''' - builds your current schedule
* '''Load Stats''' - refreshes pilot statistics
* '''Save Options''' - saves career settings
* '''Flight Log''' - opens the permanent flight history window

'''Note:''' The current '''Show Contract''' button is not implemented yet.

== Career Options ==
Career Mode currently supports the following options:
* '''Start from last airport''' - Requires you to begin your next career flight from your saved current location. If enabled, FSFO checks that you are within 10 NM of the pilot's stored airport before the flight is considered ready.
* '''Fatal crash starts over''' - If enabled, a fatal crash can end your current career and force you to start over.
* '''Must fly scheduled flight''' - Only credits career progress when you complete the next pending scheduled leg in order. If enabled and you do not fly the correct leg, the flight can still be logged, but it will not advance total legs, average score, balance, rank, or career tier.
* '''Passenger comfort''' - Enables passenger-comfort rules so smoother, better-managed flights matter more to your career results.
* '''Can be fired''' - Enables the career rule that allows poor performance or major failures to put your employment at risk.
* '''Enable fatigue''' - Turns on fatigue tracking. If enabled, FSFO checks recent workload and can block career-flight readiness when fatigue rises above the allowed threshold.
* '''Schedule based on rank''' - Automatically builds schedules using the pilot's current rank and tier to determine the maximum leg distance. If a full schedule cannot be built within that cap, FSFO falls back to the full eligible route set.
* '''Must have type rating''' - Requires the pilot to hold the appropriate type rating before operating aircraft that need one.
* '''Lock schedule until complete''' - Prevents generating a new schedule while an existing schedule still has incomplete legs.
* '''Application based on rank''' - Makes company applications depend on your current rank, including tier eligibility and hiring probability. It also enforces the rejection cooldown for repeat applications.

These options affect how schedules are generated, when flights count toward progression, and whether readiness checks will block a flight.

== Companies and Company Tiers ==
Companies are loaded from ''Airlines.cfg''. Each airline has a tier. That tier affects hiring rules, contract leg requirements, and pay scaling.

Current contract-leg requirements by company tier:
* '''Tier 1''' - 30 legs
* '''Tier 2''' - 60 legs
* '''Tier 3''' - 90 legs
* '''Tier 4''' - 120 legs
* '''Tier 5''' - 150 legs

If you leave a company before satisfying the required legs, Career Mode can apply a contract-break penalty.

== Ranks ==
Career Mode uses a five-rank system:
* '''Rank 1''' - Cadet
* '''Rank 2''' - Second Officer
* '''Rank 3''' - First Officer
* '''Rank 4''' - Captain
* '''Rank 5''' - Senior Captain

Your rank affects:
* the maximum leg distance used in automatic scheduling
* your bidding advantage when schedules are generated
* which companies you can apply to if rank-based hiring is enabled
* your promotion eligibility
* your pay multiplier through Career Tier

== How Promotions Work ==
Promotions are based on two things:
* '''Total Legs'''
* '''Average Score'''

Your '''Average Score must be at least 92.0''' before any promotion is possible.

Promotion thresholds:
* '''50 total legs''' - promoted to '''Second Officer'''
* '''125 total legs''' - promoted to '''First Officer'''
* '''200 total legs''' - promoted to '''Captain'''
* '''350 total legs''' - promoted to '''Senior Captain'''

If your flight is not credited toward progression, it will not count toward promotion.

== Career Tier and Pay ==
Career Tier increases with promotion. Pay is recalculated using a tier multiplier.

Current pay multipliers:
* '''Tier 1''' - 1.00x
* '''Tier 2''' - 1.04x
* '''Tier 3''' - 1.08x
* '''Tier 4''' - 1.12x
* '''Tier 5''' - 1.16x

When you are promoted, FSFO updates:
* your rank
* your career tier
* your pay per hour

== Company Applications ==
If '''Application based on rank''' is enabled, not every pilot can freely join every airline tier.

Current hiring chances:
* '''Cadet'''
** Tier 1 = 100%
* '''Second Officer'''
** Tier 1 = 100%
** Tier 2 = 50%
* '''First Officer'''
** Tier 1 = 100%
** Tier 2 = 100%
** Tier 3 = 50%
* '''Captain'''
** Tier 1 = 100%
** Tier 2 = 100%
** Tier 3 = 75%
* '''Senior Captain'''
** Tier 1 = 100%
** Tier 2 = 100%
** Tier 3 = 95%

If you are rejected by the same company, FSFO enforces a 7-day wait before trying again.

== Type Ratings and Training ==
Use '''Apply Type Rating''' after you have joined a company.

Type rating requests will be blocked if:
* no pilot profile exists
* the pilot is not currently employed by a company
* the pilot is already in training
* the pilot already holds that type rating

Two training paths are available:
* '''Private Training''' - costs money immediately
* '''Company Training''' - extends contract legs instead of charging the balance directly

Training duration and costs depend on the type rating group.

== Schedule Generation ==
Schedules are built from your route data and filtered by:
* current airline
* rank
* type rating, if type-rating enforcement is enabled
* current location and preferred airport logic

If '''Schedule based on rank''' is enabled, FSFO automatically applies a maximum leg distance by rank:
* '''Rank 1''' - 350 NM
* '''Rank 2''' - 650 NM
* '''Rank 3''' - 1100 NM
* '''Rank 4''' - 1800 NM
* '''Rank 5''' - 3000 NM

FSFO first tries to build a schedule using that cap. If it cannot build a full schedule, it falls back to the full eligible route pool.

If '''Schedule based on rank''' is disabled, the Max NM value entered by the user is enforced strictly.

If '''Lock schedule until complete''' is enabled, FSFO will not generate a new schedule while an incomplete schedule already exists.

== Schedule Bidding System ==
When rank-based scheduling is enabled, FSFO scores route candidates and applies a bidding system.

Route scoring currently considers:
* base block-time value
* penalties for very short flights
* rank-based length bias
* preferred-airport bonuses

FSFO then divides scored routes into a preferred top bucket and a lower bucket.

The current rank-based bid chances are:
* '''Rank 1''' - 10%
* '''Rank 2''' - 35%
* '''Rank 3''' - 60%
* '''Rank 4''' - 90%
* '''Rank 5''' - 95%

If the bidding roll succeeds, FSFO selects from the top 30% of scored routes. Otherwise, it selects from the lower portion of the list.

== Preferred Airport ==
You can set a preferred airport for a company. FSFO uses that airport when generating schedules and gives preference to routes that end there, especially near the end of a generated trip.

== Route Map ==
After a schedule is generated, FSFO can build a route map from the loaded schedule legs and open it externally.

== When a Flight Counts Toward Progression ==
A flight does not automatically count toward career progression.

If '''Must fly scheduled flight''' is enabled, the flight must complete the '''next pending leg in order'''. FSFO compares:
* the actual flight number
* the actual departure airport
* the actual arrival airport

For the leg to count, the pilot must:
* start at the correct airport
* arrive at the correct airport
* match the next pending scheduled leg

If the flight does not meet that requirement:
* it can still be logged
* it will not increase Total Legs
* it will not update Average Score
* it will not reduce Contract Remaining Legs
* it will not update Balance
* it will not trigger promotion

If the next scheduled leg is completed correctly, it is marked '''COMPLETED'''. If that was the final remaining leg, the schedule is cleared.

== Flying a Career Flight ==
Before flight, FSFO captures:
* company
* flight number
* aircraft
* departure airport
* arrival airport

During flight, Career Mode monitors multiple operational and scoring categories.

Examples include:
* pitch exceedance
* bank exceedance
* G-force exceedance
* IAS exceedance
* taxi-speed exceedance
* light misuse
* fuel-management failures
* landing-performance issues

These events affect the total score and increment the appropriate error counters.

== Landing Score ==
Landing Score is based on:
* vertical speed
* G-force
* distance from the runway threshold

When runway data is available, the current weighting is:
* '''40%''' vertical speed
* '''30%''' G-force
* '''30%''' touchdown distance

If runway threshold data is unavailable, the distance portion is redistributed proportionally between vertical speed and G-force.

== Total Score and Qualification ==
Career Mode stores both:
* '''Landing Score'''
* '''Total Score'''

A flight is currently marked '''Qualified for Progression''' when the total score meets the system's qualification rule. The flight log stores that qualification result along with pay, fines, and error counts.

== Fatigue ==
If '''Enable fatigue''' is turned on, FSFO calculates fatigue from your recent workload using both:
* number of legs
* block hours

It evaluates three rolling workload windows:
* '''Last 24 hours'''
* '''Last 72 hours'''
* '''Last 7 days'''

The current formula is:

* '''Acute Load''' = max(legs in last 24h / 4, block hours in last 24h / 8)
* '''Short Load''' = max(legs in last 72h / 8, block hours in last 72h / 18)
* '''Weekly Load''' = max(legs in last 7d / 16, block hours in last 7d / 35)

Each load is clamped from 0 to 1.

Final fatigue:
* '''Fatigue = (Acute Load × 50) + (Short Load × 30) + (Weekly Load × 20)'''

The result is capped at 100 and rounded to the nearest whole percent.

If fatigue is above the allowed limit, Career Mode readiness should fail until workload decreases.

== Flight Log ==
The Flight Log is the permanent history of your career flights.

Each flight log entry stores:
* date
* company
* flight number
* aircraft
* from airport
* to airport
* block time
* landing score
* total score
* landing rate
* landing G
* block fuel
* critical/configuration/lights/speed error counts
* qualification result
* pay earned
* fines paid

Use the Flight Log window to review your performance over time.

== Notes ==
* Career Mode currently supports one local pilot profile
* The current schedule stores only the active trip
* The flight log is the permanent historical record
* The current '''Show Contract''' button is not implemented yet

== Troubleshooting ==
=== "PilotProfile was not found" ===
Create or rebuild the database, then apply to a company.

=== No schedule was generated ===
Check that:
* ''routes.csv'' exists
* the file format is valid
* routes match the current airline
* type-rating rules are not filtering everything out
* the requested leg count is realistic for the route pool

=== My flight did not count toward progression ===
If '''Must fly scheduled flight''' is enabled, verify that:
* you flew the next pending leg in order
* you started at the scheduled departure airport
* you arrived at the scheduled arrival airport
* the flight number matched when required

=== I cannot generate a new schedule ===
If '''Lock schedule until complete''' is enabled, finish the current schedule first or turn that option off.

[[Category:User Guide]]
[[Category:Career Mode]]

Career Mode User Guide

2026-03-25T15:01:29Z

Kingm56: /* Career Options */

= FSFO Career Mode User Guide =

== Overview ==
Career Mode adds a persistent pilot progression system to FSFO. It uses a local database to track your pilot profile, your active schedule, and your permanent flight history.

The system is built around three main areas:
* '''Pilot Profile''' - your pilot's name, company, rank, tier, balance, location, type ratings, score, errors, contract legs, and training status
* '''Current Schedule''' - your active scheduled legs
* '''Flight Log''' - your permanent flight history and performance record

== Getting Started ==
# Open the '''Career Dashboard'''
# Click '''Rebuild Database''' the first time you use Career Mode
# Enter your pilot name
# Select a company
# Optionally select a type rating
# Click '''Apply Company'''

Once accepted, your pilot profile is created and Career Mode will begin tracking your progress.

== Career Dashboard ==
The Career Dashboard includes the following major functions:
* '''Rebuild Database''' - creates or recreates the local career database
* '''Apply Company''' - applies for a company and creates your pilot profile if needed
* '''Apply Type Rating''' - starts type-rating training
* '''Generate Schedule''' - builds your current schedule
* '''Load Stats''' - refreshes pilot statistics
* '''Save Options''' - saves career settings
* '''Flight Log''' - opens the permanent flight history window

'''Note:''' The current '''Show Contract''' button is not implemented yet.

== Career Options ==
Career Mode currently supports the following options:
* '''Start from last airport''' - Requires you to begin your next career flight from your saved current location. If enabled, FSFO checks that you are within 10 NM of the pilot’s stored airport before the flight is considered ready. :contentReference[oaicite:0]{index=0}
* '''Fatal crash starts over''' - If enabled, a fatal crash can end the current career and force you to start over.
* '''Must fly scheduled flight''' - Only credits career progress when you complete the '''next pending scheduled leg in order'''. If enabled and you do not fly the correct leg, the flight can still be logged, but it will not advance total legs, average score, balance, rank, or career tier.
* '''Passenger comfort''' - Enables the passenger-comfort rule set so smoother, better-managed flights matter more to your career results. :contentReference[oaicite:3]{index=3}
* '''Can be fired''' - Enables the career rule that allows poor performance or major failures to put your employment at risk. :contentReference[oaicite:4]{index=4}
* '''Enable fatigue''' - Turns on fatigue tracking. If enabled, FSFO checks recent workload and blocks career-flight readiness when fatigue rises above 80%. :contentReference[oaicite:5]{index=5}
* '''Schedule based on rank''' - Automatically builds schedules using the pilot’s current rank/tier to determine the max leg distance. If a full schedule cannot be built within that cap, FSFO falls back to the full eligible route set.
* '''Must have type rating''' - Requires the pilot to hold the appropriate type rating before operating aircraft that need one.
* '''Lock schedule until complete''' - Prevents generating a new schedule while an existing schedule still has incomplete legs.
* '''Application based on rank''' - Makes company applications depend on your current rank, including tier eligibility and hiring probability. It also enforces the rejection cooldown for repeat applications.

These options affect how schedules are generated, when flights count toward progression, and whether readiness checks will block a flight.

== Companies and Company Tiers ==
Companies are loaded from ''Airlines.cfg''. Each airline has a tier. That tier affects hiring rules, contract leg requirements, and pay scaling.

Current contract-leg requirements by company tier:
* '''Tier 1''' - 30 legs
* '''Tier 2''' - 60 legs
* '''Tier 3''' - 90 legs
* '''Tier 4''' - 120 legs
* '''Tier 5''' - 150 legs

If you leave a company before satisfying the required legs, Career Mode can apply a contract-break penalty.

== Ranks ==
Career Mode uses a five-rank system:
* '''Rank 1''' - Cadet
* '''Rank 2''' - Second Officer
* '''Rank 3''' - First Officer
* '''Rank 4''' - Captain
* '''Rank 5''' - Senior Captain

Your rank affects:
* the maximum leg distance used in automatic scheduling
* your bidding advantage when schedules are generated
* which companies you can apply to if rank-based hiring is enabled
* your promotion eligibility
* your pay multiplier through Career Tier

== How Promotions Work ==
Promotions are based on two things:
* '''Total Legs'''
* '''Average Score'''

Your '''Average Score must be at least 92.0''' before any promotion is possible.

Promotion thresholds:
* '''50 total legs''' - promoted to '''Second Officer'''
* '''125 total legs''' - promoted to '''First Officer'''
* '''200 total legs''' - promoted to '''Captain'''
* '''350 total legs''' - promoted to '''Senior Captain'''

If your flight is not credited toward progression, it will not count toward promotion.

== Career Tier and Pay ==
Career Tier increases with promotion. Pay is recalculated using a tier multiplier.

Current pay multipliers:
* '''Tier 1''' - 1.00x
* '''Tier 2''' - 1.04x
* '''Tier 3''' - 1.08x
* '''Tier 4''' - 1.12x
* '''Tier 5''' - 1.16x

When you are promoted, FSFO updates:
* your rank
* your career tier
* your pay per hour

== Company Applications ==
If '''Application based on rank''' is enabled, not every pilot can freely join every airline tier.

Current hiring chances:
* '''Cadet'''
** Tier 1 = 100%
* '''Second Officer'''
** Tier 1 = 100%
** Tier 2 = 50%
* '''First Officer'''
** Tier 1 = 100%
** Tier 2 = 100%
** Tier 3 = 50%
* '''Captain'''
** Tier 1 = 100%
** Tier 2 = 100%
** Tier 3 = 75%
* '''Senior Captain'''
** Tier 1 = 100%
** Tier 2 = 100%
** Tier 3 = 95%

If you are rejected by the same company, FSFO enforces a 7-day wait before trying again.

== Type Ratings and Training ==
Use '''Apply Type Rating''' after you have joined a company.

Type rating requests will be blocked if:
* no pilot profile exists
* the pilot is not currently employed by a company
* the pilot is already in training
* the pilot already holds that type rating

Two training paths are available:
* '''Private Training''' - costs money immediately
* '''Company Training''' - extends contract legs instead of charging the balance directly

Training duration and costs depend on the type rating group.

== Schedule Generation ==
Schedules are built from your route data and filtered by:
* current airline
* rank
* type rating, if type-rating enforcement is enabled
* current location and preferred airport logic

If '''Schedule based on rank''' is enabled, FSFO automatically applies a maximum leg distance by rank:
* '''Rank 1''' - 350 NM
* '''Rank 2''' - 650 NM
* '''Rank 3''' - 1100 NM
* '''Rank 4''' - 1800 NM
* '''Rank 5''' - 3000 NM

FSFO first tries to build a schedule using that cap. If it cannot build a full schedule, it falls back to the full eligible route pool.

If '''Schedule based on rank''' is disabled, the Max NM value entered by the user is enforced strictly.

If '''Lock schedule until complete''' is enabled, FSFO will not generate a new schedule while an incomplete schedule already exists.

== Schedule Bidding System ==
When rank-based scheduling is enabled, FSFO scores route candidates and applies a bidding system.

Route scoring currently considers:
* base block-time value
* penalties for very short flights
* rank-based length bias
* preferred-airport bonuses

FSFO then divides scored routes into a preferred top bucket and a lower bucket.

The current rank-based bid chances are:
* '''Rank 1''' - 10%
* '''Rank 2''' - 35%
* '''Rank 3''' - 60%
* '''Rank 4''' - 90%
* '''Rank 5''' - 95%

If the bidding roll succeeds, FSFO selects from the top 30% of scored routes. Otherwise, it selects from the lower portion of the list.

== Preferred Airport ==
You can set a preferred airport for a company. FSFO uses that airport when generating schedules and gives preference to routes that end there, especially near the end of a generated trip.

== Route Map ==
After a schedule is generated, FSFO can build a route map from the loaded schedule legs and open it externally.

== When a Flight Counts Toward Progression ==
A flight does not automatically count toward career progression.

If '''Must fly scheduled flight''' is enabled, the flight must complete the '''next pending leg in order'''. FSFO compares:
* the actual flight number
* the actual departure airport
* the actual arrival airport

For the leg to count, the pilot must:
* start at the correct airport
* arrive at the correct airport
* match the next pending scheduled leg

If the flight does not meet that requirement:
* it can still be logged
* it will not increase Total Legs
* it will not update Average Score
* it will not reduce Contract Remaining Legs
* it will not update Balance
* it will not trigger promotion

If the next scheduled leg is completed correctly, it is marked '''COMPLETED'''. If that was the final remaining leg, the schedule is cleared.

== Flying a Career Flight ==
Before flight, FSFO captures:
* company
* flight number
* aircraft
* departure airport
* arrival airport

During flight, Career Mode monitors multiple operational and scoring categories.

Examples include:
* pitch exceedance
* bank exceedance
* G-force exceedance
* IAS exceedance
* taxi-speed exceedance
* light misuse
* fuel-management failures
* landing-performance issues

These events affect the total score and increment the appropriate error counters.

== Landing Score ==
Landing Score is based on:
* vertical speed
* G-force
* distance from the runway threshold

When runway data is available, the current weighting is:
* '''40%''' vertical speed
* '''30%''' G-force
* '''30%''' touchdown distance

If runway threshold data is unavailable, the distance portion is redistributed proportionally between vertical speed and G-force.

== Total Score and Qualification ==
Career Mode stores both:
* '''Landing Score'''
* '''Total Score'''

A flight is currently marked '''Qualified for Progression''' when the total score meets the system's qualification rule. The flight log stores that qualification result along with pay, fines, and error counts.

== Fatigue ==
If '''Enable fatigue''' is turned on, FSFO calculates fatigue from your recent workload using both:
* number of legs
* block hours

It evaluates three rolling workload windows:
* '''Last 24 hours'''
* '''Last 72 hours'''
* '''Last 7 days'''

The current formula is:

* '''Acute Load''' = max(legs in last 24h / 4, block hours in last 24h / 8)
* '''Short Load''' = max(legs in last 72h / 8, block hours in last 72h / 18)
* '''Weekly Load''' = max(legs in last 7d / 16, block hours in last 7d / 35)

Each load is clamped from 0 to 1.

Final fatigue:
* '''Fatigue = (Acute Load × 50) + (Short Load × 30) + (Weekly Load × 20)'''

The result is capped at 100 and rounded to the nearest whole percent.

If fatigue is above the allowed limit, Career Mode readiness should fail until workload decreases.

== Flight Log ==
The Flight Log is the permanent history of your career flights.

Each flight log entry stores:
* date
* company
* flight number
* aircraft
* from airport
* to airport
* block time
* landing score
* total score
* landing rate
* landing G
* block fuel
* critical/configuration/lights/speed error counts
* qualification result
* pay earned
* fines paid

Use the Flight Log window to review your performance over time.

== Notes ==
* Career Mode currently supports one local pilot profile
* The current schedule stores only the active trip
* The flight log is the permanent historical record
* The current '''Show Contract''' button is not implemented yet

== Troubleshooting ==
=== "PilotProfile was not found" ===
Create or rebuild the database, then apply to a company.

=== No schedule was generated ===
Check that:
* ''routes.csv'' exists
* the file format is valid
* routes match the current airline
* type-rating rules are not filtering everything out
* the requested leg count is realistic for the route pool

=== My flight did not count toward progression ===
If '''Must fly scheduled flight''' is enabled, verify that:
* you flew the next pending leg in order
* you started at the scheduled departure airport
* you arrived at the scheduled arrival airport
* the flight number matched when required

=== I cannot generate a new schedule ===
If '''Lock schedule until complete''' is enabled, finish the current schedule first or turn that option off.

[[Category:User Guide]]
[[Category:Career Mode]]

Main Page

2026-03-25T14:54:51Z

Kingm56: /* Documentation and Reference */

__NOTOC__

Welcome to the official Flight Simulator First Officer (FSFO) wiki.

This wiki contains setup guides, tutorials, troubleshooting steps, and technical references for using FSFO with Microsoft Flight Simulator.

----

{| style="width:100%; border-spacing:16px;"
| style="width:50%; vertical-align:top; background:#eef3fb; border-left:8px solid #1f4fa3; padding:16px; border-radius:10px;" |

== <span style="color:#1f4fa3;">Start Here</span> ==
'''New to FSFO? Begin with these resources.'''

* '''[[Getting Started]]'''<br />
First-time setup and the minimum steps required to start your first flight.

* '''[[User Settings Reference|User Settings]]'''<br />
Explanation of every configurable option and setting in FSFO.

* '''[[Voice Commands]]'''<br />
Complete list of supported voice commands and spoken responses.

* '''[[YouTube|Video Tutorial Series]]'''<br />
Step-by-step walkthrough videos for common FSFO tasks.

* '''[[FAQ|Frequently Asked Questions]]'''<br />
A list of frequently asked questions about FSFO.

| style="width:50%; vertical-align:top; background:#f8f9f6; border-left:6px solid #5cb85c; padding:14px; border-radius:8px;" |

== Support ==
Help, fixes, and answers to common problems.

* '''[[Limitations]]'''<br />
Known feature and platform limitations you should be aware of.

* '''[[Troubleshooting]]'''<br />
Solutions for common installation, connection, and runtime issues.

* '''[[Release Notes]]'''<br />
Version history, new features, and bug fixes.

* '''[[Support|Contact Support]]'''<br />
How to contact support and get help via email or Discord.

|-
| style="width:50%; vertical-align:top; background:#f4f9f6; border-left:6px solid #5bc0de; padding:14px; border-radius:8px;" |

== Documentation and Reference ==
In-depth guides and technical references.

* '''[[Career_Mode_User_Guide|Career Mode User Guide]]'''

Pilot progression, rank advancement, schedule bidding, fatigue tracking, and career performance history.

* '''[[Advanced_Users_Guide|Advanced Users Guide]]'''

Advanced SOP editing, custom flows, and smart flow tuning.

* '''[[SIMVAR_Control_Numbers|SIMVAR Control Numbers]]'''

Reference list of SIMVAR control numbers used by FSFO.

| style="width:50%; vertical-align:top; background:#fdf7f2; border-left:6px solid #f0ad4e; padding:14px; border-radius:8px;" |

== Community ==
Updates and places to connect with other FSFO users.

* [https://discord.gg/6WSHapSWWh FSFO Discord]<br />
Live community chat, announcements, and peer support.

* [https://www.youtube.com/@flightsimulatorfirstoffice9181 FSFO YouTube Channel]<br />
Official tutorial and feature videos for FSFO.

|}

Main Page

2026-03-25T14:54:28Z

Kingm56: /* Documentation and Reference */

__NOTOC__

Welcome to the official Flight Simulator First Officer (FSFO) wiki.

This wiki contains setup guides, tutorials, troubleshooting steps, and technical references for using FSFO with Microsoft Flight Simulator.

----

{| style="width:100%; border-spacing:16px;"
| style="width:50%; vertical-align:top; background:#eef3fb; border-left:8px solid #1f4fa3; padding:16px; border-radius:10px;" |

== <span style="color:#1f4fa3;">Start Here</span> ==
'''New to FSFO? Begin with these resources.'''

* '''[[Getting Started]]'''<br />
First-time setup and the minimum steps required to start your first flight.

* '''[[User Settings Reference|User Settings]]'''<br />
Explanation of every configurable option and setting in FSFO.

* '''[[Voice Commands]]'''<br />
Complete list of supported voice commands and spoken responses.

* '''[[YouTube|Video Tutorial Series]]'''<br />
Step-by-step walkthrough videos for common FSFO tasks.

* '''[[FAQ|Frequently Asked Questions]]'''<br />
A list of frequently asked questions about FSFO.

| style="width:50%; vertical-align:top; background:#f8f9f6; border-left:6px solid #5cb85c; padding:14px; border-radius:8px;" |

== Support ==
Help, fixes, and answers to common problems.

* '''[[Limitations]]'''<br />
Known feature and platform limitations you should be aware of.

* '''[[Troubleshooting]]'''<br />
Solutions for common installation, connection, and runtime issues.

* '''[[Release Notes]]'''<br />
Version history, new features, and bug fixes.

* '''[[Support|Contact Support]]'''<br />
How to contact support and get help via email or Discord.

|-
| style="width:50%; vertical-align:top; background:#f4f9f6; border-left:6px solid #5bc0de; padding:14px; border-radius:8px;" |

== Documentation and Reference ==
In-depth guides and technical references.

* [[Career_Mode_User_Guide|Career Mode User Guide]]

Pilot progression, rank advancement, schedule bidding, fatigue tracking, and career performance history.

* '''[[Advanced Users Guide]]'''<br />
Advanced SOP editing, custom flows, and smart flow tuning.

* '''[[SIMVAR Control Numbers]]'''<br />
Reference list of SIMVAR control numbers used by FSFO.

| style="width:50%; vertical-align:top; background:#fdf7f2; border-left:6px solid #f0ad4e; padding:14px; border-radius:8px;" |

== Community ==
Updates and places to connect with other FSFO users.

* [https://discord.gg/6WSHapSWWh FSFO Discord]<br />
Live community chat, announcements, and peer support.

* [https://www.youtube.com/@flightsimulatorfirstoffice9181 FSFO YouTube Channel]<br />
Official tutorial and feature videos for FSFO.

|}

Main Page

2026-03-25T14:54:05Z

Kingm56: /* Documentation and Reference */

__NOTOC__

Welcome to the official Flight Simulator First Officer (FSFO) wiki.

This wiki contains setup guides, tutorials, troubleshooting steps, and technical references for using FSFO with Microsoft Flight Simulator.

----

{| style="width:100%; border-spacing:16px;"
| style="width:50%; vertical-align:top; background:#eef3fb; border-left:8px solid #1f4fa3; padding:16px; border-radius:10px;" |

== <span style="color:#1f4fa3;">Start Here</span> ==
'''New to FSFO? Begin with these resources.'''

* '''[[Getting Started]]'''<br />
First-time setup and the minimum steps required to start your first flight.

* '''[[User Settings Reference|User Settings]]'''<br />
Explanation of every configurable option and setting in FSFO.

* '''[[Voice Commands]]'''<br />
Complete list of supported voice commands and spoken responses.

* '''[[YouTube|Video Tutorial Series]]'''<br />
Step-by-step walkthrough videos for common FSFO tasks.

* '''[[FAQ|Frequently Asked Questions]]'''<br />
A list of frequently asked questions about FSFO.

| style="width:50%; vertical-align:top; background:#f8f9f6; border-left:6px solid #5cb85c; padding:14px; border-radius:8px;" |

== Support ==
Help, fixes, and answers to common problems.

* '''[[Limitations]]'''<br />
Known feature and platform limitations you should be aware of.

* '''[[Troubleshooting]]'''<br />
Solutions for common installation, connection, and runtime issues.

* '''[[Release Notes]]'''<br />
Version history, new features, and bug fixes.

* '''[[Support|Contact Support]]'''<br />
How to contact support and get help via email or Discord.

|-
| style="width:50%; vertical-align:top; background:#f4f9f6; border-left:6px solid #5bc0de; padding:14px; border-radius:8px;" |

== Documentation and Reference ==
In-depth guides and technical references.

* '''[[Career_Mode_User_Guide|Career Mode User Guide]]'''

Pilot progression, rank advancement, schedule bidding, fatigue tracking, and career performance history.

* '''[[Advanced_Users_Guide|Advanced Users Guide]]'''

Advanced SOP editing, custom flows, and smart flow tuning.

* '''[[SIMVAR_Control_Numbers|SIMVAR Control Numbers]]'''

Reference list of SIMVAR control numbers used by FSFO.

== Community ==
Updates and places to connect with other FSFO users.

* [https://discord.gg/6WSHapSWWh FSFO Discord]<br />
Live community chat, announcements, and peer support.

* [https://www.youtube.com/@flightsimulatorfirstoffice9181 FSFO YouTube Channel]<br />
Official tutorial and feature videos for FSFO.

|}

Main Page

2026-03-25T14:43:40Z

Kingm56: /* Documentation and Reference */

__NOTOC__

Welcome to the official Flight Simulator First Officer (FSFO) wiki.

This wiki contains setup guides, tutorials, troubleshooting steps, and technical references for using FSFO with Microsoft Flight Simulator.

----

{| style="width:100%; border-spacing:16px;"
| style="width:50%; vertical-align:top; background:#eef3fb; border-left:8px solid #1f4fa3; padding:16px; border-radius:10px;" |

== <span style="color:#1f4fa3;">Start Here</span> ==
'''New to FSFO? Begin with these resources.'''

* '''[[Getting Started]]'''<br />
First-time setup and the minimum steps required to start your first flight.

* '''[[User Settings Reference|User Settings]]'''<br />
Explanation of every configurable option and setting in FSFO.

* '''[[Voice Commands]]'''<br />
Complete list of supported voice commands and spoken responses.

* '''[[YouTube|Video Tutorial Series]]'''<br />
Step-by-step walkthrough videos for common FSFO tasks.

* '''[[FAQ|Frequently Asked Questions]]'''<br />
A list of frequently asked questions about FSFO.

| style="width:50%; vertical-align:top; background:#f8f9f6; border-left:6px solid #5cb85c; padding:14px; border-radius:8px;" |

== Support ==
Help, fixes, and answers to common problems.

* '''[[Limitations]]'''<br />
Known feature and platform limitations you should be aware of.

* '''[[Troubleshooting]]'''<br />
Solutions for common installation, connection, and runtime issues.

* '''[[Release Notes]]'''<br />
Version history, new features, and bug fixes.

* '''[[Support|Contact Support]]'''<br />
How to contact support and get help via email or Discord.

|-
| style="width:50%; vertical-align:top; background:#f4f9f6; border-left:6px solid #5bc0de; padding:14px; border-radius:8px;" |

== Documentation and Reference ==
In-depth guides and technical references.

* [[Career_Mode_User_Guide|Career Mode User Guide]]

Pilot progression, rank advancement, schedule bidding, fatigue tracking, and career performance history.

* '''[[Advanced Users Guide]]'''<br />
Advanced SOP editing, custom flows, and smart flow tuning.

* '''[[SIMVAR Control Numbers]]'''<br />
Reference list of SIMVAR control numbers used by FSFO.

| style="width:50%; vertical-align:top; background:#fdf7f2; border-left:6px solid #f0ad4e; padding:14px; border-radius:8px;" |

== Community ==
Updates and places to connect with other FSFO users.

* [https://discord.gg/6WSHapSWWh FSFO Discord]<br />
Live community chat, announcements, and peer support.

* [https://www.youtube.com/@flightsimulatorfirstoffice9181 FSFO YouTube Channel]<br />
Official tutorial and feature videos for FSFO.

|}

Main Page

2026-03-25T14:39:25Z

Kingm56:

__NOTOC__

Welcome to the official Flight Simulator First Officer (FSFO) wiki.

This wiki contains setup guides, tutorials, troubleshooting steps, and technical references for using FSFO with Microsoft Flight Simulator.

----

{| style="width:100%; border-spacing:16px;"
| style="width:50%; vertical-align:top; background:#eef3fb; border-left:8px solid #1f4fa3; padding:16px; border-radius:10px;" |

== <span style="color:#1f4fa3;">Start Here</span> ==
'''New to FSFO? Begin with these resources.'''

* '''[[Getting Started]]'''<br />
First-time setup and the minimum steps required to start your first flight.

* '''[[User Settings Reference|User Settings]]'''<br />
Explanation of every configurable option and setting in FSFO.

* '''[[Voice Commands]]'''<br />
Complete list of supported voice commands and spoken responses.

* '''[[YouTube|Video Tutorial Series]]'''<br />
Step-by-step walkthrough videos for common FSFO tasks.

* '''[[FAQ|Frequently Asked Questions]]'''<br />
A list of frequently asked questions about FSFO.

| style="width:50%; vertical-align:top; background:#f8f9f6; border-left:6px solid #5cb85c; padding:14px; border-radius:8px;" |

== Support ==
Help, fixes, and answers to common problems.

* '''[[Limitations]]'''<br />
Known feature and platform limitations you should be aware of.

* '''[[Troubleshooting]]'''<br />
Solutions for common installation, connection, and runtime issues.

* '''[[Release Notes]]'''<br />
Version history, new features, and bug fixes.

* '''[[Support|Contact Support]]'''<br />
How to contact support and get help via email or Discord.

|-
| style="width:50%; vertical-align:top; background:#f4f9f6; border-left:6px solid #5bc0de; padding:14px; border-radius:8px;" |

== Documentation and Reference ==
In-depth guides and technical references.

* '''[[Career Mode User Guide]]'''<br />
Pilot progression, rank advancement, schedule bidding, fatigue tracking, and career performance history.

* '''[[Advanced Users Guide]]'''<br />
Advanced SOP editing, custom flows, and smart flow tuning.

* '''[[SIMVAR Control Numbers]]'''<br />
Reference list of SIMVAR control numbers used by FSFO.

| style="width:50%; vertical-align:top; background:#fdf7f2; border-left:6px solid #f0ad4e; padding:14px; border-radius:8px;" |

== Community ==
Updates and places to connect with other FSFO users.

* [https://discord.gg/6WSHapSWWh FSFO Discord]<br />
Live community chat, announcements, and peer support.

* [https://www.youtube.com/@flightsimulatorfirstoffice9181 FSFO YouTube Channel]<br />
Official tutorial and feature videos for FSFO.

|}

Career Mode User Guide

2026-03-24T21:33:18Z

Kingm56: Created page with "= FSFO Career Mode User Guide = == Overview == Career Mode adds a persistent pilot progression system to FSFO. It uses a local database to track your pilot profile, your active schedule, and your permanent flight history. The system is built around three main areas: * '''Pilot Profile''' - your pilot's name, company, rank, tier, balance, location, type ratings, score, errors, contract legs, and training status * '''Current Schedule''' - your active scheduled legs * '''..."

= FSFO Career Mode User Guide =

== Overview ==
Career Mode adds a persistent pilot progression system to FSFO. It uses a local database to track your pilot profile, your active schedule, and your permanent flight history.

The system is built around three main areas:
* '''Pilot Profile''' - your pilot's name, company, rank, tier, balance, location, type ratings, score, errors, contract legs, and training status
* '''Current Schedule''' - your active scheduled legs
* '''Flight Log''' - your permanent flight history and performance record

== Getting Started ==
# Open the '''Career Dashboard'''
# Click '''Rebuild Database''' the first time you use Career Mode
# Enter your pilot name
# Select a company
# Optionally select a type rating
# Click '''Apply Company'''

Once accepted, your pilot profile is created and Career Mode will begin tracking your progress.

== Career Dashboard ==
The Career Dashboard includes the following major functions:
* '''Rebuild Database''' - creates or recreates the local career database
* '''Apply Company''' - applies for a company and creates your pilot profile if needed
* '''Apply Type Rating''' - starts type-rating training
* '''Generate Schedule''' - builds your current schedule
* '''Load Stats''' - refreshes pilot statistics
* '''Save Options''' - saves career settings
* '''Flight Log''' - opens the permanent flight history window

'''Note:''' The current '''Show Contract''' button is not implemented yet.

== Career Options ==
Career Mode currently supports the following options:
* '''Start from last airport'''
* '''Fatal crash starts over'''
* '''Must fly scheduled flight'''
* '''Passenger comfort'''
* '''Can be fired'''
* '''Enable fatigue'''
* '''Schedule based on rank'''
* '''Must have type rating'''
* '''Lock schedule until complete'''
* '''Application based on rank'''

These options affect how schedules are generated, when flights count toward progression, and whether readiness checks will block a flight.

== Companies and Company Tiers ==
Companies are loaded from ''Airlines.cfg''. Each airline has a tier. That tier affects hiring rules, contract leg requirements, and pay scaling.

Current contract-leg requirements by company tier:
* '''Tier 1''' - 30 legs
* '''Tier 2''' - 60 legs
* '''Tier 3''' - 90 legs
* '''Tier 4''' - 120 legs
* '''Tier 5''' - 150 legs

If you leave a company before satisfying the required legs, Career Mode can apply a contract-break penalty.

== Ranks ==
Career Mode uses a five-rank system:
* '''Rank 1''' - Cadet
* '''Rank 2''' - Second Officer
* '''Rank 3''' - First Officer
* '''Rank 4''' - Captain
* '''Rank 5''' - Senior Captain

Your rank affects:
* the maximum leg distance used in automatic scheduling
* your bidding advantage when schedules are generated
* which companies you can apply to if rank-based hiring is enabled
* your promotion eligibility
* your pay multiplier through Career Tier

== How Promotions Work ==
Promotions are based on two things:
* '''Total Legs'''
* '''Average Score'''

Your '''Average Score must be at least 92.0''' before any promotion is possible.

Promotion thresholds:
* '''50 total legs''' - promoted to '''Second Officer'''
* '''125 total legs''' - promoted to '''First Officer'''
* '''200 total legs''' - promoted to '''Captain'''
* '''350 total legs''' - promoted to '''Senior Captain'''

If your flight is not credited toward progression, it will not count toward promotion.

== Career Tier and Pay ==
Career Tier increases with promotion. Pay is recalculated using a tier multiplier.

Current pay multipliers:
* '''Tier 1''' - 1.00x
* '''Tier 2''' - 1.04x
* '''Tier 3''' - 1.08x
* '''Tier 4''' - 1.12x
* '''Tier 5''' - 1.16x

When you are promoted, FSFO updates:
* your rank
* your career tier
* your pay per hour

== Company Applications ==
If '''Application based on rank''' is enabled, not every pilot can freely join every airline tier.

Current hiring chances:
* '''Cadet'''
** Tier 1 = 100%
* '''Second Officer'''
** Tier 1 = 100%
** Tier 2 = 50%
* '''First Officer'''
** Tier 1 = 100%
** Tier 2 = 100%
** Tier 3 = 50%
* '''Captain'''
** Tier 1 = 100%
** Tier 2 = 100%
** Tier 3 = 75%
* '''Senior Captain'''
** Tier 1 = 100%
** Tier 2 = 100%
** Tier 3 = 95%

If you are rejected by the same company, FSFO enforces a 7-day wait before trying again.

== Type Ratings and Training ==
Use '''Apply Type Rating''' after you have joined a company.

Type rating requests will be blocked if:
* no pilot profile exists
* the pilot is not currently employed by a company
* the pilot is already in training
* the pilot already holds that type rating

Two training paths are available:
* '''Private Training''' - costs money immediately
* '''Company Training''' - extends contract legs instead of charging the balance directly

Training duration and costs depend on the type rating group.

== Schedule Generation ==
Schedules are built from your route data and filtered by:
* current airline
* rank
* type rating, if type-rating enforcement is enabled
* current location and preferred airport logic

If '''Schedule based on rank''' is enabled, FSFO automatically applies a maximum leg distance by rank:
* '''Rank 1''' - 350 NM
* '''Rank 2''' - 650 NM
* '''Rank 3''' - 1100 NM
* '''Rank 4''' - 1800 NM
* '''Rank 5''' - 3000 NM

FSFO first tries to build a schedule using that cap. If it cannot build a full schedule, it falls back to the full eligible route pool.

If '''Schedule based on rank''' is disabled, the Max NM value entered by the user is enforced strictly.

If '''Lock schedule until complete''' is enabled, FSFO will not generate a new schedule while an incomplete schedule already exists.

== Schedule Bidding System ==
When rank-based scheduling is enabled, FSFO scores route candidates and applies a bidding system.

Route scoring currently considers:
* base block-time value
* penalties for very short flights
* rank-based length bias
* preferred-airport bonuses

FSFO then divides scored routes into a preferred top bucket and a lower bucket.

The current rank-based bid chances are:
* '''Rank 1''' - 10%
* '''Rank 2''' - 35%
* '''Rank 3''' - 60%
* '''Rank 4''' - 90%
* '''Rank 5''' - 95%

If the bidding roll succeeds, FSFO selects from the top 30% of scored routes. Otherwise, it selects from the lower portion of the list.

== Preferred Airport ==
You can set a preferred airport for a company. FSFO uses that airport when generating schedules and gives preference to routes that end there, especially near the end of a generated trip.

== Route Map ==
After a schedule is generated, FSFO can build a route map from the loaded schedule legs and open it externally.

== When a Flight Counts Toward Progression ==
A flight does not automatically count toward career progression.

If '''Must fly scheduled flight''' is enabled, the flight must complete the '''next pending leg in order'''. FSFO compares:
* the actual flight number
* the actual departure airport
* the actual arrival airport

For the leg to count, the pilot must:
* start at the correct airport
* arrive at the correct airport
* match the next pending scheduled leg

If the flight does not meet that requirement:
* it can still be logged
* it will not increase Total Legs
* it will not update Average Score
* it will not reduce Contract Remaining Legs
* it will not update Balance
* it will not trigger promotion

If the next scheduled leg is completed correctly, it is marked '''COMPLETED'''. If that was the final remaining leg, the schedule is cleared.

== Flying a Career Flight ==
Before flight, FSFO captures:
* company
* flight number
* aircraft
* departure airport
* arrival airport

During flight, Career Mode monitors multiple operational and scoring categories.

Examples include:
* pitch exceedance
* bank exceedance
* G-force exceedance
* IAS exceedance
* taxi-speed exceedance
* light misuse
* fuel-management failures
* landing-performance issues

These events affect the total score and increment the appropriate error counters.

== Landing Score ==
Landing Score is based on:
* vertical speed
* G-force
* distance from the runway threshold

When runway data is available, the current weighting is:
* '''40%''' vertical speed
* '''30%''' G-force
* '''30%''' touchdown distance

If runway threshold data is unavailable, the distance portion is redistributed proportionally between vertical speed and G-force.

== Total Score and Qualification ==
Career Mode stores both:
* '''Landing Score'''
* '''Total Score'''

A flight is currently marked '''Qualified for Progression''' when the total score meets the system's qualification rule. The flight log stores that qualification result along with pay, fines, and error counts.

== Fatigue ==
If '''Enable fatigue''' is turned on, FSFO calculates fatigue from your recent workload using both:
* number of legs
* block hours

It evaluates three rolling workload windows:
* '''Last 24 hours'''
* '''Last 72 hours'''
* '''Last 7 days'''

The current formula is:

* '''Acute Load''' = max(legs in last 24h / 4, block hours in last 24h / 8)
* '''Short Load''' = max(legs in last 72h / 8, block hours in last 72h / 18)
* '''Weekly Load''' = max(legs in last 7d / 16, block hours in last 7d / 35)

Each load is clamped from 0 to 1.

Final fatigue:
* '''Fatigue = (Acute Load × 50) + (Short Load × 30) + (Weekly Load × 20)'''

The result is capped at 100 and rounded to the nearest whole percent.

If fatigue is above the allowed limit, Career Mode readiness should fail until workload decreases.

== Flight Log ==
The Flight Log is the permanent history of your career flights.

Each flight log entry stores:
* date
* company
* flight number
* aircraft
* from airport
* to airport
* block time
* landing score
* total score
* landing rate
* landing G
* block fuel
* critical/configuration/lights/speed error counts
* qualification result
* pay earned
* fines paid

Use the Flight Log window to review your performance over time.

== Notes ==
* Career Mode currently supports one local pilot profile
* The current schedule stores only the active trip
* The flight log is the permanent historical record
* The current '''Show Contract''' button is not implemented yet

== Troubleshooting ==
=== "PilotProfile was not found" ===
Create or rebuild the database, then apply to a company.

=== No schedule was generated ===
Check that:
* ''routes.csv'' exists
* the file format is valid
* routes match the current airline
* type-rating rules are not filtering everything out
* the requested leg count is realistic for the route pool

=== My flight did not count toward progression ===
If '''Must fly scheduled flight''' is enabled, verify that:
* you flew the next pending leg in order
* you started at the scheduled departure airport
* you arrived at the scheduled arrival airport
* the flight number matched when required

=== I cannot generate a new schedule ===
If '''Lock schedule until complete''' is enabled, finish the current schedule first or turn that option off.

[[Category:User Guide]]
[[Category:Career Mode]]

Troubleshooting

2026-03-22T00:15:28Z

Kingm56: /* Copilot does not move any switches */

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

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this page when something is not working as expected before contacting support.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Unless a section says otherwise, always start programs in this order: <strong>MSFS → FSUIPC7 → FSFO</strong>.
</div>

<span id="top"></span>
----

== Copilot does not move any switches ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.
</div>

=== 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.

[[File:FSUIPC7_Connected_Lvars.png|600x600px|FSUIPC7 showing connected state and available LVARs]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If the LVARs are missing (0 Lvars); please go to Step 4

If the menu is disabled (WASM is missing), please go to Step 5
</div>

=== Step 2: Verify FSFO is connected to FSUIPC7 ===

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

[[File:FSFO_FSUIPC_Status.png|450x450px|FSFO showing FSUIPC7 version in the status bar]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If no version is shown, FSFO is not connected.
</div>

=== 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.

[[File:FSFO_Aircraft_Profile.png|450x450px|Aircraft profile selection on Start Flight page]]

=== Step 4: LVARs fail to load: ===

# Make sure MSFS is fully loaded into the cockpit before starting FSFO.
# Confirm FSUIPC7 shows Connected to the simulator (step 1).
# If you are using a complex aircraft, give it extra time to finish loading its systems.
# Start FSFO '''AFTER''' FSUIPC7 is already connected.
# If the issue continues, close everything and restart in this order:
## Start MSFS and load into the cockpit.
## Start FSUIPC7 and confirm it shows Connected WITH LVARS LOADED (step 1) .
## Start FSFO last.

If the LVARs still do not load, adjust the FSUIPC WASM scan settings (last resort):

# Close MSFS, FSUIPC7, and FSFO.
# Open the FSUIPC_WASM.ini file in the WASM persistence/work folder.
# Do not edit the copy in the Community folder.
# Set the following values:
## LvarScanDelay=15 //Increase as needed...start with 15
## LvarScanFrequency=0

After saving the file, restart in this order:

# Start MSFS and load into the cockpit.
# Start FSUIPC7 and confirm it shows Connected.
# Start FSFO last.

LVARs still fail to load, check whether the FSUIPC WASM module crashed (move to step 5)
What these edits do:

* LvarScanDelay=15 gives the aircraft more time to finish initializing before FSUIPC scans for LVARs.
* LvarScanFrequency=0 disables repeated rescans, which can help if the WASM is unstable or LVARs stop updating.

=== Step 5: Reinstall FSUIPC7 if needed ===

If the steps above fail:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
After reinstall, start programs in this order:
<ol>
<li>Start MSFS and load into a cockpit.</li>
<li>Start FSUIPC7 and confirm it shows Connected.</li>
<li>Start FSFO last.</li>
</ol>
</div>

[[Troubleshooting#top|Back to top]]
----

== FSFO does not stay on top ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This behavior is caused by Windows process-level restrictions.
</div>

Reasons:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.
</div>

Workaround:

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #12 (FSUIPC_ERR_SENDMSG) ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
FSFO and FSUIPC7 must run at the same permission level.
</div>

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #2 ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This error indicates a failed or incomplete FSUIPC connection.
</div>

=== Common Cause ===

* FSUIPC7 is not running
* More than one FSUIPC7 instance is open
* Antivirus or firewall is blocking communication
* FSUIPC7 was installed in a protected folder
* FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

=== Quick Restart Sequence ===

# Close FSFO, FSUIPC7, and MSFS.
# Reboot Windows.
# Start MSFS and load fully into a cockpit.
# Start FSUIPC7 and confirm it is running.
# Start FSFO and click Connect.

=== Additional Checks ===

# Ensure only one instance of FSUIPC7 is running (review your system tray).
# Disable Auto-Connect in FSFO temporarily and connect manually.
# Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
# Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

=== Installation Checks ===

* Do not install FSUIPC7 inside Program Files or other protected Windows folders.
* Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
* If needed, reinstall FSUIPC7 and then restart the PC.
* After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
* If unresolved, perform a clean FSUIPC7 reinstall.

[[Troubleshooting#top|Back to top]]
----

== WASM version mismatch ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Error example: “WASM version X while WAPI expects Y”.
</div>

Recommended fix:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Manual fix (advanced users):
</div>

# Close FSFO, MSFS and FSUIPC7
# Go to www.fsuipc.com
# Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
# Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
# Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
# Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
# Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

[[Troubleshooting#top|Back to top]]
----

== <big>Aircraft-specific issues</big> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These issues apply only to specific aircraft or families.
</div>

=== FBW A320 or Headwind A330 – MCDU not programming ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Edit:
<pre>
Community\fsuipc-lvar-module\FSUIPC_WASM.ini
</pre>
Set:
<pre>
UseAirLocForHvars=Yes
</pre>
Save and restart MSFS.
</div>

----

=== Headwind A330 – FCU or MCDU not responding ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Copy:
<pre>
Community\fsuipc-lvar-module\modules\A320.hvar
</pre>
Rename the copy to:
<pre>
A330.hvar
</pre>
Restart MSFS.
</div>

----

=== PMDG aircraft – Enable SDK Data Broadcast ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<strong>Important:</strong> The aircraft must be loaded past the <strong>Ready to Fly</strong> screen at least once before these files exist.
</div>

# Exit Microsoft Flight Simulator.
# Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

==== MSFS 2020 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

==== MSFS 2024 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

# Open the <code>{aircraft_name}_Options.ini</code> file in a text editor such as Notepad.
# Add the following lines to the very end of the file:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
</pre>
</div>

# Save the file and restart Microsoft Flight Simulator.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
''Where <code>{username}</code> is your Windows username and <code>{aircraft_name}</code> is the specific PMDG aircraft you are using (for example, <code>737</code>).''
</div>

[[Troubleshooting#top|Back to top]]
----

== No English speech recognizer installed ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.
</div>

If English is not installed:

# Open Settings > Time & language > Language & region.
# Click Add a language.
# Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
# Select the English language > Next.
# Ensure Language pack and Speech are checked → Install.
# Restart Windows.

After restart, FSFO should detect an <code>en-*</code> recognizer.

If English is already listed or installed:

# Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
# Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

[[Troubleshooting#top|Back to top]]
----

== Voice recognition troubleshooting ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this section for microphone, permissions, and recognition accuracy problems.
</div>

'''Basic Checks:'''
* Microphone works?
** Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

* Privacy permissions (Windows 11):
** Settings > Privacy & security > Microphone
*** Microphone access: On
*** Let desktop apps access your microphone: On

* Correct input device
** Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

* No “exclusive mode” lock
** Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
*** Uncheck Allow applications to take exclusive control (as a test)

* Reasonable gain
** In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

'''English Speech Pack Installed (required):'''
* FSFO relies on English phrases. At least one English speech recognizer must be installed.
** Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
** Your Windows display language can be anything; only the English speech component is required.

'''Accuracy Tuning'''
* Lower <code>Input_VoiceAccuracy</code> if commands are missed.
* Increase it if false triggers occur.
* To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

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

[[Troubleshooting#top|Back to top]]
----

== No microphones found ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use these steps if FSFO shows no available input devices.
</div>

* '''Confirm Windows can see your mic'''
** Windows Settings > System > Sound > Input
** Select your microphone under Choose a device for speaking or recording
** Speak and verify the input level meter moves.
* '''Allow microphone permissions'''
** Windows Settings > Privacy & security > Microphone
** Turn ON:
*** Microphone access
*** Let apps access your microphone
*** Let desktop apps access your microphone
* '''Enable it in Control Panel (and set default)'''
** Open Control Panel > Sound > Recording
** Right-click your microphone > Enable
** Right-click it again > Set as Default Device
** (Optional) Set as Default Communication Device too.
* '''Basic Hardware Checks'''
** Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
** Unplug and replug, try a different USB port (avoid hubs while testing).
** If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

[[Troubleshooting#top|Back to top]]
----

== FSFO crashes ==

[[File:EventView.png|left|thumb|186x186px]]

<div style="margin-left:200px; margin-bottom:0.6em; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>When reporting crashes, include Windows Event Viewer logs.</strong>
</div>

# Type Event Viewer in the Windows Search Bar
# Click on the Event Viewer App
# Expand Windows Log > Expand Application
# Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
# Click The Details Tab, Copy and Email the contents to support

[[Troubleshooting#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
If your issue is not resolved after following the steps above, see [[Support]].
</div>

Troubleshooting

2026-03-16T17:18:48Z

Kingm56: /* FSUIPC Error #2 */

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

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this page when something is not working as expected before contacting support.
</div>

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Unless a section says otherwise, always start programs in this order: <strong>MSFS → FSUIPC7 → FSFO</strong>.
</div>

<span id="top"></span>
----

== Copilot does not move any switches ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.
</div>

=== 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.

[[File:FSUIPC7_Connected_Lvars.png|600x600px|FSUIPC7 showing connected state and available LVARs]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If LVARs are missing or the menu is disabled, the WASM module is not loaded.
</div>

=== Step 2: Verify FSFO is connected to FSUIPC7 ===

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

[[File:FSFO_FSUIPC_Status.png|450x450px|FSFO showing FSUIPC7 version in the status bar]]

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If no version is shown, FSFO is not connected.
</div>

=== 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.

[[File:FSFO_Aircraft_Profile.png|450x450px|Aircraft profile selection on Start Flight page]]

=== Step 4: Reinstall FSUIPC7 if needed ===

If the steps above fail:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
After reinstall, start programs in this order:
<ol>
<li>Start MSFS and load into a cockpit.</li>
<li>Start FSUIPC7 and confirm it shows Connected.</li>
<li>Start FSFO last.</li>
</ol>
</div>

[[Troubleshooting#top|Back to top]]
----

== FSFO does not stay on top ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This behavior is caused by Windows process-level restrictions.
</div>

Reasons:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.
</div>

Workaround:

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #12 (FSUIPC_ERR_SENDMSG) ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
FSFO and FSUIPC7 must run at the same permission level.
</div>

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

[[Troubleshooting#top|Back to top]]
----

== FSUIPC Error #2 ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
This error indicates a failed or incomplete FSUIPC connection.
</div>

=== Common Cause ===

* FSUIPC7 is not running
* More than one FSUIPC7 instance is open
* Antivirus or firewall is blocking communication
* FSUIPC7 was installed in a protected folder
* FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

=== Quick Restart Sequence ===

# Close FSFO, FSUIPC7, and MSFS.
# Reboot Windows.
# Start MSFS and load fully into a cockpit.
# Start FSUIPC7 and confirm it is running.
# Start FSFO and click Connect.

=== Additional Checks ===

# Ensure only one instance of FSUIPC7 is running (review your system tray).
# Disable Auto-Connect in FSFO temporarily and connect manually.
# Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
# Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

=== Installation Checks ===

* Do not install FSUIPC7 inside Program Files or other protected Windows folders.
* Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
* If needed, reinstall FSUIPC7 and then restart the PC.
* After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
* If unresolved, perform a clean FSUIPC7 reinstall.

[[Troubleshooting#top|Back to top]]
----

== WASM version mismatch ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
Error example: “WASM version X while WAPI expects Y”.
</div>

Recommended fix:

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

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Manual fix (advanced users):
</div>

# Close FSFO, MSFS and FSUIPC7
# Go to www.fsuipc.com
# Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
# Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
# Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
# Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
# Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

[[Troubleshooting#top|Back to top]]
----

== <big>Aircraft-specific issues</big> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
These issues apply only to specific aircraft or families.
</div>

=== FBW A320 or Headwind A330 – MCDU not programming ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Edit:
<pre>
Community\fsuipc-lvar-module\FSUIPC_WASM.ini
</pre>
Set:
<pre>
UseAirLocForHvars=Yes
</pre>
Save and restart MSFS.
</div>

----

=== Headwind A330 – FCU or MCDU not responding ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
Copy:
<pre>
Community\fsuipc-lvar-module\modules\A320.hvar
</pre>
Rename the copy to:
<pre>
A330.hvar
</pre>
Restart MSFS.
</div>

----

=== PMDG aircraft – Enable SDK Data Broadcast ===

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<strong>Important:</strong> The aircraft must be loaded past the <strong>Ready to Fly</strong> screen at least once before these files exist.
</div>

# Exit Microsoft Flight Simulator.
# Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

==== MSFS 2020 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

==== MSFS 2024 Work Folder (per aircraft) ====

'''Store / Xbox Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

'''Steam Version'''
<div style="margin:0.4em 0; padding:0.7em 0.9em; background:#fbfcff; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work
</pre>
</div>

# Open the <code>{aircraft_name}_Options.ini</code> file in a text editor such as Notepad.
# Add the following lines to the very end of the file:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1
</pre>
</div>

# Save the file and restart Microsoft Flight Simulator.

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
''Where <code>{username}</code> is your Windows username and <code>{aircraft_name}</code> is the specific PMDG aircraft you are using (for example, <code>737</code>).''
</div>

[[Troubleshooting#top|Back to top]]
----

== No English speech recognizer installed ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.
</div>

If English is not installed:

# Open Settings > Time & language > Language & region.
# Click Add a language.
# Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
# Select the English language > Next.
# Ensure Language pack and Speech are checked → Install.
# Restart Windows.

After restart, FSFO should detect an <code>en-*</code> recognizer.

If English is already listed or installed:

# Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
# Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

[[Troubleshooting#top|Back to top]]
----

== Voice recognition troubleshooting ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use this section for microphone, permissions, and recognition accuracy problems.
</div>

'''Basic Checks:'''
* Microphone works?
** Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

* Privacy permissions (Windows 11):
** Settings > Privacy & security > Microphone
*** Microphone access: On
*** Let desktop apps access your microphone: On

* Correct input device
** Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

* No “exclusive mode” lock
** Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
*** Uncheck Allow applications to take exclusive control (as a test)

* Reasonable gain
** In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

'''English Speech Pack Installed (required):'''
* FSFO relies on English phrases. At least one English speech recognizer must be installed.
** Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
** Your Windows display language can be anything; only the English speech component is required.

'''Accuracy Tuning'''
* Lower <code>Input_VoiceAccuracy</code> if commands are missed.
* Increase it if false triggers occur.
* To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

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

[[Troubleshooting#top|Back to top]]
----

== No microphones found ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Use these steps if FSFO shows no available input devices.
</div>

* '''Confirm Windows can see your mic'''
** Windows Settings > System > Sound > Input
** Select your microphone under Choose a device for speaking or recording
** Speak and verify the input level meter moves.
* '''Allow microphone permissions'''
** Windows Settings > Privacy & security > Microphone
** Turn ON:
*** Microphone access
*** Let apps access your microphone
*** Let desktop apps access your microphone
* '''Enable it in Control Panel (and set default)'''
** Open Control Panel > Sound > Recording
** Right-click your microphone > Enable
** Right-click it again > Set as Default Device
** (Optional) Set as Default Communication Device too.
* '''Basic Hardware Checks'''
** Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
** Unplug and replug, try a different USB port (avoid hubs while testing).
** If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

[[Troubleshooting#top|Back to top]]
----

== FSFO crashes ==

[[File:EventView.png|left|thumb|186x186px]]

<div style="margin-left:200px; margin-bottom:0.6em; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>When reporting crashes, include Windows Event Viewer logs.</strong>
</div>

# Type Event Viewer in the Windows Search Bar
# Click on the Event Viewer App
# Expand Windows Log > Expand Application
# Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
# Click The Details Tab, Copy and Email the contents to support

[[Troubleshooting#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
If your issue is not resolved after following the steps above, see [[Support]].
</div>

Release Notes

2026-03-16T16:26:50Z

Kingm56: /* Fixed */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.16.0
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----

== <span>Version 6.0.17.0</span> ==

==== Added ====

* Ray Munich's German region pack (it's named German, the default was renamed to German2)
* Wait_For_AGL option
* Wait_For_MSL option.

==== Fixed ====

* Resolved the AGL issue with the User AutoFlows option
* PMDG 737 weather radar not responding to the OFF command
* Fenix A320 incorrectly asking to connect the GPU when the command was to disconnect it while using SAPI
* Missing “Gear Up” callout during takeoff
* Multiple spelling errors on the First Officer and Captain .wav files
* Missing crew (flight attendant) wav files from Ray Munich's regions (sound files)
* User AutoFlow no longer triggers when merely crossing a runway; the aircraft must now be within 800 feet of the runway threshold.
* Lights AutoFlow no longer triggers simply from turning on the landing lights; the aircraft must now be within 800 feet of the runway threshold.
* Reduced runway confirmation distance from 1,500 feet to 750 feet from the runway threshold to reduce false readings.
* Issue where the approach briefing could read non-whole-number values for the approach course.
* Issue where cabin service could start and then stop immediately.
* Issue on the SOPs page where the program could ask you to confirm stopping a flow even when no flow was running.
* IniBuilds A350 Nav light being reported as Off, when it was still On
* RAAS issue where inaccurate "On Taxiway" calls when tailwinds caused IAS to exceed the threshold.
* New Altitude was not set when the aircraft was within 5nm of Top of Descent

==== Changed ====

* Updated the v-speed sync method; registered V-speeds must now be above 100 knots
* Increased the fuel management penalty from 25% to 35%
* On the SOP Controls page, VATSIM and weather information will now be displayed in the Alerts box whenever a checklist or flow is not running.
* Voice command Wipers On will result in a middle vice high setting
* Flight Attendants will now announce they are starting cabin services

== <span>Version 6.0.16.0</span> ==

==== Fixed ====

* Erroneous “Fired” message box that appeared at the end of the Shutdown Flow
* Issue where deboarding was announced before shutdown was complete
* Erroneous “Check the Flaps” callout on landing in the Fenix A320
* Issue where user-defined airborne triggers were not working

==== Changed ====

* Brakes are no longer required for the "stabilized" call; however, the Lineup/Takeoff Flow and Checklist must still be completed

== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Default NavData contained the incorrect Runway Heading
* Gear Up was not call on Takeoff
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* GSX Deboarding failed to correctly sync
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)
* Smart/Light Auto Flows - Boarding most also be completed before the Before Start will start

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.
* Checklist/Briefing - Will no longer be on a timer; simply say ready for the checklist or ready for the briefing when ready, press ctrl+alt, or your bypass key

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-03-15T20:27:00Z

Kingm56: /* Version 6.0.17.0 */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.16.0
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----

== <span>Version 6.0.17.0</span> ==

==== Added ====

* Ray Munich's German region pack (it's named German, the default was renamed to German2)
* Wait_For_AGL option
* Wait_For_MSL option.

==== Fixed ====

* Resolved the AGL issue with the User AutoFlows option
* PMDG 737 weather radar not responding to the OFF command
* Fenix A320 incorrectly asking to connect the GPU when the command was to disconnect it while using SAPI
* Missing “Gear Up” callout during takeoff
* Multiple spelling errors on the First Officer and Captain .wav files
* Missing crew (flight attendant) wav files from Ray Munich's regions (sound files)
* User AutoFlow no longer triggers when merely crossing a runway; the aircraft must now be within 800 feet of the runway threshold.
* Lights AutoFlow no longer triggers simply from turning on the landing lights; the aircraft must now be within 800 feet of the runway threshold.
* Reduced runway confirmation distance from 1,500 feet to 750 feet from the runway threshold to reduce false readings.
* Issue where the approach briefing could read non-whole-number values for the approach course.
* Issue where cabin service could start and then stop immediately.
* Issue on the SOPs page where the program could ask you to confirm stopping a flow even when no flow was running.
* IniBuilds A350 Nav light being reported as Off, when it was still On

==== Changed ====

* Updated the v-speed sync method; registered V-speeds must now be above 100 knots
* Increased the fuel management penalty from 25% to 35%
* On the SOP Controls page, VATSIM and weather information will now be displayed in the Alerts box whenever a checklist or flow is not running.

== <span>Version 6.0.16.0</span> ==

==== Fixed ====

* Erroneous “Fired” message box that appeared at the end of the Shutdown Flow
* Issue where deboarding was announced before shutdown was complete
* Erroneous “Check the Flaps” callout on landing in the Fenix A320
* Issue where user-defined airborne triggers were not working

==== Changed ====

* Brakes are no longer required for the "stabilized" call; however, the Lineup/Takeoff Flow and Checklist must still be completed

== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Default NavData contained the incorrect Runway Heading
* Gear Up was not call on Takeoff
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* GSX Deboarding failed to correctly sync
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)
* Smart/Light Auto Flows - Boarding most also be completed before the Before Start will start

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.
* Checklist/Briefing - Will no longer be on a timer; simply say ready for the checklist or ready for the briefing when ready, press ctrl+alt, or your bypass key

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Advanced Users Guide

2026-03-14T19:12:16Z

Kingm56: /* Manually Update Smart Flow Options */

This guide is intended for advanced FSFO users who want to manually customize SOPs, create their own flows and checklists, tune Smart Flows, and manage the FSFO airport database.

<span id="top"></span>

== <span id="SOP_File_Location">SOP File Location</span> ==
All SOPs are stored in:

C:\Users\[Your Name]\AppData\Local\FSFO_V6\FlowsChk

Replace '''[Your Name]''' with your Windows user name.

Each SOP file must begin with two required header lines:<pre>
type;AIRBUS;;
user;;;
</pre>

* The first line identifies the aircraft type (BOEING or AIRBUS).
* The second line is reserved for user-generated flows and checklists.

[[Advanced Users Guide#top|Back to top]]
== <span id="SOP_File_Structure">SOP File Structure</span> ==
Each line in an SOP file uses the following structure:<pre>
Phase;Type;System;Response
</pre>Example:<pre>
1;1;Auto_Brakes;MAX
</pre>Where:

* Phase = Flight phase number
* Type = Flow or Checklist
* System = Target system or command
* Response = Desired value or action

[[Advanced Users Guide#top|Back to top]]
== <span id="Phases">Phases</span> ==
The following numeric values define flight phases:<pre>
1 = Preflight or Cockpit Preparation
2 = Before Start
3 = Engine Start
4 = After Start
5 = Taxi
6 = Before Takeoff or Lineup
7 = After Takeoff
8 = Descent
9 = Approach
10 = Landing
11 = After Landing
12 = Shutdown or Parking
13 = Runway Change
100 = Turn Around
14 = User Defined
15 = User Defined
16 = User Defined
</pre>
[[Advanced Users Guide#top|Back to top]]
== <span id="Types">Types (Flow vs Checklist)</span> ==
<pre>
1 = Flow
2 = Checklist
</pre>

'''Flow''' A memorized, spatial sweep of switches and controls used to configure the aircraft. Flows are fast, heads-up, and done from memory.

'''Checklist''' A short, written challenge-response used to verify critical items are correctly set.

How they work together:

* Normal operations: Flow → Checklist
* Abnormal or emergencies: Use QRH or abnormal checklist

The flow performs the actions, the checklist verifies them.

[[Advanced Users Guide#top|Back to top]]
== <span id="Creating_Custom_Flows">Creating Custom Flows and Checklists</span> ==
Always create a backup copy of your SOP file before making manual edits.

To add user-defined flows (for example: Single Engine and Go-Around):

Update the second line of your SOP file:<pre>
type;AIRBUS;;
user;Single_Eng;Go_Around;
</pre>Then add new phase lines at the end of your file:<pre>
13;2;Takeoff_Speeds;READBACK
13;2;Altitude;READBACK

14;2;Action;Value
14;2;Action;Value

15;2;Action;Value
15;2;Action;Value
</pre>Mapping:

* Phase 14 = Supplemental Flow One
* Phase 15 = Supplemental Flow Two
* Phase 16 = Supplemental Flow Three

Voice commands:

* “Supplemental checklist one”
* “Supplemental flow one”
[[Advanced Users Guide#top|Back to top]]

== <span id="Types">Set Commands</span> ==
<pre>PACKS: Sets packs according to the option selected on the FSFO Departure Performance page.
ALTITUDE: Sets the autopilot altitude to the Initial Altitude (or Planned Altitude) selected on the FSFO Flight Plan page.
HEADING: Sets the heading bug to the departure runway heading selected on the FSFO Departure Performance page.
AIRSPEED: Sets IAS to the V2 speed entered on the FSFO Departure Performance page.
AUTO_BRAKES: Sets according to the option selected on the FSFO Arrival Performance page.
FLAPS: Sets according to the option selected on the FSFO Departure Performance page.
COCKPIT_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
DOME_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
WING_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
ANTI-ICE: Turns ENGINE_ANTI_ICE and WING_ANTI_ICE ON when OAT < 10°C and precipitation is detected; otherwise OFF.</pre>

A SET Commands used during the flows will result in the above.

[[Advanced Users Guide#top|Back to top]]

== <span id="Flow_Commands">Flow Commands Explained</span> ==

=== LVAR ===
This command is intended for advanced users who are comfortable working with MSFS Local Variables (LVARs) and know how to acquire and use them. To use it, add the LVAR command, then enter the LVAR name, an equals sign (<code>=</code>), and the desired value/state (i.e., <code>LVAR_NAME=VALUE</code>). FSFO also supports PMDG Rotor Brake commands (Toggle and Push Only) by using the <code>ROTOR_BRAKE</code> option after <code>LVAR</code> in the format <code>ROTOR_BRAKE=<SwitchID>=<Label></code>. For example: <code>1;1;LVAR;ROTOR_BRAKE=101=Battery;</code> — in this case, <code>ROTOR_BRAKE</code> tells FSFO to use the Rotor Brake command type, <code>101</code> is the SwitchID, and <code>Battery</code> is the label that will be displayed (and spoken) on the SOPs page.

Format:<pre>
1;1;LVAR;XMLVAR_StandbyPower_Selector=1=Standby Power
1;1;LVAR;ROTOR_BRAKE=101=Battery
</pre>Meaning:

* XMLVAR_StandbyPower_Selector = LVAR name
* 1 = value
* Standby Power = Label that will be displayed (and spoken) on the SOPs page
Rotor_Brake Meaning:

* <code>ROTOR_BRAKE</code> = Tells FSFO to use the Rotor Brake command type
* 101 = SwitchID
* Battery = Label that will be displayed (and spoken) on the SOPs page

----

=== SIMVAR ===
Used to control MSFS Simulation Variables.

Format:<pre>
1;1;SIMVAR;67271=1=Parking Brake
</pre>Meaning:

* SIMVAR = Tells FSFO to use the SIMVAR command type
* 67271 = SIMVAR control number (complete list here: [[SIMVAR Control Numbers]])
* 1 = value (ON)
* Parking Brake = abel that will be displayed (and spoken) on the SOPs page

----

=== Play_Sapi_Copilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Copilot voice selected in Settings. If no Copilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Sapi_Pilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Pilot voice selected in Settings. If no Pilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Wav ===
Plays a WAV file. You must enter the full path of the wav file.

Format:<pre>
1;1;Play_Wav;C:\Users\name\FSFO\boarding_Noise.wav
</pre>
----

=== Misc_Text ===
Displays reminder text under the Pilot section.

Example:<pre>
1;1;Misc_Text;Start ACARS
</pre>
----

=== Capt_Actions ===
Displays reminder text under the Captain Actions section.
----

=== Flight_Plan ===
Loads the most recent flight plan from:

C:\Users\[name]\AppData\Local\FSFO_V6\Download
----

=== Landing_Data ===
Reads back minimums and Vref speeds.
----

=== Fuel ===

* Load = FSFO will load the fuel amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Payload ===

* Load = FSFO will load the payload amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Loadsheet ===

* Confirm = Ground crew will confirm the aircraft is under Max Takeoff Weight (MTOW). If it is over MTOW, they will warn you and request that you check your loadsheet.

----

=== Doors ===

* Toggle_0 through Toggle_6 = Will open/close the doors; for example, Toggle_1 will open/close the 1L(Main) Door on most aircraft.

----

=== Walk_Around ===
While the default values are SHORT, MED, and LONG, advanced users can open the SOP text file and enter any numeric value (seconds) they like for the copilot to perform the walk-around. As an example:<pre>
1;1;WALK_AROUND;965
</pre>Defaults:

* SHORT = 150 seconds
* MED = 300 seconds
* LONG = 600 seconds

[[Advanced Users Guide#top|Back to top]]
== <span id="Smart_Flow_Tuning">Manually Update Smart Flow Options</span> ==
You can still manually update your SMART AutoFlow options by updating the userSettings.cfg file by following these steps:

# Close FSFO
# Navigate to C:\Users\[Your Name]\AppData\Local\FSFO_V6\UserData Folder
## You can also just click on the UserData button on FSFO’s front page
# Right-Click on userSettings.cfg and click Open with Notepad
# Locate and edit these lines: '''ensure no trailing white space or empty lines'''
<pre>
Flows_PreFltStart=10
Flows_BeforeTakeoffStart=800
Flows_AfterTakeoffStart=3000
Flows_DescentStart=20
Flows_ApproachStart=10000
Flows_LndgStart=1500
</pre>Units:<pre>
Flows_PreFltStart = Seconds
Flows_BeforeTakeoffStart = Feet to runway threshold
Flows_AfterTakeoffStart = AGL feet
Flows_DescentStart = Nautical miles
Flows_ApproachStart = AGL feet
Flows_LndgStart = AGL feet
</pre>
[[Advanced Users Guide#top|Back to top]]
== <span id="Airport_Database">FSFO Airport Database Tool</span> ==
FSFO Make Runway is a separate program that builds the runway database using SIMCONNECT and MSFS APIs.

=== Installation ===
You can install it in two ways:

# From FSFO
## Click '''Get Started''' on the FSFO main page
## Click '''MAKE RWY''' on the New User window
## Follow the installation instructions
# Manually:
## Navigate to *\Flight Simulator First Officer V6\Res\Exe
### * represents your FSFO V6 directory; just right-click on the Flight Simulator First Officer V6 shortcut and select "Open File Location"
## Right-Click '''FSFO_Make_Runway.exe''' and Select "Run as Administrator"

----

=== Building the Database ===
[[File:MakeRwy.png|left|thumb]]

# Start MSFS or MSFS24 and load into the cockpit
# Click '''FSFO NAV PATH''' and select the FSFO NavData folder
# Click '''Connect'''
# Click '''Build'''

'''Note: This process can take over two hours.'''

----

=== Manual Database Updates ===
Runway data file:

* *\FSFO_V6\NavData\runways.csv
[[File:AirportDb.png|left|thumb|419x419px]]

'''Note 1 (Runway Code)''':
* Stored as a 3-digit code where the last digit indicates the side:
** 0 = none
** 1 = Left (L)
** 2 = Right (R)
** 3 = Center (C)
** 4 = Water (W)

* Examples:
** 330 = Runway 33
** 331 = Runway 33L
** 332 = Runway 33R
** 333 = Runway 33C
** 090 = Runway 9
** 091 = Runway 9L

'''Note 2 (Latitude/Longitude format):'''

* Lat/Lon values must be in decimal degrees (DD) format (example: 42.193545).
* Threshold lat/lon represent the runway threshold (AFCAD “runway start”).
'''Note 3 (Feet):'''

* Elevation, length, width, and threshold offset values are (must be) in feet.

'''Note 4 (Heading):'''

* Runway heading is the magnetic runway heading.

'''Note 5 (ILS frequency):'''

* ILS frequency is stored as nnn.nn (example: 109.50) or 0 if no ILS is available.

'''Note 6 (Magnetic variation):'''

* Magnetic variation (in degrees) is the value applied to convert magnetic to true heading: True Heading = Magnetic Heading + Magnetic Variation

[[Advanced Users Guide#top|Back to top]]
----

For standard setup and everyday operation, see [[Getting Started]] and [[User Settings Reference]].

Release Notes

2026-03-14T16:39:16Z

Kingm56: /* Version 6.0.16.0 */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.16.0
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----

== <span>Version 6.0.17.0</span> ==

==== Fixed ====

* Resolved the AGL issue with the User AutoFlows option
* PMDG 737 weather radar not responding to the OFF command
* Fenix A320 incorrectly asking to connect the GPU when the command was to disconnect it while using SAPI
* Missing “Gear Up” callout during takeoff
* Multiple spelling errors on the First Officer and Captain .wav files
* Missing crew (flight attendant) wav files from Ray Munich's regions (sound files)

==== Changed ====

* Updated the v-speed sync method; registered V-speeds must now be above 100 knots
* Increased the fuel management penalty from 25% to 35%

== <span>Version 6.0.16.0</span> ==

==== Fixed ====

* Erroneous “Fired” message box that appeared at the end of the Shutdown Flow
* Issue where deboarding was announced before shutdown was complete
* Erroneous “Check the Flaps” callout on landing in the Fenix A320
* Issue where user-defined airborne triggers were not working

==== Changed ====

* Brakes are no longer required for the "stabilized" call; however, the Lineup/Takeoff Flow and Checklist must still be completed

== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Default NavData contained the incorrect Runway Heading
* Gear Up was not call on Takeoff
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* GSX Deboarding failed to correctly sync
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)
* Smart/Light Auto Flows - Boarding most also be completed before the Before Start will start

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.
* Checklist/Briefing - Will no longer be on a timer; simply say ready for the checklist or ready for the briefing when ready, press ctrl+alt, or your bypass key

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-03-06T22:14:27Z

Kingm56: /* Release Notes */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.16.0
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----

== <span>Version 6.0.16.0</span> ==

==== Fixed ====

* Erroneous “Fired” message box that appeared at the end of the Shutdown Flow
* Issue where deboarding was announced before shutdown was complete
* Erroneous “Check the Flaps” callout on landing in the Fenix A320
* Issue where user-defined airborne triggers were not working

==== Changed ====

* Brakes are no longer required for the "stabilized" call; however, the Lineup/Takeoff Flow and Checklist must still be completed

== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Default NavData contained the incorrect Runway Heading
* Gear Up was not call on Takeoff
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* GSX Deboarding failed to correctly sync
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)
* Smart/Light Auto Flows - Boarding most also be completed before the Before Start will start

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.
* Checklist/Briefing - Will no longer be on a timer; simply say ready for the checklist or ready for the briefing when ready, press ctrl+alt, or your bypass key

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-03-06T22:14:10Z

Kingm56:

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.14.1
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----

== <span>Version 6.0.16.0</span> ==

==== Fixed ====

* Erroneous “Fired” message box that appeared at the end of the Shutdown Flow
* Issue where deboarding was announced before shutdown was complete
* Erroneous “Check the Flaps” callout on landing in the Fenix A320
* Issue where user-defined airborne triggers were not working

==== Changed ====

* Brakes are no longer required for the "stabilized" call; however, the Lineup/Takeoff Flow and Checklist must still be completed

== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Default NavData contained the incorrect Runway Heading
* Gear Up was not call on Takeoff
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* GSX Deboarding failed to correctly sync
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)
* Smart/Light Auto Flows - Boarding most also be completed before the Before Start will start

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.
* Checklist/Briefing - Will no longer be on a timer; simply say ready for the checklist or ready for the briefing when ready, press ctrl+alt, or your bypass key

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

User Settings Reference

2026-02-26T22:57:48Z

Kingm56: /* Auto Flow Policy */

This section summarizes FSFO’s configurable user settings. Setting names and behaviors mirror the in-app User Settings pages.

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
This page is a reference, not a step-by-step guide. Use it to look up what each setting does.
</div>

<span id="top"></span>

----

== Input and Output ==

* '''Pilots'''

Choose the playback device (headset, speakers, etc.) for pilot and copilot voices.

* '''Cabin Crew'''

Choose the playback device for cabin crew announcements. Use a different device to simulate distance.

* '''Region'''

Sets the accent for all voices.

* '''Speech Engine'''

Available speech recognition engines:

; Microsoft

<div style="margin:0.4em 0; padding:0.6em 0.8em; background:#f4f9f6; border-left:4px solid #5cb85c;">
Highest accuracy. Uses your Windows default microphone automatically. This is the officially supported FSFO speech recognition engine.
</div>

To change which microphone is used: Settings > System > Sound > Input

You must have an English speech recognition pack installed: Settings > Time & Language > Language & Region > Add a language > Speech

<div style="margin:0.4em 0; padding:0.6em 0.8em; background:#eef3fb; border-left:4px solid #1f4fa3;">
Tip: Accuracy is highest for English (US).
</div>

; VOSK

<div style="margin:0.4em 0; padding:0.6em 0.8em; background:#fdf7f2; border-left:4px solid #f0ad4e;">
Works offline, supports multiple languages, and can use any input device. Less accurate than Microsoft. Experimental and not officially supported.
</div>

; SAPI

Lets you pick any installed SAPI voice for Pilot, Copilot, and Cabin Crew.

* '''SAPI Rate'''

Controls how fast SAPI voices speak.

[[User Settings Reference#top|Back to top]]

----

== Audio and Recognition Tuning ==

* '''Pilots Volume'''

Loudness of pilot and copilot voices.

* '''Crew Volume'''

Loudness of cabin crew voices.

* '''Ambiance Volume'''

Loudness of background noise.

* '''Pilots dB Gain'''

Adds or subtracts decibels to pilot audio before the Volume slider is applied.

* '''Amb dB Gain'''

Adds or subtracts decibels to ambiance audio before the Ambiance Volume slider is applied.

* '''Readback'''

Length of pauses between digits or characters.

* '''Distort Voice'''

Adds headset or intercom distortion.

* '''Static Voice'''

Adds background static.

* '''Open Mic'''

When checked, recognition always listens unless muted.

* '''Start Speech on Start'''

When checked, recognition activates automatically when FSFO starts.

[[User Settings Reference#top|Back to top]]

----

== Test Options ==

* '''Pilot Test'''

Both pilots say “Fuel” plus a number.

* '''Crew Test'''

Plays a standard cabin announcement.

* '''Test Boarding Music'''

Tests boarding music volume.

* '''Test Boarding Ambiance'''

Tests background ambiance volume.

[[User Settings Reference#top|Back to top]]

----

== Controller and Hot-Key Setup ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Available actions:
</div>

* '''Mute'''
Toggles voice recognition on/off

* '''PTT'''
If Open Mic is ON, holding PTT mutes voice recognition; if Open Mic is OFF, holding PTT activates recognition.

* '''Bypass'''
Cancels a wait or skips a checklist item (Ctrl + A is default).

* '''Pause'''
Pauses all FSFO actions until pressed again.

* '''GUID'''
Displays the controller Globally Unique Identifier.

* '''Set Button'''
Click then press the desired button or key.

* '''Clear Button'''
Removes the highlighted binding.

* '''Train Speech'''
Opens the Speech Trainer to improve recognition accuracy.

* '''Check For Update'''
Checks for the latest FSFO version.

* '''Delete Button'''
Deletes controllers.cfg (all saved bindings).

[[User Settings Reference#top|Back to top]]

----

== <span id="Standard_Operating_Procedures">Standard Operating Procedures (SOP)</span> ==

<div style="margin:0.8em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e;">
<strong>NOTE:</strong> Above Ground Level (AGL) vs Mean Sea Level (MSL)
</div>

* '''''AGL''' (Above Ground Level) is your aircraft’s height '''above the terrain directly below you'''.''
* '''''MSL''' (Mean Sea Level) is your altitude '''above average sea level'''.''

<div style="margin:0.6em 0; padding:0.6em 0.8em; background:#eef3fb; border-left:4px solid #1f4fa3;">
FSFO will trigger the actions listed below when the aircraft reaches the specified AGL or MSL value. Setting a value to 0 disables that trigger.
</div>

<u>OPTIONS:</u>
* '''Acceleration Altitude (AGL)'''

Copilot calls “Acceleration Altitude” once this altitude is reached after takeoff.

* '''Landing Lights (MSL)'''

Copilot toggles landing lights at this altitude.

* '''Engage VNAV (AGL)'''

Copilot engages vertical navigation mode.

* '''Engage LNAV (AGL)'''

Copilot engages lateral navigation mode.

* '''Engage AP (AGL)'''

Copilot engages the autopilot.

* '''Engage APPR (AGL)'''

Copilot engages approach mode during landing.

* '''Disconnect AT (AGL)'''

Copilot disconnects autothrottle during landing.

* '''Disconnect AP (AGL)'''

Copilot disconnects autopilot during landing.

* '''Extend Gear (AGL)'''

Copilot extends landing gear during landing.

* '''Min Flap Extension (AGL)'''

Minimum altitude at which copilot deploys flaps.

* '''Grnd Speed Warn (MPH)'''

Warns when ground speed exceeds this value.

* '''Stabilized Call (N1)'''

Copilot calls “Stabilized” when engines reach this N1%.

* '''Flow Pause (sec)'''

Description coming soon

* '''Checklist Pause (sec)'''

Description coming soon

* '''Checklist Repeat (sec)'''

Description coming soon

* '''Passing Call (MSL)'''

Copilot calls “Passing X feet” during climb or descent.

* '''Couple Taxi Lndg Lights'''

Yes, FSFO will automatically turn the taxi lights on/off to match your landing lights

* '''Couple Wing Logo Lights'''

Yes, FSFO will automatically turn the wing lights on/off to match your logo lights

* '''Manage Ground Lights'''

Copilot will manage the lights when the aircraft is on the ground:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
- When power is established, the copilot turns on the NAV Lights

- When engines are running, the copilot turns on the Beacon Lights

- When the aircraft ground speed exceeds 5 MPH, the copilot will turn on Taxi Lights

- When the aircraft is on any runway, the copilot will turn on the Landing, Strobe, and Wing Lights; when the aircraft exits the runway, he will turn them off
</pre>
</div>

* '''Battery Equal Turn Around'''

IF the power is on when FSFO is connected, the copilot will consider the current flight as a subsequent flight.

* '''Boarding Music'''

Select the boarding music, which can be played via “Boarding_Music” command via the flow and checklist editor, or by click ing the music icon via the control options, which can be accessed on the Checklist page. You can also download and play your own boarding music, as long as its a.wav file. Place your wav files in the following directory: C:\Users\[USER NAME] \AppData\Local\FSFO_V6\ Music..

* '''Safety Message'''

Select the safety message, which can be played via “Safety_Message” command via the flow and checklist editor, or by clicking the life jacket icon, which can be accessed on the SOPs page. You can also download and play your own safety messages, as long as it's a *.wav file. Place your wav files in the following directory: C:\Users\ [USER NAME]\AppData\Local\FSFO_V6 \Safety.

* '''Flaps Call'''

Controls flap callout behavior:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
- Flaps Setting:
The copilot will call the new flaps setting (e.g. Flaps 5)

- Speed Check:
The copilot will call “Speed Check” when a flap change is detected

- Speed Chk + Flap:
The copilot will call “Speed Check”, then the flaps setting when a flap change is detected
(e.g. Speed Check, Flaps 10)
</pre>
</div>

* '''VSpeed Call'''

Controls V-speed callouts:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
- None:
No V-speeds are called

- V1 + VR:
Both V1 and Rotate are called during the takeoff roll

- VR:
Only Rotate is called during the takeoff roll
(useful for aircraft that have automated V1 callouts)
</pre>
</div>

[[User Settings Reference#top|Back to top]]

== <span id="Auto_Flow_Options">Auto Flow Policy</span> ==

FSFO has three auto flow polices for you to select. Depending on the policy, FSFO will automatically initiate a flow/checklist based on the criteria below:

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<div style="font-weight:bold; color:#1f4fa3; margin-bottom:0.4em;">LIGHTS</div>
<pre>
- Pre-Flight/Cockpit Prep: Initiated when Navigation (NAV) Lights are Turned On

- Before Start: Initiated when Boarding or Loading is completed and Beacon Lights are Turned On

- Engine Start: Initiated 60 seconds after push back is detected

- After Start: Initiated when engines are running and stable with parking brakes On (It may take up to 3 mins for the engines to stabilize)

- Taxi Flow: Initiated when Taxi Lights are Turned On

- Before Takeoff/Lineup Flow: Initiated when Landing Lights are Turned On

- After Takeoff/Acceleration Flow: Initiated when Aircraft is above 3000 feet Above Ground Altitude

- Descent Flow: Initiated when the aircraft is within 20 Nautical Miles from the Top of Descent

- Approach Flow: Initiated when Landing Lights are Turned On

- Landing Flow: Initiated when the aircraft is below 1500 feet Above Ground Altitude

- After Landing Flow: Initiated when the aircraft’s Landing Lights are Turned Off

- Parking/Shutdown Flow: Starts when Taxi Lights are Turned Off and Parking Brake is Set
</pre>
</div>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<div style="font-weight:bold; color:#2f7a2f; margin-bottom:0.4em;">SMART</div>
<pre>
- Pre-Flight/Cockpit Prep: Initiated after 10 seconds from starting your flight*

- Before Start: Initiated when Boarding or Loading is completed and all doors are closed

- Engine Start: Initiated 60 seconds after push back is detected

- After Start: Initiated when engines are running and stable with parking brakes On (It may take up to 3 mins for the engines to stabilize)

- Taxi Flow: Initiated when the After Start Phase is completed and the parking brake is released

- Before Takeoff/Lineup Flow: Initiated when Aircraft is within 800 feet of the runway threshold

- After Takeoff/Acceleration Flow: Initiated when Aircraft is above 3000 feet Above Ground Altitude

- Descent Flow: Initiated when the aircraft is within 20 Nautical Miles from the Top of Descent

- Approach Flow: Initiated when the aircraft is below 10000 feet Above Ground Altitude

- Landing Flow: Initiated when the aircraft is below 1500 feet Above Ground Altitude

- After Landing Flow: Initiated when the aircraft leaves the runway

- Parking/Shutdown Flow: Starts when Taxi Lights are Turned Off and Parking Brake is Set
</pre>
</div>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<div style="font-weight:bold; color:#b26a00; margin-bottom:0.4em;">USER</div>
<pre>
Selecting the user setting allows you to choose any event, time, lights, system, or condition to trigger your flow
</pre>
</div>

[[User Settings Reference#top|Back to top]]

----

== Crew Options ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Settings that control copilot and cabin crew behavior, callouts, and automation.
</div>

* '''Attendant Messages'''

The Flight Attendant will make the following announcements:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
- Pre-Flight “Boarding complete” (intercom to First Officer

- Taxi-Out Advise passengers to switch devices to airplane mode (above 11 MPH).

- Airborne > 10,000 ft: Passengers free to use electronics.

- Descent < 12,000 ft: Advise stowage of electronics (You must complete the Descent phase).

- Taxi-In Welcome passengers to destination.

Shutdown “ Deboarding complete” (intercom).
</pre>
</div>

* '''Pilot Messages'''

The First Officer will make the following announcements:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#f4f9f6; border-left:6px solid #5cb85c; border-radius:8px;">
<pre>
- Taxi-Out Time-of-day welcome message (5 seconds after the Taxi Phase is completed).

- Reaching Cruise Altitude Inform passengers of cruise.

- Descent (4 000 ft below cruise) Announce start of descent (You must complete the Descent phase).
</pre>
</div>

* '''Apply Brakes'''

Copilot applies brakes above 28 MPH.

* '''Set Landing Gear'''

Copilot raises or lowers gear; If you wish for the copilot to only raise the gear, set the SOP Extend Gear (AGL) option to 0.

* '''Set Flaps'''

Copilot retracts or extends flaps; If you wish for the copilot to only retract the flaps, set the SOP Min Flap Extension (AGL) option to 0.

* '''Set Altimeter'''

Copilot sets standard and local pressure.

* '''Set Seatbelts'''

Copilot will turn OFF the seatbelts at Top of Climb and ON atTop of Descent

* '''Set Ctr Fuel Tanks'''

Copilot disables center tanks below threshold (7,000 pounds for heavy; otherwise, 1,000 pounds).

* '''Set Lights'''

Copilot will turn off/on the landing lights when aircraft is above/below the Passing Call (MSL) setting via the SOP option; otherwise 10000 feet will be used.

* '''Repeat Readback'''

Copilot will repeat the values stated by the pilot during a voice command. For example, if you command Heading 242, the copilot will repeat the command "Heading 2-4-2."

* '''Confirm Checklist Item'''

Copilot will ensure the system is set correctly during the checklist phase, when using the voice options. If it's not set according to the checklist, your copilot will ask you to check the system again.

* '''First Ofcr Handles Intercom'''

Copilot will automatically handle all intercom messages and prompts (e.g., cabin/ground/crew calls) without requiring your input. If disabled, the captain (you) must answer the intercom phone and respond to prompts by selecting Yes or No in the on-screen dialogue window.

* '''Call Missed Checklist'''

Copilot will alert you when you missed a checklist. For example, if the engines are running, and you failed to complete the Before Start Flow/Checklist, your copilot will ask: “Did we complete the Before Start Checklist”?

* '''Call Roll Phrases'''

Copilot will execute takeoff and landing roll callouts (e.g. stabilized, thrust set, 80 knots, reverse green, manual braking, etc…).

* '''Call Roll Responses'''

Pilot will respond to the copilot takeoff/rollout calls. For example, when the copilot states 80/100 knots, the pilot will respond “checked.” Disable if you prefer to respond yourself.

* '''Call 400 Feet'''

Copilot will call 400 feet when the aircraft reaches this Above Ground Altitude (AGL) during the climb phase. This is useful for engaging the appropriate vertical navigation mode.

* '''Call Minimums'''

Copilot will call out minimums when the aircraft descends below the AGL identified on the departure performance page (the default is 200 ft AGL).

* '''Call Glide Slope Alive'''

Copilot will call “glide slope alive” when he detects movement on the glide slope needle, and “Glide Slope Captured” when the aircraft captures the glide slope.

* '''Call System Changes'''

Copilot will alert the captain to changes (e.g. flaps five, gear up, parking brake set, etc..) of the following key systems:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3; border-radius:8px;">
<pre>
- Landing Gear

- Flaps

- Parking Brake

- Spoilers (When Armed/Disarmed)

- Lateral Navigation (LNAV, Managed Mode, Heading Select and NAV)

- Vertical Navigation (VNAV, Open Climb, etc…)

- Approach Mode

- Auto Pilot

- Auto Throttle
</pre>
</div>

* '''Auto Inflight Services'''

Flight attendants will automatically run in-flight beverage/snack service. Service begins only after Top of Climb (TOC), on flights over 250 NM, and only on passenger flights (no cargo). If any of these conditions aren’t met, service will not start.

* '''Press Takeoff Screw/AutoFlt'''

Copilot presses the TOGA Screw (PMDG aircraft) or Auto Flight button (TFDi MD-11) when the aircraft's N1 is > 65% and the Before Takeoff Checklist has been completed

[[User Settings Reference#top|Back to top]]

----

== General Options ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
General behavior options and integrations that affect how FSFO operates during a flight.
</div>

* '''Disable Gear/Flaps/Throttles'''

Copilot will ignore any flap, gear, and throttle speech recognition request. For example, if you say "gear up", your copilot will ignore this command.

* '''Disable Radio Cmds'''

Copilot will ignore any radio and transponder commands. For example, if you say "set comm one, 22800", your copilot will ignore the command.

* '''Disable Flap Calls'''

Copilot ignores manual flap adjustments and wont make callouts. Example: if you change flaps from 2 to 1, the copilot will NOT announce “Flaps 1."

* '''Skip Eng Start (AutoFlow)'''

Description Coming Soon

* '''GSX Interface'''

FSFO will request GSX instead of MSFS services when clicking on the appropriate button via the Checklist Page (Control Group Box). For example, if you click on the catering button, and this option is enabled, FSFO will use the GSX menu to request catering services.

* '''Say Intentions Interface'''

Pauses FSFO during ATC conversations.

* '''Open Door On Start'''

FSFO will open the L1 door on first connect.

* '''Use FMC Vspeeds'''

Copilot will use your FMC internal v-speed database instead of inserting the values downloaded from Simbrief. For example, on the PMDG 737, the copilot will hit the corresponding line key to load the appropriate v-speed from the FMC database. Note this only works for some aircraft (e.g. All PMDG, FBW A320, etc…).

* '''Play Ding Before Msg'''

Plays a ding before cabin announcements.

* '''Boarding/Cargo Sounds'''

Plays boarding or cargo ambiance.

* '''Verbose Mode'''

Copilot will announce his flow actions. Typically, flows are conducted silently, while checklist requires a verbal call and response. However, if you want to hear what actions your copilot is taking during the flow phase, you can enable this option.

* '''Play Squelch'''

Plays radio squelch sound.

* '''Confirm Loadsheet'''

Ground crew confirms MTOW.

* '''Kilograms'''

Reads values in kilograms.

* '''RAAS'''

Turns on the Runway Awareness and Advisory System. See [[User Settings Reference#RAAS_Options|RAAS Options]] for more details.

* '''Include ICAOs in Briefs'''

Copilot will readback the ICAOs in during the departure and approach briefings.

* '''Notify ATC Boundaries'''

Announces VATSIM ATC boundaries.

* '''Save Aircraft Location'''

Saves last aircraft location when you conclude your flight.

* '''Announce Flow'''

Announces flow start and stop; typically, flows are silent.

* '''Announce Checklist'''

Announces checklist start and stop.

* '''Rudder Flight Control Test'''

Includes rudders in control test.

* '''Up or Down Flight Control Test'''

Uses “Full Up” and “Full Down” phrasing.

* '''Ask if Ready for Briefing'''

Copilot will prompt you before the departure and approach briefings; respond by saying “Yes” (voice), pressing Ctrl+Alt, or clicking the Bypass button

* '''Cold Weather Ops'''

Copilot will fully extend the flaps and then retract them during the After Start or Taxi flow whenever the outside temperature is below freezing. This simulates a cold-weather flap movement check to help detect/clear potential icing or binding before takeoff

[[User Settings Reference#top|Back to top]]

----

== <span id="Activation_SimBrief_and_Pax">Activation, SimBrief, and Pax</span> ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Settings related to licensing, SimBrief integration, and passenger timing.
</div>

* '''Product'''

Select FSFO product.

* '''Serial Key'''

Enter 16-character serial key.

* '''Email Address'''

Used to identify and reset keys.

* '''Activation Status'''

Shows activation state.

* '''Activate Button'''

Activates the product.

* '''User Licenses'''

Displays product licenses.

* '''Open User Data Folder'''

Opens FSFO user data directory.

* '''SimBrief ID'''

Enter '''numeric''' SimBrief ID.

* '''Boarding'''

Controls boarding time (Right for slower).

* '''Food Service'''

Controls inflight service time (Right for slower).

[[User Settings Reference#top|Back to top]]

----

== RAAS Options ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Runway awareness and alerting thresholds.
</div>

* '''Short Runway (FT)'''

Alerts for short runways.

* '''Approach Runway Threshold (FT)'''

Alerts when approaching runway.

* '''On Runway Threshold (FT)'''

Alerts when on runway; aircraft must be within the runway threshold and the heading is +/- 20 of the runway heading.

* '''Unstable Approach'''

Alerts for unstable approaches; aircraft is below this threshold and following conditions exist:

<div style="margin:0.6em 0; padding:0.8em 1em; background:#fdf7f2; border-left:6px solid #f0ad4e; border-radius:8px;">
<pre>
- VREF: IAS is +/- 10

- Config: Gear and Flaps Not Set

- Bank: >14 degrees

- Descent: > 1100 Feet Per Second

- Pitch: < -5.0 or > 12.0 degrees
</pre>
</div>

* '''Altimeter Warning (AGL)'''

Alerts for incorrect altimeter.

* '''On Taxiway (IAS)'''

Alerts for taxiway overspeed.

* '''Long Landing (%)'''

Alerts for long landings.

* '''Approach Runway Landing (AGL)'''

Alerts when approaching runway for landing.

[[User Settings Reference#top|Back to top]]

----

== Interface Options ==

<div style="margin:0.6em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
Startup, UI behavior, and display options.
</div>

* '''Auto Connect'''

Attempts to connect to MSFS.

* '''Check For Updates'''

Checks for updates on startup.

* '''Warning Beeps'''

Beeps for outdated METAR or flight plans.

* '''FSFO on Top'''

Keeps FSFO window on top.

* '''Start On Flight Plan'''

Opens Flight Plan page on startup.

* '''Display ACARS'''

Flight Information will be displayed in Copilot Actions box on the SOPs Page.

* '''Include Pilot Actions'''

Displays pilot actions.

* '''Check For News'''

Displays the latest FSFO news in the app.

* '''Auto Open Post Flight'''

Opens post-flight report.

* '''Check FSUIPC'''

Checks FSUIPC version on startup.

* '''Verify Exit'''

Prompts before exiting.

* '''Remember Last Location'''

Restores window position when starting FSFO.

* '''Switch To Checklist'''

Opens checklist (SOP) page automatically.

* '''Hide Home Button'''

Hides home button.

* '''SAPI Voice Test'''

Running Voice Test plays a spoken “Voice test passed” instead of showing a message box

* '''Opacity'''

Controls the transparency of the panel background.
Lower values make the panel more transparent, allowing the simulator behind it to show through. Higher values make the panel more solid and opaque.

* '''Font size'''

Adjusts the size of all text displayed within the panel.

* '''Background picture'''
Selects an optional background image for the panel. To add an image, add it to the Background folder located: <pre>C:\Program Files\Flight Simulator First Officer V6\Res\Backgrounds\</pre>This is the default install path.
* '''Border color'''

Defines the color of the panel border.
This affects the outer edge of the panel and can be used to increase contrast against bright or dark simulator scenes.

* '''Border thickness'''

Controls how thick the panel border appears.
Higher values result in a more pronounced frame around the panel.

* '''Border brush'''

Sets the style used to draw the border.
Common options include solid or shaded styles that subtly affect how the border blends with the background.

* '''Padding'''

Controls the spacing between the panel border and its contents.
Increasing padding adds more space around text and controls, which can improve readability and reduce visual clutter.

[[User Settings Reference#top|Back to top]]

----

<div style="margin:1em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
For setup help, see [[Getting Started]]. For problem solving, see [[Troubleshooting]].
</div>

Release Notes

2026-02-26T22:49:43Z

Kingm56: /* Fixed */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.14.1
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----
== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Default NavData contained the incorrect Runway Heading
* Gear Up was not call on Takeoff
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* GSX Deboarding failed to correctly sync
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)
* Smart/Light Auto Flows - Boarding most also be completed before the Before Start will start

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.
* Checklist/Briefing - Will no longer be on a timer; simply say ready for the checklist or ready for the briefing when ready, press ctrl+alt, or your bypass key

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-02-25T20:34:46Z

Kingm56: /* Changed */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.14.1
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----
== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Default NavData contained the incorrect Runway Heading
* Gear Up was not call on Takeoff
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.
* Checklist/Briefing - Will no longer be on a timer; simply say ready for the checklist or ready for the briefing when ready, press ctrl+alt, or your bypass key

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-02-25T20:20:06Z

Kingm56: /* Fixed */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.14.1
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----
== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Default NavData contained the incorrect Runway Heading
* Gear Up was not call on Takeoff
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-02-23T18:05:38Z

Kingm56: /* Fixed */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.14.1
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----
== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* PMDG737 - Erroneous seatbelt On calls
* Arrival Performance Temp - Failed to accept negative numbers
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-02-21T18:34:40Z

Kingm56: /* Fixed */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.14.1
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----
== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* Safeguards added to prevent Decent flow from occurring before reaching Top Of Climb
* User AutoFlow was not functioning correctly while Airborne
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-02-21T18:07:59Z

Kingm56:

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="margin:0.8em 0; padding:0.8em 1em; background:#eef3fb; border-left:6px solid #1f4fa3;">
'''Latest Release:'''
Version 6.0.14.1
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----
== <span>Version 6.0.15.0</span> ==

==== Added ====

* TFDi - MD11 Profile

==== Fixed ====

* VR – Was not called when V1+VR were selected and the V1 and VR were within 4 knots
* Dep and Arv Runways were not updated when changed via the SOP screen
* When the Say Intention was active, FSFO was not pausing the flows or threads
* Logbook was not updating when no Aircraft Model Name was detected
* User AutoFlow was not functioning correctly while Airborne
* FSFO Make Runway (2020)

==== Changed ====

* PMDG/IFLY 737 - Radio is only set for Mins (vice Baro) when the min is set below 100 ft (assumes CAT II/III Landing) via the FSFO APPR option (Arv Perf page)

== <span>Version 6.0.14.1</span> ==

==== Fixed ====
* Autoflows - Flows were getting stuck and repeated

== <span>Version 6.0.14.0</span> ==

==== Added ====
* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

==== Fixed ====
* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

==== Changed ====
* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.

[[#top|Back to top]]
== <span>Version 6.0.13.0</span> ==

==== Added ====
* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

==== Fixed ====
* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

==== Changed ====
* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

==== Updated ====
* Wiki Page

[[#top|Back to top]]
== <span>Version 6.0.12.0</span> ==

==== Added ====
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

==== Fixed ====
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

==== Changed ====
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

==== Updated ====
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span>Version 6.0.11.0</span> ==

==== Added ====
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

==== Fixed ====
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

==== Changed ====
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span>Version 6.0.10.0</span> ==

==== Fixed ====
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

==== Added ====
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

==== Fixed ====
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

==== Changed ====
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-02-10T22:35:50Z

Kingm56:

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="border:1px solid #d0d4d9; background:#f9f9f9; padding:12px; margin-bottom:15px;">
'''Latest Release'''
'''[[Release Notes#v6-0-14-0|Version 6.0.13.0]]'''
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----

== <span id="v6-0-12-0">Version 6.0.14.0</span> ==

=== Added ===

* LVAR Tool – New page to view, read, and test Local Variables (LVARs).
* Say Intentions – “Say Intention” option is now connected to the sim.
* Doors – New option to toggle aircraft doors.

=== Fixed ===

* AutoFlow – Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist – Checklists would not read when called before starting a flow.
* MakeRunway – Added a dedicated MSFS 2020 build. Uninstall your current MakeRunway and install the MSFS 2020 version.
* Pushback – Engine Start was not detected when using GSX (or other third-party pushback utilities).
* Pushback – Aircraft could turn nose-right during pushback without a direction command.
* Voices – Turnaround voices were not using the “Matt” voice.
* Crew – In-flight food service was not starting.
* iniBuilds A350 – Wipers could turn on during the safety check.
* iniBuilds A350 – Flaps were not being set (including via voice command).
* iniBuilds A330 – Flaps were not being called.

=== Changed ===

* Doors – “Open Door on startup” will no longer toggle doors when you’re not on the ground or when engines are running.

== <span id="v6-0-12-0">Version 6.0.13.0</span> ==

=== Added ===

* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

=== Fixed ===

* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

=== Changed ===

* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

=== Updated ===
* Wiki Page

== <span id="v6-0-12-0">Version 6.0.12.0</span> ==

=== Added ===
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

=== Fixed ===
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

=== Changed ===
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

=== Updated ===
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span id="v6-0-11-0">Version 6.0.11.0</span> ==

=== Added ===
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

=== Fixed ===
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

=== Changed ===
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span id="v6-0-10-0">Version 6.0.10.0</span> ==

=== Fixed ===
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

=== Added ===
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

=== Fixed ===
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

=== Changed ===
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-02-08T19:46:58Z

Kingm56: /* Version 6.0.13.0 */

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="border:1px solid #d0d4d9; background:#f9f9f9; padding:12px; margin-bottom:15px;">
'''Latest Release'''
'''[[Release Notes#v6-0-13-0|Version 6.0.13.0]]'''
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----

== <span id="v6-0-12-0">Version 6.0.14.0</span> ==

=== Fixed ===

* AutoFlow: Shutdown flow could trigger immediately after the After Landing flow completed.
* Checklist: Checklists would not read when called before starting a flow.
* MakeRunway: Added a dedicated MSFS 2020 version. Uninstall your current MakeRunway and install the 2020 build.
* Pushback: Pushback was not detected for Engine Start when using GSX (or other pushback utilities).

== <span id="v6-0-12-0">Version 6.0.13.0</span> ==

=== Added ===

* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

=== Fixed ===

* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

=== Changed ===

* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

=== Updated ===
* Wiki Page

== <span id="v6-0-12-0">Version 6.0.12.0</span> ==

=== Added ===
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

=== Fixed ===
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

=== Changed ===
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

=== Updated ===
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span id="v6-0-11-0">Version 6.0.11.0</span> ==

=== Added ===
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

=== Fixed ===
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

=== Changed ===
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span id="v6-0-10-0">Version 6.0.10.0</span> ==

=== Fixed ===
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

=== Added ===
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

=== Fixed ===
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

=== Changed ===
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Release Notes

2026-02-07T00:53:40Z

Kingm56:

= Release Notes =

__NOTOC__

<span id="top"></span>

<div style="border:1px solid #d0d4d9; background:#f9f9f9; padding:12px; margin-bottom:15px;">
'''Latest Release'''
'''[[Release Notes#v6-0-13-0|Version 6.0.13.0]]'''
</div>

This page lists version history and change logs for Flight Simulator First Officer (FSFO) v6.

New features and fixes are listed at the top.

----

== <span id="v6-0-12-0">Version 6.0.13.0</span> ==

=== Added ===

* Aircraft: iniBuilds A330 and A321 (MSFS2024 ONLY)
* AutoFlow: Additional option USER, which allows you to individually set what system, event or time will start a flow
* FSFO_Make_Runway.exe - You can now update your airport database [NOT REQUIRED]
* New FSFO WIki Page
* Settings: Open Door On Start option
* Settings: Skip Eng Start (AutoFlow) - This will prevent copilot from starting your engines
* Wait_For_System Doors_Open and Doors_Closed option
* Engine Start across all AutoFlow options (60 seconds after pushback is started)
* Slider to control Boarding/Deboarding speed
* Slider to control food and beverage service speeds
* Editor: Added Doors Toggle_0 through Toggle_6 option to open/close doors
* Editor: Play_Wav option which allows you to play any wav file during your flows.
* Editor: Added the ability for advance users to add any LVAR to your flow (see advance users PDF).
* Editor: Added the ability for advance users to add any SIMVAR to your flow (see advance users PDF).

=== Fixed ===

* IFLY737: Doors were always detected as open
* INIA350: Default Profile contained multiple errors.
* Erroneous Check the A/T and Lights call
* Food services being repeated over-and-over again
* Help PDF failed to open the User Guide
* Button: Pushing the pause button only paused FSFO (not unpause)
* Editor: Ask For Checklist was only working once

=== Changed ===

* SOP OPTION: Vspeed option to set V1, V1+VR or none.
* HELP: Open FSFO Wiki Page
* Smart Option:
** Set Parking Brake now starts the After Start Flow
** Release Parking Brake now starts the Taxi Flow
** When the Aircraft leaves the runway it will start the After Landing Flow

=== Updated ===
* Wiki Page

== <span id="v6-0-12-0">Version 6.0.12.0</span> ==

=== Added ===
* Aircraft: Inibuilds A300
* Aircraft: Inibuilds A310
* Settings: Cold Weather Ops Operations
* Settings: Slider to boost the Ambient Sound Wav Files
* Settings: Slider to boost the Pilots Sound Wav Files
* Settings: Added buttons to test the ambiance and boarding music
* Settings: Couple Wing and Logo to Landing Lights
* Intercom option to communicate with the Flight Crew
* Flows: If cold weather Ops was detected, the Copilot will set the flaps before the Takeoff or Lineup Flow
* Flows: Loadsheet option. When Confirm is selected, you will be contacted by ground to ensure the aircraft is within weight limits
* Flows: Radio_Tune and Radio_Stby (tunes the standby frequency) options:
** TWR – Tunes the departure tower before top of descent (TOD) and the arrival tower after TOD
** CTR – Tunes the departure center before TOD and the arrival center after TOD
** DEP – Tunes the departure control (DEP) frequency before TOD and the corresponding arrival control frequency after TOD
** APR – Tunes the approach control (APP) frequency for the departure airport before TOD and the app frequency for the arrival airport after TOD
** GRND – Tunes the ground frequency at the departure airport before TOD and the arrival ground frequency after TOD
** CLR – Tunes clearance delivery at the departure airport before TOD and the equivalent arrival frequency after TOD
** UNICOM – Sets COM1 to 122.800
** WX – Sets COM1 to 122.000 for the HiFi Active Sky weather broadcast
** ATIS – Tunes the departure ATIS before TOD and the arrival ATIS after TOD
** CTAF – Tunes the CTAF frequency for the departure airport before TOD and the CTAF for the arrival airport after TOD (or tower if CTAF isn’t flagged)
* Speech: "contact tower", "contact center", "contact departure", "contact approach", "contact ground", "contact clearance delivery", "tune unicom", "tune c-taf", "tune atis", "tune weather"
* Sounds: Different Greeting for Turn Around Flights
* First Officer warns if ice is detected
* PMDG: Added Press PMDG Takeoff Screw option. It will press the takeoff screw when N1 percent is greater than 70 percent
* PMDG777: Added Nose_On and Nose_Off Landing Light options
* Pilot now informs Copilot that he will extend or retract the flaps for cold weather ops
* Check the AutoThrottle if it is off before takeoff

=== Fixed ===
* Copilot was not setting the flaps during the Before Takeoff Flow when cold weather ops was detected
* Duplicate flap calls
* SOPs: Performance data was not displaying when closing and opening the PREF data
* Flows: The Hybrid Auto Flow (Shutdown) was triggered when the taxi light was still on
* Main Page: Settings icon border
* Aircraft: Erroneously gear down called on takeoff
* iniA350: Wipers not set correctly for MSFS 2024 users
* PMDG737: Anti-ice off verbal command resulted in the wipers being turned on
* MSFS ATR: POWER_MANAGEMENT TO was being set to MCT
* iFly737: Descent winds were not loading
* PMDG777: Erroneous check the lights call
* Score: Erroneous taxi and nav light penalties
* Score: Erroneous spoiler not deployed penalty
* Settings: When autoflow was set to NONE, the copilot would still execute autoflows in the air
* Landing: Erroneous check the flaps callouts
* GSX: Erroneous pax loading numbers and completions
* Food Services
* Flight Plan: FSFO was not asking if you would like to make a turn around flight, when the battery is ON
* Flight Plan: FSFO failed to revalidate the flight plan when clicking Download SimBrief
* Editor: When selecting you want to use GSX, it would still not use GSX

=== Changed ===
* Settings: Added Crew Option Set Lights (setting the landing lights on and off is now decoupled from the SOP Passing Call)
* Score: Removed taxi light from pilot score and added unstable approach
* Flight Plan: When clicking Start Flight, and FSFO is not connected to MSFS, it will now ask if you would like to connect

=== Updated ===
* Voice command list
* User settings document

[[#top|Back to top]]

----

== <span id="v6-0-11-0">Version 6.0.11.0</span> ==

=== Added ===
* Just Flight 146 Profile
* Settings: Check for Update Button
* Confirmation Message Box to confirm stopping a phase
* Voice Commands: Preflight Checklist, Before Start Checklist, etc (when called, only the checklist portion will execute)
* Labels for Top Row to assist our blind pilots
* Labels for the Settings Page to assist our blind pilots
* Labels for the Edit Page to assist our blind pilots
* American Airlines, Delta and Fedex Background Options
* Button on the main page to open the users data folder
* PMDG737: Weather Radar is now interactive
* Settings: Option to play squelch sound at the beginning of Ground Comms
* Sounds: Added new Ground sounds to Matt region (thank you reddddddd)

=== Fixed ===
* Sounds: Removed the underscore from Reverse Normal, A C Wild Generators, A P U Bleed and Oxygen Test from FO sounds
* Sounds: Removed the underscore from Gear_Down and AutoPilot_Off Capt sounds
* Sounds: Several Crew sounds were missing from British 1
* Speech: The PTT feature was not working correctly when not using Open Mic
* SOP Page: When leaving and returning to the SOPs page, the copilot would lose track of what line they were on
* Editor: Standby value was reset to 1
* Editor: user;;; line failed to save
* Editor: Capt Actions failed to save
* FEN A320: Verify profile warning
* FEN A320: Error when entering ZFW as KGs
* PMDG737: Flap calls were inaccurate (example: Flaps 10 when on Flaps 5)
* PMDG737: AutoBrakes were set to Max when selected to Off
* PMDG737: Retractable Landing Lights to the retract position
* PMDG737: EFIS Mode was not set by the First Officer
* PMDG737: EFIS Range was not set by the First Officer
* PMDG737: Course not being set
* PMDG and iFly 737: Added 4 (MAX) for AutoBrake options
* iFly737: Wait times increased from 10 to 20 to allow winds to download before pressing LOAD
* Flight Plan: Error when manually creating flight plan
* Settings: Boarding music not saving

=== Changed ===
* Editor: Now asks if you would like to restart after saving. It will keep your current aircraft profile loaded

[[#top|Back to top]]

----

== <span id="v6-0-10-0">Version 6.0.10.0</span> ==

=== Fixed ===
* EMER NOTAM: FSFO was failing to save activation status
* FEN A320: Failing validation test

[[#top|Back to top]]

----

== <span id="v6-0-9-0">Version 6.0.9.0</span> ==

=== Added ===
* FSFO now saves and loads your last Aircraft Profile and Checklist
* FSFO will now check to ensure the selected Aircraft Profile matches your current model. You will get a warning if there is a mismatch
* Show PERF button on the SOPs page to allow access to vital performance data
* PMDG fallback for airspeed, altitude, and heading. If the LVAR is 0, FSFO will use the FSUIPC variable
* User License Button. You can now view which FSFO licenses are stored in Windows Key Storage
* Button to Hide or Unhide GSX Menu
* FSFO will now validate your SimBrief flight plan to ensure it was generated within a 2-hour window
* FEN A320: Wait_For_Captain option
* FEN A320: Hydraulic_Pumps On, Off, Eng1_On or Off, Eng2_On or Off
* FEN A320: Opened and Closed added to the COCKPIT_DOORS option
* FEN A320: EFIS_Filter_Capt, EFIS_Mode_Capt, EFIS_Range_Capt and LS_Mode_Capt options
* iFly 737: Download Descent Winds
* iFly 737: Transponder_Reply option with Stby, On, and Auto as options
* iFly 737: IFE and Cabin Utility Flow Options
* iFly 737: Hyd_Pumps A and B On or Off
* iFly and PMDG 737: Minimums Set will now set the minimums on the aircraft
* AERO CRJ: NOSE_LIGHTS ON, OFF, SET options
* GSX GPU added to additional services

=== Fixed ===
* FEN A320: PA Button was not actually turning on
* iFly 737: Transponder was set correctly, but FO failed to acknowledge
* iFly 737: Heading and altitude set commands
* iFly 737 and PMDG 737: Was not setting ILS frequency
* iFly 737: Copilot was not turning off his FD switch
* ini A350: Wipers were turning on when set to off (MSFS 2024 only)
* ini A350: Public Address option was setting the wrong system
* PMDG 777: Landing lights not turning off or on
* GSX engine confirm started
* Standby command can now be edited via the editor
* Pushback sequence was starting in the air
* Action key was skipping the Engine Start phase
* SAPI was announcing the underscore
* Transition altitude setting had no effect. Copilot was always setting the TA
* Spinning altitude, heading, and speed dials for the ATR and CRJ
* App was always on top, regardless of user setting
* Payload command was generating a hidden message box that would freeze a flow
* Message box requesting the player to generate a SOP was hidden under the application during activation
* Checklist validation was failing without lines 14, 15, and 16
* Multiple Anti-Ice On calls

=== Changed ===
* For Hybrid and Light AutoFlows, you must also apply the parking brake
* For Hybrid and Light AutoFlows, the Lineup or Before Start and After Landing Flow are now triggered by the landing lights
* Disable Gear and Flaps Control now includes throttles

[[#top|Back to top]]

----

For setup help see [[Getting Started]] or for problem resolution see [[Troubleshooting]].

Advanced Users Guide

2026-02-04T04:28:59Z

Kingm56: /* Manual Database Updates */

= Advanced Users Guide =
This guide is intended for advanced FSFO users who want to manually customize SOPs, create their own flows and checklists, tune Smart Flows, and manage the FSFO airport database.

<span id="top"></span>
<div style="border:1px solid #aaa; background:#f9f9f9; padding:12px; width:320px; float:right; margin:0 0 15px 15px;">
'''Quick navigation'''<br />
Jump to a settings group:

* [[Advanced Users Guide#SOP_File_Location|SOP File Location]]
* [[Advanced Users Guide#SOP_File_Structure|SOP File Structure]]
* [[Advanced Users Guide#Phases|Phases]]
* [[Advanced Users Guide#Types|Types (Flow vs Checklist)]]
* [[Advanced Users Guide#Creating_Custom_Flows|Creating Custom Flows and Checklists]]
* [[Advanced Users Guide#Flow_Commands|Flow Commands Explained]]
* [[Advanced Users Guide#Smart_Flow_Tuning|Manually Update Smart Flow Options]]
* [[Advanced Users Guide#Airport_Database|FSFO Airport Database Tool]]
</div>
== <span id="SOP_File_Location">SOP File Location</span> ==
All SOPs are stored in:

C:\Users\[Your Name]\AppData\Local\FSFO_V6\FlowsChk

Replace '''[Your Name]''' with your Windows user name.

Each SOP file must begin with two required header lines:<pre>
type;AIRBUS;;
user;;;
</pre>

* The first line identifies the aircraft type (BOEING or AIRBUS).
* The second line is reserved for user-generated flows and checklists.

[[Advanced Users Guide#top|Back to top]]
== <span id="SOP_File_Structure">SOP File Structure</span> ==
Each line in an SOP file uses the following structure:<pre>
Phase;Type;System;Response
</pre>Example:<pre>
1;1;Auto_Brakes;MAX
</pre>Where:

* Phase = Flight phase number
* Type = Flow or Checklist
* System = Target system or command
* Response = Desired value or action

[[Advanced Users Guide#top|Back to top]]
== <span id="Phases">Phases</span> ==
The following numeric values define flight phases:<pre>
1 = Preflight or Cockpit Preparation
2 = Before Start
3 = Engine Start
4 = After Start
5 = Taxi
6 = Before Takeoff or Lineup
7 = After Takeoff
8 = Descent
9 = Approach
10 = Landing
11 = After Landing
12 = Shutdown or Parking
13 = Runway Change
100 = Turn Around
14 = User Defined
15 = User Defined
16 = User Defined
</pre>
[[Advanced Users Guide#top|Back to top]]
== <span id="Types">Types (Flow vs Checklist)</span> ==
<pre>
1 = Flow
2 = Checklist
</pre>

'''Flow''' A memorized, spatial sweep of switches and controls used to configure the aircraft. Flows are fast, heads-up, and done from memory.

'''Checklist''' A short, written challenge-response used to verify critical items are correctly set.

How they work together:

* Normal operations: Flow → Checklist
* Abnormal or emergencies: Use QRH or abnormal checklist

The flow performs the actions, the checklist verifies them.

[[Advanced Users Guide#top|Back to top]]
== <span id="Creating_Custom_Flows">Creating Custom Flows and Checklists</span> ==
Always create a backup copy of your SOP file before making manual edits.

To add user-defined flows (for example: Single Engine and Go-Around):

Update the second line of your SOP file:<pre>
type;AIRBUS;;
user;Single_Eng;Go_Around;
</pre>Then add new phase lines at the end of your file:<pre>
13;2;Takeoff_Speeds;READBACK
13;2;Altitude;READBACK

14;2;Action;Value
14;2;Action;Value

15;2;Action;Value
15;2;Action;Value
</pre>Mapping:

* Phase 14 = Supplemental Flow One
* Phase 15 = Supplemental Flow Two
* Phase 16 = Supplemental Flow Three

Voice commands:

* “Supplemental checklist one”
* “Supplemental flow one”
[[Advanced Users Guide#top|Back to top]]

== <span id="Types">Set Commands</span> ==
<pre>PACKS: Sets packs according to the option selected on the FSFO Departure Performance page.
ALTITUDE: Sets the autopilot altitude to the Initial Altitude (or Planned Altitude) selected on the FSFO Flight Plan page.
HEADING: Sets the heading bug to the departure runway heading selected on the FSFO Departure Performance page.
AIRSPEED: Sets IAS to the V2 speed entered on the FSFO Departure Performance page.
AUTO_BRAKES: Sets according to the option selected on the FSFO Arrival Performance page.
FLAPS: Sets according to the option selected on the FSFO Departure Performance page.
COCKPIT_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
DOME_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
WING_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
ANTI-ICE: Turns ENGINE_ANTI_ICE and WING_ANTI_ICE ON when OAT < 10°C and precipitation is detected; otherwise OFF.</pre>

A SET Commands used during the flows will result in the above.

[[Advanced Users Guide#top|Back to top]]

== <span id="Flow_Commands">Flow Commands Explained</span> ==

=== LVAR ===
This command is intended for advanced users who are comfortable working with MSFS Local Variables (LVARs) and know how to acquire and use them. To use it, add the LVAR command, then enter the LVAR name, an equals sign (<code>=</code>), and the desired value/state (i.e., <code>LVAR_NAME=VALUE</code>). FSFO also supports PMDG Rotor Brake commands (Toggle and Push Only) by using the <code>ROTOR_BRAKE</code> option after <code>LVAR</code> in the format <code>ROTOR_BRAKE=<SwitchID>=<Label></code>. For example: <code>1;1;LVAR;ROTOR_BRAKE=101=Battery;</code> — in this case, <code>ROTOR_BRAKE</code> tells FSFO to use the Rotor Brake command type, <code>101</code> is the SwitchID, and <code>Battery</code> is the label that will be displayed (and spoken) on the SOPs page.

Format:<pre>
1;1;LVAR;XMLVAR_StandbyPower_Selector=1=Standby Power
1;1;LVAR;ROTOR_BRAKE=101=Battery
</pre>Meaning:

* XMLVAR_StandbyPower_Selector = LVAR name
* 1 = value
* Standby Power = Label that will be displayed (and spoken) on the SOPs page
Rotor_Brake Meaning:

* <code>ROTOR_BRAKE</code> = Tells FSFO to use the Rotor Brake command type
* 101 = SwitchID
* Battery = Label that will be displayed (and spoken) on the SOPs page

----

=== SIMVAR ===
Used to control MSFS Simulation Variables.

Format:<pre>
1;1;SIMVAR;67271=1=Parking Brake
</pre>Meaning:

* SIMVAR = Tells FSFO to use the SIMVAR command type
* 67271 = SIMVAR control number (complete list here: [[SIMVAR Control Numbers]])
* 1 = value (ON)
* Parking Brake = abel that will be displayed (and spoken) on the SOPs page

----

=== Play_Sapi_Copilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Copilot voice selected in Settings. If no Copilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Sapi_Pilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Pilot voice selected in Settings. If no Pilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Wav ===
Plays a WAV file. You must enter the full path of the wav file.

Format:<pre>
1;1;Play_Wav;C:\Users\name\FSFO\boarding_Noise.wav
</pre>
----

=== Misc_Text ===
Displays reminder text under the Pilot section.

Example:<pre>
1;1;Misc_Text;Start ACARS
</pre>
----

=== Capt_Actions ===
Displays reminder text under the Captain Actions section.
----

=== Flight_Plan ===
Loads the most recent flight plan from:

C:\Users\[name]\AppData\Local\FSFO_V6\Download
----

=== Landing_Data ===
Reads back minimums and Vref speeds.
----

=== Fuel ===

* Load = FSFO will load the fuel amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Payload ===

* Load = FSFO will load the payload amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Loadsheet ===

* Confirm = Ground crew will confirm the aircraft is under Max Takeoff Weight (MTOW). If it is over MTOW, they will warn you and request that you check your loadsheet.

----

=== Doors ===

* Toggle_0 through Toggle_6 = Will open/close the doors; for example, Toggle_1 will open/close the 1L(Main) Door on most aircraft.

----

=== Walk_Around ===
While the default values are SHORT, MED, and LONG, advanced users can open the SOP text file and enter any numeric value (seconds) they like for the copilot to perform the walk-around. As an example:<pre>
1;1;WALK_AROUND;965
</pre>Defaults:

* SHORT = 150 seconds
* MED = 300 seconds
* LONG = 600 seconds

[[Advanced Users Guide#top|Back to top]]
== <span id="Smart_Flow_Tuning">Manually Update Smart Flow Options</span> ==
You can still manually update your SMART AutoFlow options by updating the userSettings.cfg file by following these steps:

# Close FSFO
# Navigate to C:\Users\[Your Name]\AppData\Local\FSFO_V6\UserData Folder
## You can also just click on the UserData button on FSFO’s front page
# Right-Click on userSettings.cfg and click Open with Notepad
# Locate and edit these lines1; '''ensure no trailing white space or empty lines'''
<pre>
Flows_PreFltStart=10
Flows_BeforeTakeoffStart=800
Flows_AfterTakeoffStart=3000
Flows_DescentStart=20
Flows_ApproachStart=10000
Flows_LndgStart=1500
</pre>Units:<pre>
Flows_PreFltStart = Seconds
Flows_BeforeTakeoffStart = Feet to runway threshold
Flows_AfterTakeoffStart = AGL feet
Flows_DescentStart = Nautical miles
Flows_ApproachStart = AGL feet
Flows_LndgStart = AGL feet
</pre>
[[Advanced Users Guide#top|Back to top]]
== <span id="Airport_Database">FSFO Airport Database Tool</span> ==
FSFO Make Runway is a separate program that builds the runway database using SIMCONNECT and MSFS APIs.

=== Installation ===
You can install it in two ways:

# From FSFO
## Click '''Get Started''' on the FSFO main page
## Click '''MAKE RWY''' on the New User window
## Follow the installation instructions
# Manually:
## Navigate to *\Flight Simulator First Officer V6\Res\Exe
### * represents your FSFO V6 directory; just right-click on the Flight Simulator First Officer V6 shortcut and select "Open File Location"
## Right-Click '''FSFO_Make_Runway.exe''' and Select "Run as Administrator"

----

=== Building the Database ===
[[File:MakeRwy.png|left|thumb]]

# Start MSFS or MSFS24 and load into the cockpit
# Click '''FSFO NAV PATH''' and select the FSFO NavData folder
# Click '''Connect'''
# Click '''Build'''

'''Note: This process can take over two hours.'''

----

=== Manual Database Updates ===
Runway data file:

* *\FSFO_V6\NavData\runways.csv
[[File:AirportDb.png|left|thumb|419x419px]]

'''Note 1 (Runway Code)''':
* Stored as a 3-digit code where the last digit indicates the side:
** 0 = none
** 1 = Left (L)
** 2 = Right (R)
** 3 = Center (C)
** 4 = Water (W)

* Examples:
** 330 = Runway 33
** 331 = Runway 33L
** 332 = Runway 33R
** 333 = Runway 33C
** 090 = Runway 9
** 091 = Runway 9L

'''Note 2 (Latitude/Longitude format):'''

* Lat/Lon values must be in decimal degrees (DD) format (example: 42.193545).
* Threshold lat/lon represent the runway threshold (AFCAD “runway start”).
'''Note 3 (Feet):'''

* Elevation, length, width, and threshold offset values are (must be) in feet.

'''Note 4 (Heading):'''

* Runway heading is the magnetic runway heading.

'''Note 5 (ILS frequency):'''

* ILS frequency is stored as nnn.nn (example: 109.50) or 0 if no ILS is available.

'''Note 6 (Magnetic variation):'''

* Magnetic variation (in degrees) is the value applied to convert magnetic to true heading: True Heading = Magnetic Heading + Magnetic Variation

[[Advanced Users Guide#top|Back to top]]
----

For standard setup and everyday operation, see [[Getting Started]] and [[User Settings Reference]].

Advanced Users Guide

2026-02-04T04:19:59Z

Kingm56: /* SIMVAR */

Advanced Users Guide

2026-02-04T04:18:44Z

Kingm56: /* Flow Commands Explained */

= Advanced Users Guide =
This guide is intended for advanced FSFO users who want to manually customize SOPs, create their own flows and checklists, tune Smart Flows, and manage the FSFO airport database.

<span id="top"></span>
<div style="border:1px solid #aaa; background:#f9f9f9; padding:12px; width:320px; float:right; margin:0 0 15px 15px;">
'''Quick navigation'''<br />
Jump to a settings group:

* [[Advanced Users Guide#SOP_File_Location|SOP File Location]]
* [[Advanced Users Guide#SOP_File_Structure|SOP File Structure]]
* [[Advanced Users Guide#Phases|Phases]]
* [[Advanced Users Guide#Types|Types (Flow vs Checklist)]]
* [[Advanced Users Guide#Creating_Custom_Flows|Creating Custom Flows and Checklists]]
* [[Advanced Users Guide#Flow_Commands|Flow Commands Explained]]
* [[Advanced Users Guide#Smart_Flow_Tuning|Manually Update Smart Flow Options]]
* [[Advanced Users Guide#Airport_Database|FSFO Airport Database Tool]]
</div>
== <span id="SOP_File_Location">SOP File Location</span> ==
All SOPs are stored in:

C:\Users\[Your Name]\AppData\Local\FSFO_V6\FlowsChk

Replace '''[Your Name]''' with your Windows user name.

Each SOP file must begin with two required header lines:<pre>
type;AIRBUS;;
user;;;
</pre>

* The first line identifies the aircraft type (BOEING or AIRBUS).
* The second line is reserved for user-generated flows and checklists.

[[Advanced Users Guide#top|Back to top]]
== <span id="SOP_File_Structure">SOP File Structure</span> ==
Each line in an SOP file uses the following structure:<pre>
Phase;Type;System;Response
</pre>Example:<pre>
1;1;Auto_Brakes;MAX
</pre>Where:

* Phase = Flight phase number
* Type = Flow or Checklist
* System = Target system or command
* Response = Desired value or action

[[Advanced Users Guide#top|Back to top]]
== <span id="Phases">Phases</span> ==
The following numeric values define flight phases:<pre>
1 = Preflight or Cockpit Preparation
2 = Before Start
3 = Engine Start
4 = After Start
5 = Taxi
6 = Before Takeoff or Lineup
7 = After Takeoff
8 = Descent
9 = Approach
10 = Landing
11 = After Landing
12 = Shutdown or Parking
13 = Runway Change
100 = Turn Around
14 = User Defined
15 = User Defined
16 = User Defined
</pre>
[[Advanced Users Guide#top|Back to top]]
== <span id="Types">Types (Flow vs Checklist)</span> ==
<pre>
1 = Flow
2 = Checklist
</pre>

'''Flow''' A memorized, spatial sweep of switches and controls used to configure the aircraft. Flows are fast, heads-up, and done from memory.

'''Checklist''' A short, written challenge-response used to verify critical items are correctly set.

How they work together:

* Normal operations: Flow → Checklist
* Abnormal or emergencies: Use QRH or abnormal checklist

The flow performs the actions, the checklist verifies them.

[[Advanced Users Guide#top|Back to top]]
== <span id="Creating_Custom_Flows">Creating Custom Flows and Checklists</span> ==
Always create a backup copy of your SOP file before making manual edits.

To add user-defined flows (for example: Single Engine and Go-Around):

Update the second line of your SOP file:<pre>
type;AIRBUS;;
user;Single_Eng;Go_Around;
</pre>Then add new phase lines at the end of your file:<pre>
13;2;Takeoff_Speeds;READBACK
13;2;Altitude;READBACK

14;2;Action;Value
14;2;Action;Value

15;2;Action;Value
15;2;Action;Value
</pre>Mapping:

* Phase 14 = Supplemental Flow One
* Phase 15 = Supplemental Flow Two
* Phase 16 = Supplemental Flow Three

Voice commands:

* “Supplemental checklist one”
* “Supplemental flow one”
[[Advanced Users Guide#top|Back to top]]

== <span id="Types">Set Commands</span> ==
<pre>PACKS: Sets packs according to the option selected on the FSFO Departure Performance page.
ALTITUDE: Sets the autopilot altitude to the Initial Altitude (or Planned Altitude) selected on the FSFO Flight Plan page.
HEADING: Sets the heading bug to the departure runway heading selected on the FSFO Departure Performance page.
AIRSPEED: Sets IAS to the V2 speed entered on the FSFO Departure Performance page.
AUTO_BRAKES: Sets according to the option selected on the FSFO Arrival Performance page.
FLAPS: Sets according to the option selected on the FSFO Departure Performance page.
COCKPIT_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
DOME_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
WING_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
ANTI-ICE: Turns ENGINE_ANTI_ICE and WING_ANTI_ICE ON when OAT < 10°C and precipitation is detected; otherwise OFF.</pre>

A SET Commands used during the flows will result in the above.

[[Advanced Users Guide#top|Back to top]]

== <span id="Flow_Commands">Flow Commands Explained</span> ==

=== LVAR ===
This command is intended for advanced users who are comfortable working with MSFS Local Variables (LVARs) and know how to acquire and use them. To use it, add the LVAR command, then enter the LVAR name, an equals sign (<code>=</code>), and the desired value/state (i.e., <code>LVAR_NAME=VALUE</code>). FSFO also supports PMDG Rotor Brake commands (Toggle and Push Only) by using the <code>ROTOR_BRAKE</code> option after <code>LVAR</code> in the format <code>ROTOR_BRAKE=<SwitchID>=<Label></code>. For example: <code>1;1;LVAR;ROTOR_BRAKE=101=Battery;</code> — in this case, <code>ROTOR_BRAKE</code> tells FSFO to use the Rotor Brake command type, <code>101</code> is the SwitchID, and <code>Battery</code> is the label that will be displayed (and spoken) on the SOPs page.

Format:<pre>
1;1;LVAR;XMLVAR_StandbyPower_Selector=1=Standby Power
1;1;LVAR;ROTOR_BRAKE=101=Battery
</pre>Meaning:

* XMLVAR_StandbyPower_Selector = LVAR name
* 1 = value
* Standby Power = Label that will be displayed (and spoken) on the SOPs page
Rotor_Brake Meaning:

* <code>ROTOR_BRAKE</code> = Tells FSFO to use the Rotor Brake command type
* 101 = SwitchID
* Battery = Label that will be displayed (and spoken) on the SOPs page

----

=== SIMVAR ===
Used to control MSFS Simulation Variables.

Format:<pre>
1;1;SIMVAR;67271=1=Parking Brake
</pre>Meaning:

* SIMVAR = Tells FSFO to use the SIMVAR command type
* 67271 = SIMVAR control number
* 1 = value (ON)
* Parking Brake = abel that will be displayed (and spoken) on the SOPs page

----

=== Play_Sapi_Copilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Copilot voice selected in Settings. If no Copilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Sapi_Pilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Pilot voice selected in Settings. If no Pilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Wav ===
Plays a WAV file. You must enter the full path of the wav file.

Format:<pre>
1;1;Play_Wav;C:\Users\name\FSFO\boarding_Noise.wav
</pre>
----

=== Misc_Text ===
Displays reminder text under the Pilot section.

Example:<pre>
1;1;Misc_Text;Start ACARS
</pre>
----

=== Capt_Actions ===
Displays reminder text under the Captain Actions section.
----

=== Flight_Plan ===
Loads the most recent flight plan from:

C:\Users\[name]\AppData\Local\FSFO_V6\Download
----

=== Landing_Data ===
Reads back minimums and Vref speeds.
----

=== Fuel ===

* Load = FSFO will load the fuel amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Payload ===

* Load = FSFO will load the payload amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Loadsheet ===

* Confirm = Ground crew will confirm the aircraft is under Max Takeoff Weight (MTOW). If it is over MTOW, they will warn you and request that you check your loadsheet.

----

=== Doors ===

* Toggle_0 through Toggle_6 = Will open/close the doors; for example, Toggle_1 will open/close the 1L(Main) Door on most aircraft.

----

=== Walk_Around ===
While the default values are SHORT, MED, and LONG, advanced users can open the SOP text file and enter any numeric value (seconds) they like for the copilot to perform the walk-around. As an example:<pre>
1;1;WALK_AROUND;965
</pre>Defaults:

* SHORT = 150 seconds
* MED = 300 seconds
* LONG = 600 seconds

[[Advanced Users Guide#top|Back to top]]
== <span id="Smart_Flow_Tuning">Manually Update Smart Flow Options</span> ==
You can still manually update your SMART AutoFlow options by updating the userSettings.cfg file by following these steps:

# Close FSFO
# Navigate to C:\Users\[Your Name]\AppData\Local\FSFO_V6\UserData Folder
## You can also just click on the UserData button on FSFO’s front page
# Right-Click on userSettings.cfg and click Open with Notepad
# Locate and edit these lines1; '''ensure no trailing white space or empty lines'''
<pre>
Flows_PreFltStart=10
Flows_BeforeTakeoffStart=800
Flows_AfterTakeoffStart=3000
Flows_DescentStart=20
Flows_ApproachStart=10000
Flows_LndgStart=1500
</pre>Units:<pre>
Flows_PreFltStart = Seconds
Flows_BeforeTakeoffStart = Feet to runway threshold
Flows_AfterTakeoffStart = AGL feet
Flows_DescentStart = Nautical miles
Flows_ApproachStart = AGL feet
Flows_LndgStart = AGL feet
</pre>
[[Advanced Users Guide#top|Back to top]]
== <span id="Airport_Database">FSFO Airport Database Tool</span> ==
FSFO Make Runway is a separate program that builds the runway database using SIMCONNECT and MSFS APIs.

=== Installation ===
You can install it in two ways:

# From FSFO
## Click '''Get Started''' on the FSFO main page
## Click '''MAKE RWY''' on the New User window
## Follow the installation instructions
# Manually:
## Navigate to *\Flight Simulator First Officer V6\Res\Exe
### * represents your FSFO V6 directory; just right-click on the Flight Simulator First Officer V6 shortcut and select "Open File Location"
## Right-Click '''FSFO_Make_Runway.exe''' and Select "Run as Administrator"

----

=== Building the Database ===
[[File:MakeRwy.png|left|thumb]]

# Start MSFS or MSFS24 and load into the cockpit
# Click '''FSFO NAV PATH''' and select the FSFO NavData folder
# Click '''Connect'''
# Click '''Build'''

'''Note: This process can take over two hours.'''

----

=== Manual Database Updates ===
Runway data file:

* *\FSFO_V6\NavData\runways.csv
[[File:AirportDb.png|left|thumb|419x419px]]

'''Note 1 (Runway Code)''':
* Stored as a 3-digit code where the last digit indicates the side:
** 0 = none
** 1 = Left (L)
** 2 = Right (R)
** 3 = Center (C)
** 4 = Water (W)

* Examples:
** 330 = Runway 33
** 331 = Runway 33L
** 332 = Runway 33R
** 333 = Runway 33C
** 090 = Runway 9
** 091 = Runway 9L

'''Note 2 (Latitude/Longitude format):'''

* Lat/Lon values must be in decimal degrees (DD) format (example: 42.193545).
* Threshold lat/lon represent the runway threshold (AFCAD “runway start”).
'''Note 3 (Feet):'''

* Elevation, length, width, and threshold offset values are (must be) in feet.

'''Note 4 (Heading):'''

* Runway heading is the magnetic runway heading.

'''Note 5 (ILS frequency):'''

* ILS frequency is stored as nnn.nn (example: 109.50) or 0 if no ILS is available.

'''Note 6 (Magnetic variation):'''

* Magnetic variation (in degrees) is the value applied to convert magnetic to true heading: True Heading = Magnetic Heading + Magnetic Variation

[[Advanced Users Guide#top|Back to top]]
----

For standard setup and everyday operation, see [[Getting Started]] and [[User Settings Reference]].

Advanced Users Guide

2026-02-04T04:16:40Z

Kingm56: /* Flow Commands Explained */

= Advanced Users Guide =
This guide is intended for advanced FSFO users who want to manually customize SOPs, create their own flows and checklists, tune Smart Flows, and manage the FSFO airport database.

<span id="top"></span>
<div style="border:1px solid #aaa; background:#f9f9f9; padding:12px; width:320px; float:right; margin:0 0 15px 15px;">
'''Quick navigation'''<br />
Jump to a settings group:

* [[Advanced Users Guide#SOP_File_Location|SOP File Location]]
* [[Advanced Users Guide#SOP_File_Structure|SOP File Structure]]
* [[Advanced Users Guide#Phases|Phases]]
* [[Advanced Users Guide#Types|Types (Flow vs Checklist)]]
* [[Advanced Users Guide#Creating_Custom_Flows|Creating Custom Flows and Checklists]]
* [[Advanced Users Guide#Flow_Commands|Flow Commands Explained]]
* [[Advanced Users Guide#Smart_Flow_Tuning|Manually Update Smart Flow Options]]
* [[Advanced Users Guide#Airport_Database|FSFO Airport Database Tool]]
</div>
== <span id="SOP_File_Location">SOP File Location</span> ==
All SOPs are stored in:

C:\Users\[Your Name]\AppData\Local\FSFO_V6\FlowsChk

Replace '''[Your Name]''' with your Windows user name.

Each SOP file must begin with two required header lines:<pre>
type;AIRBUS;;
user;;;
</pre>

* The first line identifies the aircraft type (BOEING or AIRBUS).
* The second line is reserved for user-generated flows and checklists.

[[Advanced Users Guide#top|Back to top]]
== <span id="SOP_File_Structure">SOP File Structure</span> ==
Each line in an SOP file uses the following structure:<pre>
Phase;Type;System;Response
</pre>Example:<pre>
1;1;Auto_Brakes;MAX
</pre>Where:

* Phase = Flight phase number
* Type = Flow or Checklist
* System = Target system or command
* Response = Desired value or action

[[Advanced Users Guide#top|Back to top]]
== <span id="Phases">Phases</span> ==
The following numeric values define flight phases:<pre>
1 = Preflight or Cockpit Preparation
2 = Before Start
3 = Engine Start
4 = After Start
5 = Taxi
6 = Before Takeoff or Lineup
7 = After Takeoff
8 = Descent
9 = Approach
10 = Landing
11 = After Landing
12 = Shutdown or Parking
13 = Runway Change
100 = Turn Around
14 = User Defined
15 = User Defined
16 = User Defined
</pre>
[[Advanced Users Guide#top|Back to top]]
== <span id="Types">Types (Flow vs Checklist)</span> ==
<pre>
1 = Flow
2 = Checklist
</pre>

'''Flow''' A memorized, spatial sweep of switches and controls used to configure the aircraft. Flows are fast, heads-up, and done from memory.

'''Checklist''' A short, written challenge-response used to verify critical items are correctly set.

How they work together:

* Normal operations: Flow → Checklist
* Abnormal or emergencies: Use QRH or abnormal checklist

The flow performs the actions, the checklist verifies them.

[[Advanced Users Guide#top|Back to top]]
== <span id="Creating_Custom_Flows">Creating Custom Flows and Checklists</span> ==
Always create a backup copy of your SOP file before making manual edits.

To add user-defined flows (for example: Single Engine and Go-Around):

Update the second line of your SOP file:<pre>
type;AIRBUS;;
user;Single_Eng;Go_Around;
</pre>Then add new phase lines at the end of your file:<pre>
13;2;Takeoff_Speeds;READBACK
13;2;Altitude;READBACK

14;2;Action;Value
14;2;Action;Value

15;2;Action;Value
15;2;Action;Value
</pre>Mapping:

* Phase 14 = Supplemental Flow One
* Phase 15 = Supplemental Flow Two
* Phase 16 = Supplemental Flow Three

Voice commands:

* “Supplemental checklist one”
* “Supplemental flow one”
[[Advanced Users Guide#top|Back to top]]

== <span id="Types">Set Commands</span> ==
<pre>PACKS: Sets packs according to the option selected on the FSFO Departure Performance page.
ALTITUDE: Sets the autopilot altitude to the Initial Altitude (or Planned Altitude) selected on the FSFO Flight Plan page.
HEADING: Sets the heading bug to the departure runway heading selected on the FSFO Departure Performance page.
AIRSPEED: Sets IAS to the V2 speed entered on the FSFO Departure Performance page.
AUTO_BRAKES: Sets according to the option selected on the FSFO Arrival Performance page.
FLAPS: Sets according to the option selected on the FSFO Departure Performance page.
COCKPIT_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
DOME_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
WING_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
ANTI-ICE: Turns ENGINE_ANTI_ICE and WING_ANTI_ICE ON when OAT < 10°C and precipitation is detected; otherwise OFF.</pre>

A SET Commands used during the flows will result in the above.

[[Advanced Users Guide#top|Back to top]]

== <span id="Flow_Commands">Flow Commands Explained</span> ==

=== LVAR ===
This command is intended for advanced users who are comfortable working with MSFS Local Variables (LVARs) and know how to acquire and use them. To use it, add the LVAR command, then enter the LVAR name, an equals sign (<code>=</code>), and the desired value/state (i.e., <code>LVAR_NAME=VALUE</code>). FSFO also supports PMDG Rotor Brake commands (Toggle and Push Only) by using the <code>ROTOR_BRAKE</code> option after <code>LVAR</code> in the format <code>ROTOR_BRAKE=<SwitchID>=<Label></code>. For example: <code>1;1;LVAR;ROTOR_BRAKE=101=Battery;</code> — in this case, <code>ROTOR_BRAKE</code> tells FSFO to use the Rotor Brake command type, <code>101</code> is the SwitchID, and <code>Battery</code> is the label that will be displayed (and spoken) on the SOPs page.

Format:<pre>
1;1;LVAR;XMLVAR_StandbyPower_Selector=1=Standby Power
1;1;LVAR;ROTOR_BRAKE=101=Battery
</pre>Meaning:

* XMLVAR_StandbyPower_Selector = LVAR name
* 1 = value
* Standby Power = Label that will be displayed (and spoken) on the SOPs page
Rotor_Brake Meaning:

* <code>ROTOR_BRAKE</code> = Tells FSFO to use the Rotor Brake command type
* 101 = SwitchID
* Battery = Label that will be displayed (and spoken) on the SOPs page
[[Advanced Users Guide#top|Back to top]]
----

=== SIMVAR ===
Used to control MSFS Simulation Variables.

Format:<pre>
1;1;SIMVAR;67271=1=Parking Brake
</pre>Meaning:

* SIMVAR = Tells FSFO to use the SIMVAR command type
* 67271 = SIMVAR control number
* 1 = value (ON)
* Parking Brake = abel that will be displayed (and spoken) on the SOPs page

----

=== Play_Sapi_Copilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Copilot voice selected in Settings. If no Copilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Sapi_Pilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Pilot voice selected in Settings. If no Pilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Wav ===
Plays a WAV file. You must enter the full path of the wav file.

Format:<pre>
1;1;Play_Wav;C:\Users\name\FSFO\boarding_Noise.wav
</pre>
----

=== Misc_Text ===
Displays reminder text under the Pilot section.

Example:<pre>
1;1;Misc_Text;Start ACARS
</pre>
----

=== Capt_Actions ===
Displays reminder text under the Captain Actions section.
----

=== Flight_Plan ===
Loads the most recent flight plan from:

C:\Users\[name]\AppData\Local\FSFO_V6\Download
----

=== Landing_Data ===
Reads back minimums and Vref speeds.
----

=== Fuel ===

* Load = FSFO will load the fuel amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Payload ===

* Load = FSFO will load the payload amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Loadsheet ===

* Confirm = Ground crew will confirm the aircraft is under Max Takeoff Weight (MTOW). If it is over MTOW, they will warn you and request that you check your loadsheet.

----

=== Doors ===

* Toggle_0 through Toggle_6 = Will open/close the doors; for example, Toggle_1 will open/close the 1L(Main) Door on most aircraft.

----

=== Walk_Around ===
While the default values are SHORT, MED, and LONG, advanced users can open the SOP text file and enter any numeric value (seconds) they like for the copilot to perform the walk-around. As an example:<pre>
1;1;WALK_AROUND;965
</pre>Defaults:

* SHORT = 150 seconds
* MED = 300 seconds
* LONG = 600 seconds

[[Advanced Users Guide#top|Back to top]]
== <span id="Smart_Flow_Tuning">Manually Update Smart Flow Options</span> ==
You can still manually update your SMART AutoFlow options by updating the userSettings.cfg file by following these steps:

# Close FSFO
# Navigate to C:\Users\[Your Name]\AppData\Local\FSFO_V6\UserData Folder
## You can also just click on the UserData button on FSFO’s front page
# Right-Click on userSettings.cfg and click Open with Notepad
# Locate and edit these lines1; '''ensure no trailing white space or empty lines'''
<pre>
Flows_PreFltStart=10
Flows_BeforeTakeoffStart=800
Flows_AfterTakeoffStart=3000
Flows_DescentStart=20
Flows_ApproachStart=10000
Flows_LndgStart=1500
</pre>Units:<pre>
Flows_PreFltStart = Seconds
Flows_BeforeTakeoffStart = Feet to runway threshold
Flows_AfterTakeoffStart = AGL feet
Flows_DescentStart = Nautical miles
Flows_ApproachStart = AGL feet
Flows_LndgStart = AGL feet
</pre>
[[Advanced Users Guide#top|Back to top]]
== <span id="Airport_Database">FSFO Airport Database Tool</span> ==
FSFO Make Runway is a separate program that builds the runway database using SIMCONNECT and MSFS APIs.

=== Installation ===
You can install it in two ways:

# From FSFO
## Click '''Get Started''' on the FSFO main page
## Click '''MAKE RWY''' on the New User window
## Follow the installation instructions
# Manually:
## Navigate to *\Flight Simulator First Officer V6\Res\Exe
### * represents your FSFO V6 directory; just right-click on the Flight Simulator First Officer V6 shortcut and select "Open File Location"
## Right-Click '''FSFO_Make_Runway.exe''' and Select "Run as Administrator"

----

=== Building the Database ===
[[File:MakeRwy.png|left|thumb]]

# Start MSFS or MSFS24 and load into the cockpit
# Click '''FSFO NAV PATH''' and select the FSFO NavData folder
# Click '''Connect'''
# Click '''Build'''

'''Note: This process can take over two hours.'''

----

=== Manual Database Updates ===
Runway data file:

* *\FSFO_V6\NavData\runways.csv
[[File:AirportDb.png|left|thumb|419x419px]]

'''Note 1 (Runway Code)''':
* Stored as a 3-digit code where the last digit indicates the side:
** 0 = none
** 1 = Left (L)
** 2 = Right (R)
** 3 = Center (C)
** 4 = Water (W)

* Examples:
** 330 = Runway 33
** 331 = Runway 33L
** 332 = Runway 33R
** 333 = Runway 33C
** 090 = Runway 9
** 091 = Runway 9L

'''Note 2 (Latitude/Longitude format):'''

* Lat/Lon values must be in decimal degrees (DD) format (example: 42.193545).
* Threshold lat/lon represent the runway threshold (AFCAD “runway start”).
'''Note 3 (Feet):'''

* Elevation, length, width, and threshold offset values are (must be) in feet.

'''Note 4 (Heading):'''

* Runway heading is the magnetic runway heading.

'''Note 5 (ILS frequency):'''

* ILS frequency is stored as nnn.nn (example: 109.50) or 0 if no ILS is available.

'''Note 6 (Magnetic variation):'''

* Magnetic variation (in degrees) is the value applied to convert magnetic to true heading: True Heading = Magnetic Heading + Magnetic Variation

[[Advanced Users Guide#top|Back to top]]
----

For standard setup and everyday operation, see [[Getting Started]] and [[User Settings Reference]].

Advanced Users Guide

2026-02-04T04:15:06Z

Kingm56: /* Flow Commands Explained */

= Advanced Users Guide =
This guide is intended for advanced FSFO users who want to manually customize SOPs, create their own flows and checklists, tune Smart Flows, and manage the FSFO airport database.

<span id="top"></span>
<div style="border:1px solid #aaa; background:#f9f9f9; padding:12px; width:320px; float:right; margin:0 0 15px 15px;">
'''Quick navigation'''<br />
Jump to a settings group:

* [[Advanced Users Guide#SOP_File_Location|SOP File Location]]
* [[Advanced Users Guide#SOP_File_Structure|SOP File Structure]]
* [[Advanced Users Guide#Phases|Phases]]
* [[Advanced Users Guide#Types|Types (Flow vs Checklist)]]
* [[Advanced Users Guide#Creating_Custom_Flows|Creating Custom Flows and Checklists]]
* [[Advanced Users Guide#Flow_Commands|Flow Commands Explained]]
* [[Advanced Users Guide#Smart_Flow_Tuning|Manually Update Smart Flow Options]]
* [[Advanced Users Guide#Airport_Database|FSFO Airport Database Tool]]
</div>
== <span id="SOP_File_Location">SOP File Location</span> ==
All SOPs are stored in:

C:\Users\[Your Name]\AppData\Local\FSFO_V6\FlowsChk

Replace '''[Your Name]''' with your Windows user name.

Each SOP file must begin with two required header lines:<pre>
type;AIRBUS;;
user;;;
</pre>

* The first line identifies the aircraft type (BOEING or AIRBUS).
* The second line is reserved for user-generated flows and checklists.

[[Advanced Users Guide#top|Back to top]]
== <span id="SOP_File_Structure">SOP File Structure</span> ==
Each line in an SOP file uses the following structure:<pre>
Phase;Type;System;Response
</pre>Example:<pre>
1;1;Auto_Brakes;MAX
</pre>Where:

* Phase = Flight phase number
* Type = Flow or Checklist
* System = Target system or command
* Response = Desired value or action

[[Advanced Users Guide#top|Back to top]]
== <span id="Phases">Phases</span> ==
The following numeric values define flight phases:<pre>
1 = Preflight or Cockpit Preparation
2 = Before Start
3 = Engine Start
4 = After Start
5 = Taxi
6 = Before Takeoff or Lineup
7 = After Takeoff
8 = Descent
9 = Approach
10 = Landing
11 = After Landing
12 = Shutdown or Parking
13 = Runway Change
100 = Turn Around
14 = User Defined
15 = User Defined
16 = User Defined
</pre>
[[Advanced Users Guide#top|Back to top]]
== <span id="Types">Types (Flow vs Checklist)</span> ==
<pre>
1 = Flow
2 = Checklist
</pre>

'''Flow''' A memorized, spatial sweep of switches and controls used to configure the aircraft. Flows are fast, heads-up, and done from memory.

'''Checklist''' A short, written challenge-response used to verify critical items are correctly set.

How they work together:

* Normal operations: Flow → Checklist
* Abnormal or emergencies: Use QRH or abnormal checklist

The flow performs the actions, the checklist verifies them.

[[Advanced Users Guide#top|Back to top]]
== <span id="Creating_Custom_Flows">Creating Custom Flows and Checklists</span> ==
Always create a backup copy of your SOP file before making manual edits.

To add user-defined flows (for example: Single Engine and Go-Around):

Update the second line of your SOP file:<pre>
type;AIRBUS;;
user;Single_Eng;Go_Around;
</pre>Then add new phase lines at the end of your file:<pre>
13;2;Takeoff_Speeds;READBACK
13;2;Altitude;READBACK

14;2;Action;Value
14;2;Action;Value

15;2;Action;Value
15;2;Action;Value
</pre>Mapping:

* Phase 14 = Supplemental Flow One
* Phase 15 = Supplemental Flow Two
* Phase 16 = Supplemental Flow Three

Voice commands:

* “Supplemental checklist one”
* “Supplemental flow one”
[[Advanced Users Guide#top|Back to top]]

== <span id="Types">Set Commands</span> ==
<pre>PACKS: Sets packs according to the option selected on the FSFO Departure Performance page.
ALTITUDE: Sets the autopilot altitude to the Initial Altitude (or Planned Altitude) selected on the FSFO Flight Plan page.
HEADING: Sets the heading bug to the departure runway heading selected on the FSFO Departure Performance page.
AIRSPEED: Sets IAS to the V2 speed entered on the FSFO Departure Performance page.
AUTO_BRAKES: Sets according to the option selected on the FSFO Arrival Performance page.
FLAPS: Sets according to the option selected on the FSFO Departure Performance page.
COCKPIT_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
DOME_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
WING_LIGHTS: Turns ON during night, dawn, and dusk; OFF during daytime.
ANTI-ICE: Turns ENGINE_ANTI_ICE and WING_ANTI_ICE ON when OAT < 10°C and precipitation is detected; otherwise OFF.</pre>

A SET Commands used during the flows will result in the above.

[[Advanced Users Guide#top|Back to top]]

== <span id="Flow_Commands">Flow Commands Explained</span> ==

=== LVAR ===
This command is intended for advanced users who are comfortable working with MSFS Local Variables (LVARs) and know how to acquire and use them. To use it, add the LVAR command, then enter the LVAR name, an equals sign (<code>=</code>), and the desired value/state (i.e., <code>LVAR_NAME=VALUE</code>). FSFO also supports PMDG Rotor Brake commands (Toggle and Push Only) by using the <code>ROTOR_BRAKE</code> option after <code>LVAR</code> in the format <code>ROTOR_BRAKE=<SwitchID>=<Label></code>. For example: <code>1;1;LVAR;ROTOR_BRAKE=101=Battery;</code> — in this case, <code>ROTOR_BRAKE</code> tells FSFO to use the Rotor Brake command type, <code>101</code> is the SwitchID, and <code>Battery</code> is the label that will be displayed (and spoken) on the SOPs page.

Format:<pre>
1;1;LVAR;XMLVAR_StandbyPower_Selector=1=Standby Power
1;1;LVAR;ROTOR_BRAKE=101=Battery
</pre>Meaning:

* XMLVAR_StandbyPower_Selector = LVAR name
* 1 = value
* Standby Power = Label that will be displayed (and spoken) on the SOPs page
Rotor_Brake Meaning:

* <code>ROTOR_BRAKE</code> = Tells FSFO to use the Rotor Brake command type
* 101 = SwitchID
* Battery = Label that will be displayed (and spoken) on the SOPs page

----

=== SIMVAR ===
Used to control MSFS Simulation Variables.

Format:<pre>
1;1;SIMVAR;67271=1=Parking Brake
</pre>Meaning:

* SIMVAR = Tells FSFO to use the SIMVAR command type
* 67271 = SIMVAR control number
* 1 = value (ON)
* Parking Brake = abel that will be displayed (and spoken) on the SOPs page

----

=== Play_Sapi_Copilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Copilot voice selected in Settings. If no Copilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Sapi_Pilot ===
FSFO will use Microsoft SAPI to speak the text you enter using the Pilot voice selected in Settings. If no Pilot SAPI voice is selected, FSFO will use the Windows default SAPI voice.
----

=== Play_Wav ===
Plays a WAV file. You must enter the full path of the wav file.

Format:<pre>
1;1;Play_Wav;C:\Users\name\FSFO\boarding_Noise.wav
</pre>
----

=== Misc_Text ===
Displays reminder text under the Pilot section.

Example:<pre>
1;1;Misc_Text;Start ACARS
</pre>
----

=== Capt_Actions ===
Displays reminder text under the Captain Actions section.
----

=== Flight_Plan ===
Loads the most recent flight plan from:

C:\Users\[name]\AppData\Local\FSFO_V6\Download
----

=== Landing_Data ===
Reads back minimums and Vref speeds.
----

=== Fuel ===

* Load = FSFO will load the fuel amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Payload ===

* Load = FSFO will load the payload amount shown on the FSFO Flight Plan page (typically pulled from SimBrief, if used) into your aircraft. Do not use this option with third-party aircraft that specifically require fueling through the EFB and/or FMC; doing so may result in incorrect weight and center-of-gravity values.
* Readback = Copilot will read back your aircraft s current fuel value in pounds or kilograms, depending on whether the FSFO Kilogram setting is enabled.

----

=== Loadsheet ===

* Confirm = Ground crew will confirm the aircraft is under Max Takeoff Weight (MTOW). If it is over MTOW, they will warn you and request that you check your loadsheet.

----

=== Doors ===

* Toggle_0 through Toggle_6 = Will open/close the doors; for example, Toggle_1 will open/close the 1L(Main) Door on most aircraft.

----

=== Walk_Around ===
While the default values are SHORT, MED, and LONG, advanced users can open the SOP text file and enter any numeric value (seconds) they like for the copilot to perform the walk-around. As an example:<pre>
1;1;WALK_AROUND;965
</pre>Defaults:

* SHORT = 150 seconds
* MED = 300 seconds
* LONG = 600 seconds

[[Advanced Users Guide#top|Back to top]]
----

== <span id="Smart_Flow_Tuning">Manually Update Smart Flow Options</span> ==
You can still manually update your SMART AutoFlow options by updating the userSettings.cfg file by following these steps:

# Close FSFO
# Navigate to C:\Users\[Your Name]\AppData\Local\FSFO_V6\UserData Folder
## You can also just click on the UserData button on FSFO’s front page
# Right-Click on userSettings.cfg and click Open with Notepad
# Locate and edit these lines1; '''ensure no trailing white space or empty lines'''
<pre>
Flows_PreFltStart=10
Flows_BeforeTakeoffStart=800
Flows_AfterTakeoffStart=3000
Flows_DescentStart=20
Flows_ApproachStart=10000
Flows_LndgStart=1500
</pre>Units:<pre>
Flows_PreFltStart = Seconds
Flows_BeforeTakeoffStart = Feet to runway threshold
Flows_AfterTakeoffStart = AGL feet
Flows_DescentStart = Nautical miles
Flows_ApproachStart = AGL feet
Flows_LndgStart = AGL feet
</pre>
[[Advanced Users Guide#top|Back to top]]
----

== <span id="Airport_Database">FSFO Airport Database Tool</span> ==
FSFO Make Runway is a separate program that builds the runway database using SIMCONNECT and MSFS APIs.

=== Installation ===
You can install it in two ways:

# From FSFO
## Click '''Get Started''' on the FSFO main page
## Click '''MAKE RWY''' on the New User window
## Follow the installation instructions
# Manually:
## Navigate to *\Flight Simulator First Officer V6\Res\Exe
### * represents your FSFO V6 directory; just right-click on the Flight Simulator First Officer V6 shortcut and select "Open File Location"
## Right-Click '''FSFO_Make_Runway.exe''' and Select "Run as Administrator"

----

=== Building the Database ===
[[File:MakeRwy.png|left|thumb]]

# Start MSFS or MSFS24 and load into the cockpit
# Click '''FSFO NAV PATH''' and select the FSFO NavData folder
# Click '''Connect'''
# Click '''Build'''

'''Note: This process can take over two hours.'''

----

=== Manual Database Updates ===
Runway data file:

* *\FSFO_V6\NavData\runways.csv
[[File:AirportDb.png|left|thumb|419x419px]]

'''Note 1 (Runway Code)''':
* Stored as a 3-digit code where the last digit indicates the side:
** 0 = none
** 1 = Left (L)
** 2 = Right (R)
** 3 = Center (C)
** 4 = Water (W)

* Examples:
** 330 = Runway 33
** 331 = Runway 33L
** 332 = Runway 33R
** 333 = Runway 33C
** 090 = Runway 9
** 091 = Runway 9L

'''Note 2 (Latitude/Longitude format):'''

* Lat/Lon values must be in decimal degrees (DD) format (example: 42.193545).
* Threshold lat/lon represent the runway threshold (AFCAD “runway start”).
'''Note 3 (Feet):'''

* Elevation, length, width, and threshold offset values are (must be) in feet.

'''Note 4 (Heading):'''

* Runway heading is the magnetic runway heading.

'''Note 5 (ILS frequency):'''

* ILS frequency is stored as nnn.nn (example: 109.50) or 0 if no ILS is available.

'''Note 6 (Magnetic variation):'''

* Magnetic variation (in degrees) is the value applied to convert magnetic to true heading: True Heading = Magnetic Heading + Magnetic Variation

[[Advanced Users Guide#top|Back to top]]
----

For standard setup and everyday operation, see [[Getting Started]] and [[User Settings Reference]].

Advanced Users Guide

2026-02-04T03:47:52Z

Kingm56: /* FSFO Airport Database Tool */

Advanced Users Guide

2026-02-04T03:46:15Z

Kingm56: /* Manual Database Updates */

Advanced Users Guide

2026-02-04T03:46:01Z

Kingm56: /* Manual Database Updates */

Advanced Users Guide

2026-02-04T03:45:49Z

Kingm56: /* Manual Database Updates */