User Manual

1. Introduction

1.1 What is StreamFlight?

StreamFlight is a standalone flight-simulation companion designed to bring flight information, live simulator telemetry, streaming tools, flight-awareness features and external integrations together in a single application.

One Companion. Every Sim. Every Flight.

StreamFlight connects directly to supported flight simulators and monitors your flight as it happens. It can display information such as aircraft type, callsign, altitude, speed, heading, vertical speed, weather, distance to destination, estimated time en route, estimated time of arrival and overall flight progress.

Flight information can be obtained automatically from SimBrief or entered manually, allowing StreamFlight to be used whether you fly detailed planned airline operations or simply want to start the simulator and fly.

StreamFlight also includes features extending beyond basic telemetry, including:

• Gamer Mode flight-information displays
• OBS / Streamlabs Desktop browser-based overlays
• Control Input Display
• Automatic Flight Phase Detection
• Camera Control tools
• Runway Awareness and Advisory System (RAAS)
• Landing Rate detection and display
• Live ATC information using VATSIM and IVAO
• Passenger Manifest and viewer check-in
• Output files for integration with OBS / Streamlabs Desktop, chatbot and automation software, and other applications

StreamFlight runs independently from the simulator and does not require installation into the simulator's Community folder or aircraft directories.

1.2 One Companion. Every Sim. Every Flight.

StreamFlight has been designed around a simple principle:

One Companion. Every Sim. Every Flight.

Rather than being tied to a particular aircraft, airline, simulator or style of flying, StreamFlight provides a common set of flight tools that can accompany different types of simulator flying.

You might use StreamFlight for a scheduled airline flight using a SimBrief flight plan, a short general-aviation trip entered manually, an online flight using VATSIM or IVAO, or a flight being broadcast through OBS / Streamlabs Desktop.

The interface and available features remain familiar even when moving between supported simulators.

Some advanced features depend on capabilities provided by a particular simulator and are therefore not available on every supported platform. These differences are identified throughout this manual where relevant.

1.3 Who is StreamFlight For?

StreamFlight is designed for both streamers and non-streamers.

Flight Simulation Users

You do not need to stream to use StreamFlight.

Gamer Mode allows flight information to be displayed directly on your monitor, providing a convenient companion display while flying.

StreamFlight can monitor the progress of your flight, automatically determine the current flight phase, calculate and display useful flight information, provide runway-awareness announcements, detect your landing rate and provide other information without requiring OBS / Streamlabs Desktop or a streaming platform.

Streamers and Content Creators

For streamers, StreamFlight provides browser-based overlays and output files that can be incorporated into applications such as OBS / Streamlabs Desktop.

These can be used to show viewers live information about the flight without requiring the streamer to manually update text throughout the journey.

Depending on the feature being used, a stream can display information such as:

• Callsign
• Aircraft type
• Departure and destination
• Altitude
• Speed
• Heading
• Vertical speed
• Wind and temperature
• Distance to destination
• ETE and ETA
• Flight progress
• Current flight phase
• Control inputs
• Landing rate
• Live ATC information

StreamFlight can also work with Streamer.bot or other compatible chatbot/automation software, allowing StreamFlight information and interactive features to be incorporated into a live-stream chat.

The Passenger Manifest, for example, can be integrated with compatible automation software to allow viewers to check in for the current flight and receive an assigned seat.

OBS / Streamlabs Desktop and chatbot/automation software are optional integrations and are not required for normal StreamFlight operation.

1.4 Supported Flight Simulators

StreamFlight v3.0.0 supports the following flight simulators:

Microsoft Flight Simulator

• Microsoft Flight Simulator 2020
• Microsoft Flight Simulator 2024

StreamFlight communicates with Microsoft Flight Simulator using SimConnect.

MSFS currently provides the broadest StreamFlight feature support, including features that depend on simulator-specific functionality such as Camera Control, Control Input Display and RAAS.

X-Plane

• X-Plane 11
• X-Plane 12

StreamFlight communicates with X-Plane using XPUIPC.

Some initial X-Plane configuration is required before StreamFlight can receive simulator data. The installation and configuration procedure is covered later in this manual.

Prepar3D

StreamFlight supports compatible Prepar3D installations through FSUIPC.

As with X-Plane, some StreamFlight functionality may differ from that available when using Microsoft Flight Simulator.

1.5 Overview of StreamFlight Features

StreamFlight v3.0.0 combines several flight-simulation tools within one application.

Flight Planning and SimBrief

StreamFlight can retrieve flight information from SimBrief, including the flight callsign, aircraft, departure and destination airports, cruise level, route, weather and passenger information.

SimBrief is optional. Flight details can also be entered manually.

Live Flight Telemetry

While connected to a supported simulator, StreamFlight monitors live simulator information including altitude, speed, heading, vertical speed, position, wind and outside air temperature.

This information is used both for display and by other StreamFlight systems.

Flight Progress

StreamFlight tracks the progress of the flight and provides information including:

• Distance to Go (DTG)
• Estimated Time En Route (ETE)
• Estimated Time of Arrival (ETA)
• Flight progress
• Current flight phase

Flight phases can normally be detected automatically, while a manual override is available when required.

Gamer Mode

Gamer Mode allows StreamFlight information to be displayed directly on the simulator computer without requiring streaming software.

Different display templates and positioning options allow the information to be presented according to the user's preference.

Streaming Overlays

StreamFlight provides browser-based sources that can be added to OBS / Streamlabs Desktop and other compatible applications.

This allows live flight information to become part of a stream layout while StreamFlight continues updating the information automatically.

StreamFlight also supports network operation for users running their simulator and streaming software on separate computers.

Control Input Display

On supported simulators, the Control Input Display provides a graphical representation of:

• Pitch
• Roll
• Rudder
• Throttle

The display can be incorporated into OBS / Streamlabs Desktop as a browser source.

Camera Control

StreamFlight includes built-in camera tools for Microsoft Flight Simulator.

The Orbit camera creates an external camera movement around the aircraft, while FlyBy provides a moving external view intended to create a fly-past style shot.

Camera parameters can be adjusted from within StreamFlight, and the camera can be returned to the normal cockpit view when the effect is complete.

StreamFlight camera control can also be disabled when another camera system, such as P42 ChasePlane, is being used.

RAAS

The Runway Awareness and Advisory System (RAAS) provides runway-related audio announcements during relevant stages of flight.

Available announcements include:

• Approaching Runway
• On Runway
• Runway Remaining
• Caution Short Runway
• Long Landing

RAAS is currently available for Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024.

Landing Rate

StreamFlight can detect touchdown and record the aircraft's landing rate in feet per minute.

The landing can also be assigned a classification ranging from a particularly smooth landing through increasingly firm landings.

Landing Rate information can be displayed in Gamer Mode, presented through a dedicated OBS / Streamlabs Desktop browser source and made available for external integrations.

Live ATC

StreamFlight can use information from VATSIM and IVAO to identify relevant online ATC information.

When the aircraft's COM1 radio is tuned to an online controller, StreamFlight can match the frequency with available network data and provide controller/station information.

VATSIM CTAF information can also be used where applicable.

Passenger Manifest

The Passenger Manifest provides an interactive feature particularly suited to live streaming.

Passenger capacity can be obtained from flight information, and viewers can check in for the flight and receive an automatically assigned seat.

The manifest tracks checked-in passengers, allocated seats and remaining capacity throughout the flight.

When combined with Streamer.bot or other compatible chatbot/automation software, commands can be provided to allow viewers to check in, retrieve their assigned seat and see current passenger information directly from stream chat.

The Streamer.bot examples provided later in this manual demonstrate one way of implementing this integration. Other compatible chatbot or automation applications may also be used, although their configuration will differ.

Output Files and External Integration

StreamFlight writes a range of flight information to the user-selected Output Folder.

These files allow other applications to use StreamFlight data without needing direct access to the simulator.

Typical integrations include:

• OBS / Streamlabs Desktop
• Streamer.bot or other compatible chatbot/automation software
• Custom stream layouts
• Automation tools
• User-created applications and scripts

The complete set of user-facing Output Folder files is documented in Chapter 13.

1.6 StreamFlight for Streamers

Although StreamFlight provides extensive streaming functionality, streaming is only one part of the application.

When used as part of a streaming setup, StreamFlight can reduce the amount of information that needs to be updated manually during a flight.

For example, a flight-information overlay can automatically follow the aircraft from preflight through departure, cruise, arrival and landing while continually updating the information presented to viewers.

Separate browser sources are available for specialised features such as the Control Input Display and Landing Rate.

StreamFlight's output files also allow individual values to be incorporated into custom OBS / Streamlabs Desktop layouts. This provides greater flexibility for users who prefer to build their own stream graphics rather than use the supplied browser overlay.

Users with a dedicated streaming computer can use StreamFlight's network options to make supported browser sources available across the local network.

The Passenger Manifest extends this integration further by allowing viewers to participate in the flight rather than simply watch it.

Streamer.bot is used for the chatbot/automation examples in this manual. Other compatible chatbot or automation software may also be used with StreamFlight where it can consume the relevant output files or services.

Streaming configuration and OBS / Streamlabs Desktop setup are covered in detail later in this manual.

1.7 StreamFlight for Non-Streamers

OBS / Streamlabs Desktop is not required to use StreamFlight.

Users who do not stream can use StreamFlight as a standalone flight companion.

Gamer Mode can display useful flight information directly on the simulator computer, while features such as automatic flight-phase detection, flight progress, Landing Rate, Camera Control, Live ATC information and RAAS can be used independently of a live stream.

This means StreamFlight can be used simply as an additional source of flight information and functionality during normal simulator flying.

Users who have no interest in OBS / Streamlabs Desktop, chatbot/automation software or live-stream chat can ignore those integration sections of this manual without affecting normal StreamFlight operation.

1.8 System Requirements

StreamFlight is a Windows desktop application.

To use StreamFlight, you will require:

• A compatible Windows PC
• StreamFlight v3.0.0 installed and activated
• At least one supported flight simulator
• The appropriate simulator interface where required

Depending on the simulator being used:

Microsoft Flight Simulator 2020 / 2024
Uses SimConnect communication.

X-Plane 11 / 12
Requires XPUIPC and the appropriate StreamFlight/XPUIPC configuration.

Prepar3D
Requires the appropriate FSUIPC installation.

An internet connection is required for functionality that retrieves information from online services, including features such as:

• SimBrief
• VATSIM
• IVAO
• Licence activation and related licence operations

OBS / Streamlabs Desktop is required only when StreamFlight browser sources or other streaming-software integration is being used.

Streamer.bot or other compatible chatbot/automation software is required only when using the corresponding automation or chat-integration features.

1.9 Feature Availability by Simulator

StreamFlight supports multiple flight simulators, but the available functionality is not identical across all platforms.

Core functionality such as flight information and supported telemetry is available across the supported simulator families, while certain advanced features rely on simulator-specific interfaces.

For example, StreamFlight v3.0.0 provides MSFS-specific functionality including:

• Camera Control
• Control Input Display
• RAAS

Other features may be available across multiple simulators but can behave differently because of differences in the data supplied by each simulator.

Throughout this manual, simulator-specific requirements are identified using notes where they are relevant to a particular feature.

A complete Simulator Feature Compatibility Matrix is provided in Chapter 16 for quick reference.

1.10 About This Manual

This manual covers StreamFlight v3.0.0 and is intended primarily as an end-user guide.

It explains how to install, configure and operate StreamFlight, as well as how to integrate its features with OBS / Streamlabs Desktop, Streamer.bot and other compatible software where required.

The manual is organised so that new users can begin with installation and their first flight before moving into individual StreamFlight features.

Later chapters provide detailed configuration, troubleshooting and reference information.

Throughout the manual, the following conventions are used:

NOTE
Provides additional information, clarification or useful guidance.

IMPORTANT
Identifies information that should be understood before continuing or that can materially affect the operation of a feature.

WARNING
Identifies an action or condition that may cause an unwanted result and requires particular attention.

Names of buttons, checkboxes, tabs and other controls are shown using their names as they appear in StreamFlight.

File names are shown in a distinct form, for example altitude.txt.

Chat commands are shown in a similar form, for example !checkin.

Port numbers are shown numerically, for example 38086.

Where instructions apply only to a particular simulator, this is identified explicitly.

Screenshots and figures used throughout the manual are intended to illustrate the relevant controls and configuration. Minor visual differences may occur between StreamFlight revisions.

2. Installation, Licensing & First Launch

This chapter explains how to install and activate StreamFlight, become familiar with the main interface, select the required Output Folder and establish the initial connection to your flight simulator.

It also introduces Dual-PC operation for users who run their simulator and streaming software on separate computers.

By the end of this chapter, StreamFlight should be ready for your first flight.

2.1 Installing StreamFlight

StreamFlight v3.1.0 is supplied as a ZIP archive and does not use a traditional Windows installer.

To install StreamFlight:

1. Download the StreamFlight ZIP file supplied with your purchase.
2. Choose a permanent location on your computer for StreamFlight.
3. Extract the entire contents of the ZIP archive to that location.
4. Open the extracted StreamFlight folder.
5. Run the StreamFlight application.

Choosing an Installation Location

StreamFlight can be placed in a folder of your choice. A dedicated permanent location is recommended, for example:

or:

The Windows Downloads folder can also be used, but it is not recommended as a permanent location. Downloads is commonly used for temporary files and may be periodically cleaned or reorganised.

Choose a location where you intend StreamFlight to remain.

StreamFlight is a standalone application. It does not need to be placed in the Microsoft Flight Simulator Community folder, the X-Plane directory, the Prepar3D directory, or an aircraft folder.

The StreamFlight Output Folder, which is used for generated flight and integration data, is separate from the application folder and will be configured later in this chapter.

Once the files have been extracted, start StreamFlight. On first launch, the Licence Activation window will be displayed automatically.

2.2 Starting StreamFlight for the First Time

When StreamFlight starts, it first checks for a valid activation.

If the computer has not previously been activated, the StreamFlight Licence Activation window is displayed before the main application opens.

The activation window contains:

• Licence Key field
• ACTIVATE button
• Activation status area

Enter the licence key supplied with your StreamFlight purchase and select ACTIVATE.

While StreamFlight contacts the licence service, the status will show that activation is in progress.

When activation succeeds, StreamFlight confirms:

Licence Activated Successfully.

The activation window then closes and the main StreamFlight application opens.

If activation fails, StreamFlight displays the error returned by the activation process. Check that the licence key has been entered correctly and that the computer has an active internet connection before trying again.

2.3 Activating Your Licence

Your StreamFlight licence is associated with an activation on the computer on which StreamFlight is being used.

The licence key should be entered exactly as supplied with your purchase.

After successful activation, StreamFlight stores the activation information required for subsequent launches. You do not normally need to enter the licence key every time StreamFlight starts.

On later launches, StreamFlight checks the stored activation.

If the licence service cannot temporarily be reached but StreamFlight has a valid locally stored activation, the application can continue to use that valid activation.

If StreamFlight determines that the stored licence data is invalid or corrupted, the following warning is displayed:

LICENCE DATA INVALID

You will then be asked to activate StreamFlight again.

2.4 Licence Information

Once StreamFlight is running, information about the currently activated licence can be viewed from:

User Settings → ABOUT / LICENCE

Selecting ABOUT / LICENCE opens the StreamFlight Licence Information window.

The window displays:

• Product
• Application version
• Licence ID
• Customer
• Email
• Licence Version
• Status

For an active installation, the licence status is shown as:

Active

The Licence Information window also provides controls for deactivating or transferring the licence.

2.5 Deactivating a Licence

The DEACTIVATE LICENCE option releases the StreamFlight activation from the current computer.

Open:

User Settings → ABOUT / LICENCE

and select:

DEACTIVATE LICENCE

StreamFlight asks for confirmation before proceeding.

If confirmed, StreamFlight contacts the licence service and deactivates the licence on the current computer.

A successful deactivation is confirmed with:

The StreamFlight licence has been deactivated on this computer.

If StreamFlight is subsequently started on that computer, activation will be required again.

2.6 Transferring StreamFlight to Another Computer

If you are moving StreamFlight to another computer, use the built-in licence transfer function rather than simply abandoning the existing activation.

On the computer where StreamFlight is currently activated, open:

User Settings → ABOUT / LICENCE

and select:

TRANSFER LICENCE

StreamFlight explains that the current computer will be deactivated and that StreamFlight will require activation again the next time it starts on that computer.

Confirm the transfer when you are ready to proceed.

Once the licence has successfully been released, StreamFlight displays:

The StreamFlight licence has been released from this computer.

You can then extract StreamFlight on the new computer and activate it using your original licence key.

2.7 Understanding the StreamFlight Interface

After successful activation, the main StreamFlight window opens.

The v3.0.0 interface is divided into a series of tabs, with common simulator and status information remaining accessible from the main application window.

The primary tabs are:

• Flight Plan
• Overlays
• FIDS Overlay
• Camera Control
• RAAS
• User Settings

Each tab groups related StreamFlight functions together.

The main interface also provides visual information about simulator connectivity.

StreamFlight automatically determines which supported simulator interface it is communicating with rather than requiring you to manually select MSFS, X-Plane or Prepar3D for each flight.

The individual tabs are introduced below and covered in detail in later chapters.

New in 3.1.0: The Flight Planner tab appears before Flight Setup and lets you search airline routes by airports, airline, aircraft, duration and distance. Double-click a result to continue to SimBrief. See Section 3.19 — Integrated Flight Planner for full instructions.

2.8 Flight Plan Tab

The Flight Plan tab is the main starting point when preparing StreamFlight for a flight.

It allows you to create or load flight information using either:

• SimBrief
• Manual Flight Details

Depending on how the flight is configured, this area contains information such as:

• Aircraft type
• Callsign
• Departure airport
• Destination airport
• Cruise flight level
• Route information
• Destination information
• SimBrief flight information

You are not required to use SimBrief. StreamFlight can also operate using manually entered flight details.

Flight planning and SimBrief are covered fully in Chapter 3 — Flight Planning & SimBrief.

2.9 Overlays Tab

The Overlays tab contains StreamFlight's display and streaming-related functionality.

This area provides access to features including:

• Gamer Mode
• Monitor Overlay
• Overlay templates
• Overlay positioning
• Live Flight Telemetry browser source
• Control Input Display
• Landing Rate display options
• Browser-source configuration
• Dual-PC / LAN options

Browser sources can be used with OBS / Streamlabs Desktop and other compatible software.

You do not need streaming software to use StreamFlight. Gamer Mode provides on-screen information for users who simply want StreamFlight available while they fly.

Overlay functionality is covered in Chapter 5 — Overlays & Gamer Mode, with the Control Input Display covered separately in Chapter 6 — Control Input Display.

2.10 FIDS Tab

Introduced in StreamFlight 3.1.5, the FIDS tab provides airport-style Departures and Arrivals boards using live VATSIM and IVAO traffic. Your flight is highlighted and board visibility is managed automatically as the flight progresses.

See Chapter 13 — Flight Information Display System (FIDS) for configuration, OBS setup and troubleshooting.

2.11 Camera Control Tab

The Camera Control tab provides StreamFlight's built-in camera tools for Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024.

The two primary camera modes are:

Orbit
Moves the external camera around the aircraft.

FlyBy
Creates a moving external fly-past style camera view.

Controls are provided for adjusting the behaviour of each camera mode.

The tab also provides the option to disable StreamFlight Camera Controls when using an external camera system such as P42 ChasePlane.

Camera Control is covered fully in Chapter 7 — Camera Control.

2.12 RAAS Tab

The RAAS tab contains the configuration for StreamFlight's Runway Awareness and Advisory System.

RAAS provides runway-related audio announcements for supported Microsoft Flight Simulator operations.

Available announcement categories include:

• Approaching Runway
• On Runway
• Runway Remaining
• Caution Short Runway
• Long Landing

The tab also provides controls for audio output, volume and other RAAS preferences.

RAAS is covered fully in Chapter 8 — RAAS: Runway Awareness & Advisory System.

2.13 User Settings Tab

The User Settings tab contains general StreamFlight configuration.

This includes the Output Folder, which is one of the most important initial StreamFlight settings.

The tab also provides access to:

ABOUT / LICENCE

for viewing and managing the StreamFlight licence.

Other simulator and application configuration covered by the User Settings area is explained in detail in Chapter 14 — User Settings & X-Plane Configuration.

2.14 Selecting the Output Folder

StreamFlight requires an Output Folder before it can save flight and overlay data.

The Output Folder is a location selected by you where StreamFlight writes the user-facing data files generated during operation.

These files can subsequently be used by StreamFlight features and external applications such as:

• OBS / Streamlabs Desktop
• Streamer.bot or other compatible chatbot/automation software
• Custom overlays
• Automation software
• User-created scripts and applications

To select the Output Folder:

1. Open the User Settings tab.
2. Locate Output Folder.
3. Select BROWSE.
4. Select an existing folder or create a new folder.
5. Confirm the selection.

Once selected, StreamFlight creates and initialises the required user-facing output files and confirms the selected location.

If you attempt to select the StreamFlight application folder, StreamFlight displays an Invalid Output Folder warning.

Instead, choose a separate location or create a dedicated folder for StreamFlight output data.

For example:

The exact location is your choice.

A dedicated folder is recommended because StreamFlight creates and continually updates a number of files while it is running.

Once configured, StreamFlight remembers the selected Output Folder.

The contents and purpose of the user-facing files created in this folder are covered in Chapter 13 — Output Files & External Integration.

2.15 Simulator Detection

StreamFlight supports:

• Microsoft Flight Simulator 2020
• Microsoft Flight Simulator 2024
• X-Plane 11
• X-Plane 12
• Prepar3D

StreamFlight automatically detects and connects to the appropriate simulator interface.

You do not normally need to tell StreamFlight which simulator you are about to use.

Microsoft Flight Simulator 2020 / 2024

StreamFlight communicates with Microsoft Flight Simulator using SimConnect.

For normal MSFS operation, start Microsoft Flight Simulator and StreamFlight. Once simulator data becomes available, StreamFlight establishes the connection automatically.

No XPUIPC or FSUIPC installation is required for StreamFlight's normal MSFS SimConnect connection.

X-Plane 11 / 12

StreamFlight communicates with X-Plane through XPUIPC.

For X-Plane operation, StreamFlight needs to know the location of your X-Plane installation and XPUIPC must be correctly installed.

If StreamFlight cannot find XPUIPC, it identifies the configuration as:

Missing XPUIPC

and provides instructions for installing the supplied XPUIPC files into:

X-Plane\Resources\plugins

After installing XPUIPC, X-Plane must be restarted before the newly installed plugin can be used.

StreamFlight may therefore display:

Restart X-PLANE

when a restart is required.

Detailed X-Plane path selection, XPUIPC installation and StreamFlight's XPUIPC configuration are covered in Chapter 14 — User Settings & X-Plane Configuration.

Prepar3D

StreamFlight communicates with Prepar3D through FSUIPC6.

When the appropriate Prepar3D/FSUIPC environment is running and available, StreamFlight can detect and use that connection automatically.

Detailed Prepar3D configuration and troubleshooting are covered later in this manual.

Connection Status

The StreamFlight interface indicates whether a supported simulator has been detected and whether StreamFlight is receiving simulator data.

2.16 Dual-PC Streaming Setups

StreamFlight supports users who run their flight simulator and streaming software on separate computers.

A typical Dual-PC streaming setup consists of:

Simulator PC

• Runs the flight simulator
• Runs StreamFlight
• Receives the live simulator data

Streaming PC

• Runs OBS / Streamlabs Desktop
• Receives supported StreamFlight browser sources across the local network

This allows the simulator workload and streaming workload to be separated while StreamFlight continues to obtain its live flight information directly from the simulator computer.

StreamFlight includes a Dual PC Setup / LAN Mode option that allows supported browser sources to be accessed from another computer on the same local network.

When Dual-PC / LAN Mode is enabled, the browser-source address used by the streaming computer differs from the normal local address used when StreamFlight and the streaming software are running on the same computer.

For a normal single-PC setup, no Dual-PC configuration is required.

Detailed Dual-PC configuration, browser-source addresses and network considerations are covered in Chapter 5 — Overlays & Gamer Mode.

2.17 First-Flight Quick Start

Once StreamFlight is installed and activated, only a few steps are required to prepare it for a basic first flight.

Step 1 — Start StreamFlight

Open the folder where you extracted StreamFlight and start the StreamFlight application.

The main application should open without requesting activation if the computer has already been successfully activated.

Step 2 — Select the Output Folder

Open:

User Settings

and select a dedicated Output Folder if one has not already been configured.

Step 3 — Start Your Flight Simulator

Start one of the supported simulators:

• Microsoft Flight Simulator 2020
• Microsoft Flight Simulator 2024
• X-Plane 11
• X-Plane 12
• Prepar3D

For X-Plane and Prepar3D, make sure the required simulator interface has already been installed and configured.

Step 4 — Confirm the Simulator Connection

Wait for StreamFlight to detect the simulator.

The StreamFlight status area should indicate that the simulator has been detected and that data is being received.

Step 5 — Enter or Load Your Flight

Open the Flight Plan tab.

You can either:

• Fetch your flight from SimBrief, or
• Enter the required flight information manually.

You do not need SimBrief to use StreamFlight.

Detailed flight-plan configuration is covered in Chapter 3 — Flight Planning & SimBrief.

Step 6 — Fly

Once StreamFlight has a valid simulator connection and the required flight information, it can begin monitoring your flight.

Depending on the simulator and features you choose to use, StreamFlight can then:

• Monitor live telemetry
• Track flight progress
• Detect flight phases
• Calculate DTG, ETE and ETA
• Update the Output Folder
• Display Gamer Mode information
• Provide browser-source data
• Monitor Live ATC
• Detect your landing rate
• Provide RAAS announcements
• Operate supported camera tools
• Support Passenger Manifest integrations

You can enable and configure these features as required.

At this point, StreamFlight is installed, activated and ready to accompany your flights.

The next chapter explains how to create or load the flight information StreamFlight will use.

3. Flight Planning & SimBrief

StreamFlight uses basic flight information to identify the flight you are operating and to support features such as flight progress, overlays, airport information, weather, Passenger Manifest and external integrations.

Flight information can be provided in two ways:

• Fetching an existing flight from SimBrief
• Entering the required flight details manually

SimBrief is optional. You can use StreamFlight without a SimBrief account or flight plan, although some information that originates specifically from a SimBrief Operational Flight Plan (OFP) will not be available when using manual flight details alone.

3.1 Flight Information Overview

The Flight Plan tab is where the primary information for the current flight is entered or retrieved.

The main flight information includes:

• Aircraft type
• Callsign
• Departure ICAO
• Destination ICAO
• Cruise Flight Level
• Destination latitude
• Destination longitude
• Destination elevation

When SimBrief is used, StreamFlight can additionally retrieve information including:

• Planned route
• Planned departure runway
• Planned destination runway
• Departure METAR
• Destination METAR
• Planned route distance
• Planned passenger count

StreamFlight also uses its included airport database to obtain supporting information about the departure and destination airports.

3.2 Using SimBrief

SimBrief is an online flight-planning service commonly used in flight simulation.

If you prepare your flight using SimBrief, StreamFlight can retrieve information from your latest SimBrief flight plan rather than requiring you to enter the main flight details manually.

To use SimBrief with StreamFlight:

1. Create or generate your flight plan in SimBrief.
2. Open StreamFlight.
3. Open the Flight Plan tab.
4. Enter your SimBrief Pilot ID.
5. Select Fetch SimBrief.

StreamFlight then contacts SimBrief and retrieves the latest available flight information associated with that Pilot ID.

An internet connection is required when fetching SimBrief data.

3.3 Finding Your SimBrief Pilot ID

StreamFlight uses your numerical SimBrief Pilot ID to retrieve your flight.

This is not necessarily the same as your SimBrief username.

Enter the numerical Pilot ID into the Pilot ID field on the Flight Plan tab.

Once entered and successfully used, StreamFlight remembers the Pilot ID so that it does not normally need to be entered again for every flight.

3.4 Fetching a SimBrief Flight Plan

Before fetching a flight, make sure:

• A valid Output Folder has been selected.
• Your SimBrief Pilot ID has been entered.
• The required flight has been generated in SimBrief.
• The computer has an active internet connection.

Select:

Fetch SimBrief

StreamFlight retrieves the available flight information and populates the appropriate Flight Plan fields.

The fetched information can include:

• Callsign
• Aircraft ICAO type
• Departure airport
• Destination airport
• Cruise Flight Level
• Planned route
• Departure runway
• Destination runway
• Departure METAR
• Destination METAR
• Planned route distance
• Planned passenger count

StreamFlight also performs local airport lookups for the departure and destination after the flight has been fetched.

If the SimBrief request cannot be completed, StreamFlight displays an error rather than silently replacing the existing flight information.

3.5 Aircraft Type

The Aircraft Type field identifies the aircraft being used for the flight.

When SimBrief is used, StreamFlight obtains the ICAO aircraft type from the SimBrief flight plan.

Examples include:

• B738
• B77L
• A320
• C172

The Aircraft Type field can also be entered or changed manually.

StreamFlight converts manually entered aircraft information to uppercase.

The aircraft type is used by StreamFlight displays and integrations and is also written to the Output Folder for use by compatible external applications.

3.6 Callsign

The Callsign field identifies the flight.

When a SimBrief flight is fetched, StreamFlight builds the callsign from the airline ICAO code and flight number supplied by SimBrief.

For example:

• BAW123

or:

• KLM456

For general aviation or manually configured flights, the callsign can be entered manually.

StreamFlight converts manually entered callsigns to uppercase.

The callsign is used by several StreamFlight displays and integrations, including the Passenger Manifest when SimBrief passenger information is available.

3.7 Departure Airport

Enter the four-character airport ICAO code into the Departure ICAO field.

For example:

• EGLL
• KJFK
• WSSS

When a SimBrief flight is fetched, the departure ICAO is populated automatically.

When an ICAO is entered manually, StreamFlight looks up the airport using its included airport database.

If the airport is found, StreamFlight obtains supporting information including:

• Airport latitude
• Airport longitude
• Airport elevation
• Associated city/municipality

If the entered four-character ICAO cannot be found, StreamFlight reports:

Airport ICAO 'XXXX' not found.

3.8 Destination Airport

The Destination ICAO field identifies the planned destination.

As with the departure airport, enter the four-character airport ICAO code.

When SimBrief is used, the destination is populated automatically.

When the destination ICAO is entered or changed, StreamFlight uses its included airport database to obtain:

• Destination latitude
• Destination longitude
• Destination elevation
• Associated city/municipality

The destination coordinates and elevation are displayed on the Flight Plan tab.

This information is important to several StreamFlight functions because it allows StreamFlight to understand where the destination is located independently of SimBrief.

If the airport cannot be found in the included airport database, StreamFlight reports that the ICAO was not found and the associated destination information will not be available.

3.9 Cruise Flight Level

The Cruise FL field identifies the planned cruise altitude.

When a SimBrief flight is fetched, StreamFlight obtains the cruise information from the available SimBrief flight-plan data and converts it into Flight Level format.

For example:

• FL380

The Cruise FL can also be entered manually.

StreamFlight accepts and normalises Flight Level information so that it can be used consistently by the application.

Cruise altitude information is used by flight-phase and telemetry-related functionality later in the flight.

3.10 Destination Coordinates and Airport Elevation

When StreamFlight recognises the Destination ICAO, it automatically fills the destination information displayed on the Flight Plan tab.

This includes:

• Destination Lon
• Destination Lat
• Destination Elevation

These values are obtained from StreamFlight's included airport database.

The coordinates allow StreamFlight to determine the geographic location of the destination, while airport elevation is useful to functions that need to understand the aircraft's height relative to the destination airport.

When using SimBrief, the destination ICAO is still enriched using StreamFlight's local airport information after the SimBrief flight has been fetched.

Normally, you do not need to enter destination coordinates manually when StreamFlight recognises the airport ICAO.

3.11 Flight Route

When a SimBrief flight is fetched, StreamFlight retrieves the planned route where that information is available.

The route is made available through the StreamFlight Output Folder in:

• flightplan.txt

StreamFlight adds the departure and destination to the retrieved route. Where SimBrief supplies planned runway information, the runway is included with the corresponding airport.

A route may therefore be represented in a form similar to:

• EGLL/27R ...route... EHAM/18R

The exact contents depend on the SimBrief flight plan.

If SimBrief does not provide a usable route, StreamFlight records the route as unavailable.

Manual departure and destination entry alone does not create a full en-route flight plan.

The complete Output Folder file reference is provided in Chapter 13 — Output Files & External Integration.

3.12 Departure and Destination Weather

When available in the SimBrief Operational Flight Plan, StreamFlight retrieves the METAR for both the departure and destination airports.

These are made available through:

• departure_metar.txt

and:

• destination_metar.txt

If SimBrief does not provide a METAR for one of the airports, StreamFlight records that information as unavailable.

The METAR output can be useful for custom OBS / Streamlabs Desktop layouts, Streamer.bot or other compatible automation software, and other external integrations.

3.13 Passenger Information

When SimBrief provides a planned passenger count, StreamFlight retrieves that number as part of the flight information.

This information is used by the Passenger Manifest feature.

For example, if the SimBrief flight contains a planned passenger count of:

• 162

StreamFlight can initialise the Passenger Manifest for that flight with a capacity of 162 passengers.

The Passenger Manifest can then use that capacity when viewers check in and receive seats.

The planned capacity and actual checked-in passenger count are therefore separate values.

When StreamFlight identifies a new passenger flight from the fetched SimBrief information, it can initialise the manifest and prepare the Passenger Check-In service for that flight.

Passenger Manifest operation, seat allocation and chatbot integration are covered fully in Chapter 11 — Passenger Manifest & Viewer Check-In.

3.14 Entering Flight Details Manually

SimBrief is not required to use StreamFlight.

For flights where you do not have a SimBrief plan, enter the required information directly into the Flight Plan tab.

At minimum, the most useful manual information consists of:

• Aircraft Type
• Callsign
• Departure ICAO
• Destination ICAO
• Cruise FL

When a valid four-character Departure or Destination ICAO is entered, StreamFlight automatically looks up the airport in its included airport database.

This allows StreamFlight to obtain airport information such as coordinates, elevation and city/municipality even when SimBrief is not being used.

Manual flight information is remembered by StreamFlight.

Information Not Supplied by Manual Airport Entry

Entering the departure and destination manually does not create a SimBrief Operational Flight Plan.

Consequently, information that originates specifically from SimBrief may not be available, including:

• Full planned route
• Planned departure runway
• Planned arrival runway
• SimBrief METAR information
• SimBrief planned route distance
• SimBrief planned passenger count

This does not prevent StreamFlight from operating. Features that can work from simulator telemetry and the available airport information continue to function according to their simulator support and data requirements.

3.15 Swapping Departure and Destination Airports

StreamFlight includes:

Manual Swap: DEPARTURE/ARRIVAL

This is particularly useful for:

• Return flights
• Rotation flights
• Out-and-back operations

For example, if the current flight is:

• EGLL → EHAM

selecting the swap function changes it to:

• EHAM → EGLL

After the swap, StreamFlight performs fresh airport lookups for the new departure and destination so that the associated airport information is updated.

The flight progress and flight-phase tracking are also reset for the new direction of travel.

The button swaps the airport information already present in StreamFlight. It does not change or regenerate your flight on SimBrief.

If the return sector has its own SimBrief OFP and you want StreamFlight to use that route, weather, passenger count and other SimBrief information, generate the appropriate flight in SimBrief and select Fetch SimBrief instead.

3.16 Changing Flight Information After a Flight Has Been Loaded

The primary Flight Plan fields remain editable after a flight has been loaded.

This allows you to correct or change information when necessary.

For example, you may need to:

• Correct an aircraft type
• Change a callsign
• Replace a departure or destination
• Adjust the Cruise FL

When a valid Departure or Destination ICAO is changed, StreamFlight performs a new airport lookup for the changed airport.

If the underlying flight plan itself has changed significantly, the recommended approach is to update or regenerate the flight in SimBrief and then select Fetch SimBrief again.

This keeps the StreamFlight flight information aligned with the flight plan you intend to operate.

3.17 Starting a New Flight

For a completely new flight, prepare the new flight information before departure.

If using SimBrief:

1. Generate the new flight in SimBrief.
2. Confirm that the correct flight is available.
3. Open the StreamFlight Flight Plan tab.
4. Select Fetch SimBrief.

StreamFlight then retrieves the new flight information.

If you are not using SimBrief, replace the existing Flight Plan information manually with the details for the new flight.

For a simple return or rotation using the existing airport pair, the Manual Swap: DEPARTURE/ARRIVAL function can be used where appropriate.

When a new SimBrief flight includes passenger information, StreamFlight also determines whether a new Passenger Manifest should be initialised for that flight.

This is particularly important when operating several sectors during the same StreamFlight session.

3.18 SimBrief and Flight Information Troubleshooting

StreamFlight Says "Enter Pilot ID"

The Pilot ID field is empty or does not contain a valid numerical SimBrief Pilot ID.

Enter your numerical Pilot ID and select Fetch SimBrief again.

StreamFlight Says an Output Folder is Required

A valid Output Folder must be configured before StreamFlight can complete the SimBrief fetch and save the resulting information.

Configure the Output Folder under User Settings and try again.

The Wrong Flight is Retrieved

StreamFlight retrieves the flight currently available for the supplied SimBrief Pilot ID.

Check that:

• The Pilot ID is correct.
• The required flight has been generated in SimBrief.
• You are not still retrieving an older SimBrief flight.

Generate/update the required flight in SimBrief and fetch it again.

An Airport ICAO is Not Found

StreamFlight uses its included airport database for local airport information.

Check that:

• The ICAO has been entered correctly.
• The code contains the expected four characters.
• The airport exists in the StreamFlight airport database.

If StreamFlight cannot identify the airport, it reports that the ICAO was not found.

Route or METAR Shows as Unavailable

The route and METAR information used here originates from the SimBrief flight data.

If the corresponding information is not present in the SimBrief response, StreamFlight records it as unavailable.

Passenger Manifest Does Not Initialise

Passenger Manifest capacity depends on a valid passenger count being supplied by SimBrief.

Passenger Manifest-specific troubleshooting is covered in Chapter 11.

SimBrief Fetch Fails

Check:

• Internet connectivity
• Pilot ID
• That SimBrief is reachable
• That the required flight has been generated

StreamFlight displays the SimBrief error if the request cannot be completed.

Further troubleshooting is provided in Chapter 15 — Troubleshooting.

3.19 Integrated Flight Planner (New in StreamFlight 3.1.0)

The Flight Planner is a built-in route discovery tool. Use it to explore airline flights and choose a departure, destination and callsign before continuing to SimBrief. It is available from the Flight Planner tab in StreamFlight.

Searching for Flights

1. Open the Flight Planner tab.
2. Optionally enter a Departure ICAO and/or Arrival ICAO airport code.
3. Choose an Airline ICAO and, if required, an Aircraft Type.
4. Optionally set Min. Duration (H), Max. Duration (H), Min. Dist. (NM) or Max. Dist. (NM) to narrow the search.
5. Click SEARCH ROUTES to display matching flights.

You do not have to fill in every filter. Leave fields blank when you want a wider selection of routes.

Understanding the Results

The results table shows Departure, Arrival, Airline, Aircraft, Callsign, Duration and Distance. Duration is shown as hours and minutes; distance is in nautical miles (NM).

Use the << and >> buttons to move between result pages. The counter beneath the search button shows which results are currently displayed and the total number of matches.

Some results display Select Aircraft where an aircraft type is not specified in the database. Choose an appropriate aircraft when planning your flight.

Choosing a Flight and Continuing to SimBrief

Double-click a flight in the results table to select it and continue to the Flight Setup / SimBrief workflow. Review the selected flight information before proceeding with your flight plan.

Route Database Accuracy

The Flight Planner uses an extensive airline route database that is continually under review. Routes may occasionally be outdated or inaccurate. Corrections to the online database can appear in new searches without requiring an application update.

If you find an incorrect airline, departure airport or arrival airport, please report it in the Found a Bug forum on the GadgetFPV Discord server, including the callsign and airport codes where possible.

Connection and Search Limits

The Flight Planner requires an internet connection and a valid StreamFlight 3 activation to access the route database. If a request limit message appears after repeated searches, wait a few minutes before trying again.

4. Flight Telemetry & Flight Progress

Once connected to a supported simulator, StreamFlight continuously receives live information about the aircraft and uses that data to monitor the flight.

This includes basic telemetry such as altitude, speed and heading, as well as calculated or interpreted information such as:

• Distance to Go (DTG)
• Estimated Time En Route (ETE)
• Estimated Time of Arrival (ETA)
• Flight progress
• Current flight phase

The exact data available to StreamFlight depends on the simulator and the interface used to communicate with it.

4.1 How StreamFlight Receives Simulator Data

StreamFlight automatically communicates with the supported simulator that is currently available.

The simulator interfaces used by StreamFlight are:

• Microsoft Flight Simulator 2020 / 2024 — SimConnect
• X-Plane 11 / 12 — XPUIPC
• Prepar3D — FSUIPC6

Once a simulator connection has been established, StreamFlight begins receiving live aircraft data.

The data received from the simulator is then used throughout StreamFlight for functions including:

• Gamer Mode
• Browser-source overlays
• Flight progress
• Flight-phase detection
• ETA and ETE calculations
• Control Input Display where supported
• Landing Rate
• RAAS where supported
• Camera functions where supported
• Output Folder telemetry files

You do not need to manually start telemetry collection. It begins automatically when StreamFlight establishes a valid simulator connection.

4.2 Altitude

StreamFlight receives the aircraft's altitude from the simulator and makes it available to supported displays and integrations.

Altitude is used for more than simply displaying the aircraft's current height.

StreamFlight also uses altitude-related information when determining the current stage of the flight and when supporting features that depend on the aircraft's vertical position.

The current altitude is also written to:

• altitude.txt

in the selected Output Folder.

4.3 Airspeed

StreamFlight receives live aircraft speed information from the simulator.

The current speed can be displayed through StreamFlight overlays and is written to:

• speed.txt

Speed is also used internally by StreamFlight when determining aircraft movement and calculating time-related flight information.

For example, StreamFlight does not attempt to produce meaningful en-route time calculations from an aircraft that is effectively stationary.

Speed is therefore both a displayed telemetry value and an important part of StreamFlight's flight-monitoring logic.

4.4 Heading

StreamFlight can obtain heading information from the simulator and maintains heading information for external use.

Depending on the simulator interface, StreamFlight can work with heading information such as:

• Magnetic heading

The corresponding Output Folder files are:

• heading_magnetic.txt

The heading presented by a particular StreamFlight display may depend on the simulator data available and the purpose of that display.

4.5 Vertical Speed

StreamFlight monitors the aircraft's vertical speed.

Vertical speed indicates how rapidly the aircraft is climbing or descending and is expressed in feet per minute.

Examples include:

• +1500 fpm

for a climb, or:

• -800 fpm

for a descent.

Vertical speed is made available through:

• vspeed.txt

Vertical movement also helps StreamFlight understand the aircraft's current flight state.

4.6 Outside Air Temperature

StreamFlight receives Outside Air Temperature (OAT) where the simulator interface provides it.

This value can be displayed through supported overlays and is written to:

• temperature_oat.txt

OAT represents the outside atmospheric temperature reported by the simulator at the aircraft's current position and altitude.

4.7 Wind

StreamFlight receives wind information from the simulator where supported.

The resulting wind display combines the relevant wind information into a form suitable for StreamFlight overlays and external integrations.

The value is written to:

• wind.txt

The wind shown by StreamFlight represents simulator-provided atmospheric information and may therefore differ from a METAR obtained earlier through SimBrief.

4.8 Aircraft Position

StreamFlight monitors the aircraft's current geographic position.

The current coordinates are made available through:

• latitude.txt

and:

• longitude.txt

Destination coordinates are also maintained separately through:

• destination_lat.txt

and:

• destination_lon.txt

The aircraft's position allows StreamFlight to understand where the aircraft is in relation to the planned destination and supports several flight-progress calculations.

Normally, the user does not need to interact with the raw latitude and longitude values.

They are primarily useful to StreamFlight itself and to users creating external integrations.

4.9 Distance to Go (DTG)

Distance to Go, or DTG, represents the remaining distance to the destination used by StreamFlight.

The current value is made available through:

• dtg_destination.txt

and can also be displayed in StreamFlight overlays.

DTG is important because it forms the basis of several other StreamFlight calculations, including ETE, ETA and flight progress.

StreamFlight uses the simulator data available for the active simulator rather than simply treating the straight-line distance between the departure and destination airports as the entire flight.

This is particularly important because an actual flight route can be considerably longer than the direct geographic distance between two airports.

As the aircraft progresses towards the destination, DTG should generally reduce.

However, it does not have to decrease every second. Changes in routing, turns, approaches and simulator navigation behaviour can affect the remaining distance.

4.10 Estimated Time En Route (ETE)

Estimated Time En Route (ETE) represents StreamFlight's estimate of the remaining flying time to the destination.

The current ETE is written to:

• ete.txt

and can be displayed through StreamFlight overlays.

StreamFlight calculates ETE from the current remaining distance and aircraft movement rather than simply displaying the original planned SimBrief flight time.

This means the value can change during the flight.

For example:

• A higher groundspeed can reduce the estimated remaining time.
• A lower groundspeed can increase it.
• A change in remaining distance can alter the estimate.

StreamFlight does not display a normal en-route ETE while the aircraft is still in PREFLIGHT.

Once the flight is underway and sufficient information is available, ETE is calculated from the live flight situation.

When the flight reaches its destination, ETE is reduced to zero.

4.11 Estimated Time of Arrival (ETA)

Estimated Time of Arrival (ETA) is calculated from the current ETE.

The ETA is made available through:

• eta.txt

and supported StreamFlight displays.

Because ETE changes as the flight progresses, ETA can also move earlier or later.

For example, changes to:

• Aircraft speed
• Routing
• Remaining distance
• Flight conditions

can alter the estimated arrival time.

StreamFlight does not provide a normal arrival estimate during PREFLIGHT.

Once the aircraft is underway and an ETE can be calculated, StreamFlight can determine the corresponding ETA.

At the end of the flight, the remaining time is reduced to zero.

4.12 Flight Progress Bar

StreamFlight can represent the overall progress of the flight using a visual progress bar.

The progress bar is available through supported Gamer Mode and browser-source displays.

The progress bar represents movement from the beginning of the flight towards the destination.

For a normal flight, StreamFlight establishes an appropriate starting distance and then compares the remaining distance against that starting point as the flight progresses.

The result is converted into a percentage representing the approximate progress of the flight.

For example:

• Beginning of flight — approximately 0%
• Mid-flight — approximately 50%
• Approaching destination — approaching 100%
• Arrival — 100%

Planned Route Versus Direct Airport Distance

Where appropriate flight-plan information is available, StreamFlight can use the planned flight distance to establish a more realistic progress baseline.

This is important because the direct geographic distance between the departure and destination airports may be substantially shorter than the actual route being flown.

StreamFlight therefore does not rely solely on the simple airport-to-airport distance when better route information is available.

Browser-Source Progress Bar

For users incorporating the StreamFlight progress bar into OBS / Streamlabs Desktop or another compatible browser-source application, StreamFlight provides:

• progressbar.html

This is the browser-source file used to display the progress bar.

Detailed browser-source configuration is covered in Chapter 5 — Overlays & Gamer Mode.

Restarting StreamFlight

StreamFlight includes logic intended to preserve or reconstruct sensible flight progress if the application is started again during an existing flight.

This is discussed further in Section 4.18 — Starting StreamFlight During an Existing Flight.

4.13 Automatic Flight Phase Detection

StreamFlight automatically determines the current stage of the flight using live simulator information.

You do not normally need to tell StreamFlight when you have started taxiing, taken off, begun descending or landed.

StreamFlight continuously evaluates the aircraft state and moves through the appropriate flight phases as the flight develops.

Automatic flight-phase detection supports:

• Overlay information
• Flight progress behaviour
• ETE and ETA behaviour
• External integrations
• Flight status information

The current flight phase is also written to:

• flight_phase.txt

4.14 StreamFlight Flight Phases

StreamFlight uses the following flight phases:

PREFLIGHT

The aircraft is at the beginning of the flight before taxi-out has commenced.

This is the normal starting phase.

ETE and ETA are not presented as normal en-route values during PREFLIGHT.

TAXI OUT

The aircraft has begun ground movement in preparation for departure.

This marks the transition from preflight preparation into the active flight sequence.

TAKEOFF

The aircraft is in the departure/takeoff stage.

StreamFlight uses this part of the flight to establish important progress information for the sector.

CLIMB

The aircraft is airborne and climbing towards its cruise level.

CRUISE

The aircraft has reached the cruise portion of the flight.

DESCENT

The aircraft has left the cruise portion and is descending towards the destination.

APPROACH

The aircraft is in the later descent/approach portion of the flight.

LANDING

The aircraft has reached the landing stage at the destination.

StreamFlight applies safeguards to prevent normal low-altitude flight from being interpreted as a landing without the preceding airborne/approach sequence.

TAXI IN

The aircraft has landed and is taxiing after arrival.

A normal flight therefore progresses approximately as follows:

PREFLIGHT → TAXI OUT → TAKEOFF → CLIMB → CRUISE → DESCENT → APPROACH → LANDING → TAXI IN

The exact timing of each transition depends on the aircraft's simulator state.

4.15 Manual Flight Phase Override

Although StreamFlight normally controls the flight phase automatically, a Manual Phase Override is available.

This is useful if:

• The automatically detected phase does not represent the current situation.
• You started StreamFlight in an unusual aircraft state.
• You are performing a non-standard flight.
• You need to force a particular phase for testing or streaming purposes.

When a phase is manually selected, StreamFlight uses the selected phase instead of allowing the automatic detector to immediately replace it.

The selected manual phase is visually highlighted so that you can see that a manual phase is active.

4.16 Returning to Automatic Flight Phase Detection

After using Manual Phase Override, StreamFlight can be returned to automatic flight-phase detection.

Once automatic operation is restored, StreamFlight again evaluates the current simulator state and determines the appropriate phase.

StreamFlight may require a short period of live simulator data before the automatically reconstructed phase is displayed.

This is intentional: StreamFlight evaluates the current aircraft state rather than assuming that the flight has restarted from PREFLIGHT.

4.17 Reset Progress Bar + Flight Phase

StreamFlight normally recognises the end of one flight and the beginning of another through the normal flight-phase sequence.

For a conventional flight, the aircraft lands, taxis to its parking position and eventually returns to PREFLIGHT when the flight has ended.

However, not every type of flying follows this sequence.

Examples include:

• Touch-and-go circuits
• Repeated circuit training
• Landing, taxiing clear and departing again without shutting down the engines
• Rapid turnaround operations where the aircraft remains running between sectors

In these situations, StreamFlight may never naturally return to PREFLIGHT because the aircraft has not reached the normal end-of-flight condition.

StreamFlight therefore provides:

Reset Progress Bar + Flight Phase

Use this control when you want StreamFlight to treat the next departure as the beginning of a new flight cycle without shutting down the aircraft.

The reset clears the previous flight's progress and flight-phase tracking so that StreamFlight can establish the next departure correctly.

Example — Touch-and-Go Operations

Consider an aircraft performing circuit training:

TAKEOFF → CLIMB → APPROACH → LANDING → TAKEOFF

The aircraft touches down and immediately departs again.

Because the engines remain running and the aircraft never returns to the normal PREFLIGHT condition, StreamFlight may still retain state associated with the previous circuit.

Using Reset Progress Bar + Flight Phase allows the next circuit to begin with fresh progress and phase tracking.

Example — Landing and Departing Again

You may instead:

1. Land at an airport.
2. Taxi clear of the runway.
3. Remain with the engines running.
4. Prepare for another departure.
5. Depart again.

If the aircraft never reaches the normal PREFLIGHT condition, use Reset Progress Bar + Flight Phase before beginning the next flight cycle.

The reset control is therefore particularly useful for pilots performing touch-and-goes, circuits, training flights and consecutive departures without an engine shutdown.

4.18 Starting StreamFlight During an Existing Flight

StreamFlight does not have to be running before the aircraft leaves the departure airport.

If StreamFlight is started or restarted while a flight is already in progress, it attempts to reconstruct the current situation from the available simulator and flight information.

After connection, StreamFlight evaluates the live aircraft state and can recover an appropriate phase such as:

• CLIMB
• CRUISE
• DESCENT
• APPROACH

rather than assuming that the aircraft must be in PREFLIGHT.

This reconstruction is not necessarily instantaneous. StreamFlight may need several seconds of live data before the appropriate phase, ETE, ETA and progress information stabilise.

Recovering Flight Progress

Where existing progress information is available and remains plausible for the current flight, StreamFlight can use it when restoring progress.

If the original takeoff baseline is not available, StreamFlight can use available flight-plan and destination information to establish a reasonable fallback.

This allows StreamFlight to provide useful progress information even when it was not running at the exact moment of departure.

Do Not Reset Simply Because StreamFlight Was Restarted

If you restart StreamFlight during a flight, first allow it to reconnect and reconstruct the current state.

Use Reset Progress Bar + Flight Phase only when you genuinely intend to begin a new flight cycle.

4.19 Simulator-Specific Telemetry Differences

Although StreamFlight presents a common user experience across its supported simulators, the underlying telemetry interfaces are different.

Microsoft Flight Simulator 2020 / 2024

StreamFlight communicates with MSFS through SimConnect.

MSFS provides the broadest integration with StreamFlight and supports features that depend specifically on SimConnect in addition to the standard flight telemetry.

These include features such as:

• Control Input Display
• Camera Control
• RAAS

where documented as supported.

X-Plane 11 / 12

StreamFlight communicates with X-Plane through XPUIPC.

Standard flight telemetry is available to StreamFlight through the configured XPUIPC interface.

StreamFlight maintains X-Plane-specific flight-progress handling so that progress can be tracked appropriately using the data available from X-Plane.

Some MSFS-specific features are not currently available with X-Plane.

For example, the Control Input Display is currently identified in StreamFlight as:

MSFS 20/24 — X-Plane & P3D coming soon

Prepar3D

StreamFlight communicates with Prepar3D through FSUIPC6.

Supported flight telemetry is obtained through the FSUIPC interface.

As with X-Plane, features that specifically require the MSFS SimConnect implementation are not automatically available simply because standard telemetry is available.

Why Values Can Differ Between Simulators

The three simulator families do not necessarily expose every value in exactly the same form.

As a result:

• Some telemetry may be obtained from different simulator variables.
• Progress tracking may use simulator-specific handling.
• Some StreamFlight features are simulator-specific.
• Small differences in displayed behaviour between simulators can be normal.

The complete feature compatibility overview is provided in Appendix 15.2 — Simulator Feature Compatibility Matrix.

4.20 Understanding Telemetry During a Flight

During normal operation, StreamFlight telemetry should continuously respond to the aircraft's simulator state.

For example:

• Altitude changes as the aircraft climbs or descends.
• Speed changes as the aircraft accelerates or decelerates.
• Heading follows changes in aircraft direction.
• Vertical speed reflects climbs and descents.
• DTG generally reduces as the destination is approached.
• ETE responds to remaining distance and aircraft speed.
• ETA changes as ETE changes.
• Flight progress advances towards the destination.
• Flight phase changes as the aircraft moves through the flight.

If several unrelated telemetry values stop changing at the same time, this can indicate that StreamFlight is no longer receiving current simulator data rather than a problem with an individual display.

Check the simulator connection status before troubleshooting individual telemetry values.

Detailed connection and telemetry troubleshooting is provided in Chapter 15 — Troubleshooting.

5. Overlays & Gamer Mode

StreamFlight provides several ways to display live flight information while you fly or stream.

For users who simply want flight information visible while flying, Gamer Mode provides an on-screen telemetry display without requiring streaming software.

For streamers, StreamFlight provides browser-source displays that can be incorporated into OBS / Streamlabs Desktop and other compatible applications.

StreamFlight can also act as the data source for completely custom overlays. Individual flight and telemetry values can be used in OBS through Text (GDI+) sources, allowing users to create layouts that match their own channel branding or stream design.

This chapter explains Gamer Mode, the supplied templates, browser sources, Dual-PC operation and the creation of custom overlays.

The dedicated Control Input Display and Landing Rate displays are covered separately in later chapters.

5.1 Understanding StreamFlight Overlays

StreamFlight provides several ways of presenting flight information.

Gamer Mode

Gamer Mode displays StreamFlight information directly on the simulator computer.

It is designed for users who want live flight information visible while flying, regardless of whether they are streaming.

No OBS / Streamlabs Desktop installation is required to use Gamer Mode.

Browser Sources

Browser sources allow StreamFlight displays to be incorporated into streaming and production software.

These are particularly useful with:

• OBS
• Streamlabs Desktop
• Other software capable of displaying a compatible browser source

StreamFlight provides the browser-source service; the external application determines where and how that source appears within the stream or production layout.

Custom Overlays

Users are not restricted to StreamFlight's supplied visual layouts.

Individual StreamFlight values are continuously written to the selected Output Folder and can be read by applications such as OBS.

This makes it possible to create a completely custom flight-information display using individual telemetry values, browser-source elements and your own graphics.

5.2 Gamer Mode

Gamer Mode provides an on-screen StreamFlight display directly over your normal desktop/simulator environment.

It allows important flight information to remain visible without requiring a separate streaming application.

Depending on the selected template and available flight information, Gamer Mode can display information such as:

• Aircraft
• Callsign
• Departure
• Destination
• Flight phase
• Altitude
• Speed
• Heading
• Vertical speed
• Wind
• Outside Air Temperature
• DTG
• ETE
• ETA
• Flight progress

The exact information and layout depend on the selected Gamer Mode template.

Gamer Mode is therefore useful both for:

• Streamers who want to see StreamFlight information themselves while flying
• Non-streamers who want an on-screen flight companion

5.3 Enabling Gamer Mode

Gamer Mode is controlled from the Overlays tab.

Locate the Gamer Mode controls and enable the feature.

When Gamer Mode is enabled, StreamFlight displays the selected overlay on the simulator computer.

The overlay updates automatically as new simulator and flight information becomes available.

When Gamer Mode is disabled, the on-screen Gamer Mode display is removed.

5.4 Gamer Mode Templates

StreamFlight provides several Gamer Mode templates so that users can choose the amount and style of information they want displayed.

The available templates are:

• Classic
• Informative
• Basic
• Minimal
• TikTok

Each template presents StreamFlight information differently.

Classic

A general-purpose StreamFlight layout providing a balanced selection of flight information.

Informative

Designed to provide a more information-rich display for users who want additional flight data visible.

Basic

A simpler layout for users who want the primary flight information without a heavily populated display.

Minimal

A reduced display intended for users who want StreamFlight information to occupy less screen space.

TikTok

A layout designed for use where a different screen composition or vertical-content style is required.

Select the template that best suits your display and the amount of information you want visible.

5.5 Overlay Position

Gamer Mode provides a position selector that determines where the overlay is placed on the monitor.

The available selections are:

• DEFAULT
• LEFT
• CENTRE
• RIGHT

DEFAULT

Uses the standard positioning defined by the selected Gamer Mode template.

This is the recommended starting option when first selecting a template.

LEFT

Positions the Gamer Mode display towards the left side of the monitor.

CENTRE

Positions the Gamer Mode display towards the centre of the monitor.

RIGHT

Positions the Gamer Mode display towards the right side of the monitor.

These options allow the overlay to be moved away from important simulator instruments, menus or other information.

For example, LEFT or RIGHT may be useful when part of the simulator display is already occupied by another window or instrument.

StreamFlight remembers the selected Gamer Mode position.

5.6 Auto-Hide

Gamer Mode includes an Auto-Hide option.

When enabled, StreamFlight can automatically hide the Gamer Mode display when appropriate rather than leaving it permanently visible.

This is useful when you want flight information available during normal operation but do not want the overlay permanently occupying screen space.

When Auto-Hide is disabled, Gamer Mode remains visible according to its normal enabled state.

5.7 Showing Flight Phase

StreamFlight can include the automatically detected flight phase in supported overlay displays.

Typical phases include:

• PREFLIGHT
• TAXI OUT
• TAKEOFF
• CLIMB
• CRUISE
• DESCENT
• APPROACH
• LANDING
• TAXI IN

The displayed phase follows StreamFlight's automatic flight-phase detection unless Manual Phase Override is being used.

Flight-phase detection is explained fully in Chapter 4 — Flight Telemetry & Flight Progress.

Where the display provides an option to show or hide the flight phase, you can choose whether this information appears.

This can be useful for users who prefer a cleaner display containing fewer elements.

5.8 Live Flight Telemetry Browser Source

StreamFlight provides a Live Flight Telemetry browser source for use with OBS / Streamlabs Desktop and other compatible browser-source applications.

The browser-source service is provided directly by StreamFlight while the application is running.

The primary Live Flight Telemetry service uses port:

• 38080

If the primary port is unavailable, StreamFlight can use the fallback port:

• 38081

The Live Flight Telemetry browser source uses the:

/browsersource

endpoint.

For normal same-PC operation, StreamFlight provides the appropriate browser-source address through the interface.

Rather than manually constructing the address, use the COPY function provided by StreamFlight whenever possible.

This avoids typing errors and ensures that the current browser-source address is used.

5.9 Adding StreamFlight to OBS / Streamlabs Desktop

The Live Flight Telemetry display can be added as a browser source.

The exact interface may differ slightly between applications, but the basic procedure is the same.

Step 1 — Start StreamFlight

Start StreamFlight and ensure that it is running normally.

Step 2 — Copy the Browser Source Address

Open the Overlays tab and locate the Live Flight Telemetry browser source.

Select:

COPY

StreamFlight copies the appropriate browser-source address.

Step 3 — Create a Browser Source

In OBS / Streamlabs Desktop:

1. Open the scene where you want StreamFlight to appear.
2. Add a new Browser Source.
3. Give the source a recognisable name, such as:

StreamFlight - Live Telemetry

1. Paste the address copied from StreamFlight into the browser-source URL field.
2. Confirm the browser source.

Step 4 — Position the Source

Once added, resize and position the StreamFlight browser source within the scene.

The placement of the browser source is controlled by OBS / Streamlabs Desktop, not by StreamFlight's Gamer Mode position setting.

Once configured, the browser source receives updated information from StreamFlight while StreamFlight is running.

5.10 Copying Browser Source Addresses

StreamFlight provides COPY controls for its supported browser sources.

These controls remove the need to manually construct or type browser-source addresses.

When StreamFlight and OBS / Streamlabs Desktop are running on the same computer, the local browser-source address is used.

For a Dual-PC configuration, StreamFlight can provide an address suitable for access from another computer on the local network.

If a previously configured browser source stops displaying following a port conflict, copy the current address from StreamFlight again and verify the URL configured in the browser source.

5.11 Dual-PC Setup / LAN Mode

StreamFlight supports configurations where the flight simulator and StreamFlight run on one computer while the streaming software runs on another.

A typical arrangement is:

Simulator PC

Runs:

• Flight simulator
• StreamFlight

Streaming PC

Runs:

• OBS / Streamlabs Desktop

The two computers communicate over the local network.

Enabling Dual-PC / LAN Mode

On the simulator computer:

1. Start StreamFlight.
2. Open the Overlays tab.
3. Enable Dual PC Setup / LAN Mode.
4. Use the appropriate COPY control to obtain the browser-source address.

The address supplied in LAN Mode allows the browser-source service to be reached from another computer on the local network.

On the streaming computer:

1. Open OBS / Streamlabs Desktop.
2. Add or open the required Browser Source.
3. Paste the address copied from StreamFlight.
4. Confirm the browser source.

The streaming computer then receives the browser-source display from StreamFlight running on the simulator computer.

Network Requirements

For Dual-PC operation:

• Both computers must be connected to the same local network.
• The simulator computer must be reachable from the streaming computer.
• StreamFlight must be running on the simulator computer.
• Windows Firewall or third-party security software must allow the required local network communication.
• The required StreamFlight browser-source port must not be blocked.

A wired Ethernet connection is generally preferable for a permanent Dual-PC streaming setup, although StreamFlight does not require a particular physical network technology.

Testing the Connection

If the browser source does not appear on the streaming computer, first confirm that the source works locally on the simulator computer.

If it works locally but not from the second computer, investigate:

• Network connectivity
• Firewall configuration
• LAN address
• Port accessibility

Detailed troubleshooting is provided in Chapter 15 — Troubleshooting.

5.12 Using StreamFlight with Other Browser-Source Software

StreamFlight is not tied exclusively to OBS.

The Live Flight Telemetry display is delivered using standard browser-source functionality.

Therefore, other applications capable of displaying a compatible browser source may also be able to use it.

This includes Streamlabs Desktop and other streaming or production software supporting browser/web sources.

The general procedure is:

1. Start StreamFlight.
2. Copy the appropriate browser-source address.
3. Create a browser/web source in the external application.
4. Paste the StreamFlight address.
5. Position and size the source as required.

5.13 Overlay Behaviour During a Flight

Once StreamFlight is connected to the simulator, overlay information updates as the flight progresses.

Depending on the selected template and enabled options, information can include:

• Altitude
• Speed
• Heading
• Vertical speed
• Wind
• Temperature
• DTG
• ETE
• ETA
• Flight phase
• Flight progress

Some information is not expected to be meaningful during every stage of the flight.

For example, StreamFlight does not provide normal en-route ETE and ETA information while the flight remains in PREFLIGHT.

As the aircraft begins its flight and StreamFlight obtains sufficient information, the relevant values become available.

Flight Information and Telemetry

Overlay information can originate from different sources.

For example:

Flight information

• Aircraft type
• Callsign
• Departure
• Destination

may originate from SimBrief or manually entered flight details.

Live telemetry

• Altitude
• Speed
• Heading
• Vertical speed
• Wind
• Temperature

originates from the connected simulator.

Calculated information

• DTG
• ETE
• ETA
• Flight progress
• Flight phase

is determined by StreamFlight using the available flight and simulator information.

Understanding these differences can help when troubleshooting an individual missing value.

5.14 Customising the Overlay Display

StreamFlight allows its visual displays to be adjusted without requiring users to modify the underlying application files.

For Gamer Mode, available options include controls such as:

• Template selection
• Display position
• Auto-Hide
• Flight-phase visibility

For browser sources, additional positioning and scaling can be performed within OBS / Streamlabs Desktop.

For example, you can:

• Move the source
• Resize it
• Crop it where appropriate
• Place it above or below other scene elements
• Show or hide it as part of the scene design

For users wanting considerably more control over the visual design, StreamFlight's individual output files can also be used to create a completely custom overlay.

5.15 Creating Your Own Custom Overlay

You are not limited to the visual overlays supplied with StreamFlight.

StreamFlight continuously makes flight information available through the selected Output Folder, allowing you to build your own overlay design in OBS / Streamlabs Desktop or other compatible software.

This is useful if you want your flight information to match:

• Your channel branding
• An existing stream layout
• A particular aircraft or airline theme
• A minimal telemetry display
• A vertical or social-media layout
• Your own preferred selection of flight information

There are two principal methods for incorporating StreamFlight information into a custom overlay:

1. Individual StreamFlight Output Folder files
2. StreamFlight browser-source elements

These methods can also be combined.

Using Text (GDI+) in OBS

StreamFlight writes many individual flight and telemetry values as text files in the selected Output Folder.

Examples include:

• callsign.txt
• aircrafttype.txt
• departureicao.txt
• destinationicao.txt
• altitude.txt
• speed.txt
• heading_true.txt
• vspeed.txt
• dtg_destination.txt
• ete.txt
• eta.txt
• flight_phase.txt

OBS can read these files directly using a Text (GDI+) source.

Adding a StreamFlight Text Value

To add a StreamFlight value to a custom OBS layout:

1. In OBS, add a new Text (GDI+) source.
2. Enable Read from file.
3. Browse to the StreamFlight Output Folder.
4. Select the required StreamFlight .txt file.
5. Configure the font and other visual settings.
6. Position the text source within the scene.

For example, selecting:

• callsign.txt

allows OBS to display the current callsign.

Selecting:

• altitude.txt

allows OBS to display the current altitude supplied by StreamFlight.

As StreamFlight updates the file, OBS updates the displayed text.

The process can be repeated for each value required in the custom layout.

Designing the Overlay

Because each value can be a separate source, the visual design is controlled by the user.

For example, you can independently configure:

• Font
• Font size
• Position
• Alignment
• Opacity
• Background graphics
• Frames
• Labels
• Logos
• Other scene elements

This allows StreamFlight to provide the data while OBS controls the final presentation.

Combining Text and Browser Sources

A custom overlay does not have to use only text files.

StreamFlight browser-source elements can be combined with Text (GDI+) sources.

For example, a custom overlay could use individual StreamFlight text files for:

• Callsign
• Departure
• Destination
• Altitude
• Speed
• DTG
• ETE
• ETA

while displaying the StreamFlight flight progress bar as a browser-source element.

Other StreamFlight browser-source features described elsewhere in this manual can similarly be incorporated where appropriate.

Example Custom Layout

A custom flight-information panel might display:

FLIGHT

• BAW123

ROUTE

• EGLL → EHAM

ALTITUDE

• 36,000 ft

SPEED

• 465 kts

DTG

• 186 nm

ETA

• 18:42

with the StreamFlight progress bar displayed underneath.

The labels and surrounding graphics can be created directly within the stream layout, while the changing values are supplied by StreamFlight.

Using Other Compatible Software

The same principle is not limited to OBS.

Other software capable of reading text files or consuming StreamFlight browser sources may also be used to create custom displays or integrations.

The exact configuration depends on the third-party application.

Do Not Modify StreamFlight to Create a Custom Overlay

Creating a custom overlay does not require modification of the StreamFlight application.

Using the documented Output Folder files is the recommended approach for custom text-based integrations.

This keeps the custom design separate from StreamFlight itself.

The complete list of user-facing files available in the Output Folder is provided in Chapter 13 — Output Files & External Integration.

5.16 Flight Progress Browser Source

In addition to the main Live Flight Telemetry display, StreamFlight provides the visual flight progress bar through:

• progressbar.html

This allows the progress display to be incorporated into an OBS / Streamlabs Desktop scene where appropriate.

The progress bar reflects the flight-progress calculation described in Chapter 4 — Flight Telemetry & Flight Progress.

When incorporated into a custom scene, it can be positioned alongside StreamFlight text values, graphics or other stream elements.

5.17 Browser Source Ports

StreamFlight v3.0.0 uses dedicated ports for its browser-source services.

The relevant ports are:

The corresponding browser-source endpoints include:

Live Flight Telemetry

• /browsersource

Control Input Display

• /controls

Landing Rate

• /landingrate

The Control Input Display and Landing Rate are covered fully in Chapter 6 and Chapter 9 respectively.

Normally, users do not need to remember or manually configure these port numbers because StreamFlight provides COPY controls for its browser-source addresses.

The port information is primarily useful for:

• Advanced configurations
• Dual-PC setups
• Troubleshooting
• Identifying port conflicts

If a primary port is unavailable, StreamFlight can use the corresponding fallback port.

5.18 Browser Source Troubleshooting

If a StreamFlight browser source does not appear, several basic checks can quickly identify the cause.

StreamFlight Is Not Running

The browser-source service is provided by StreamFlight.

If StreamFlight is closed, the live browser source is unavailable.

Incorrect Browser Source Address

Use the COPY control in StreamFlight and compare the copied address with the URL configured in OBS / Streamlabs Desktop.

If necessary, replace the existing address with the newly copied address.

Browser Source Is Hidden

Check that:

• The source is enabled in the current scene.
• The source has not been hidden.
• It is positioned within the visible canvas.
• Another scene element is not completely covering it.

Primary Port Is Unavailable

If StreamFlight cannot use the primary port for a browser-source service, it can use the corresponding fallback port.

Copy the current browser-source address from StreamFlight again.

Browser Source Works Locally but Not on the Streaming PC

For a Dual-PC configuration, check that:

• Dual PC Setup / LAN Mode is enabled.
• Both computers are on the same local network.
• The correct LAN address is being used.
• Windows Firewall is not blocking StreamFlight.
• Third-party security software is not blocking the connection.
• The required port is accessible between the two computers.

Browser Source Appears but Does Not Update

If the display itself appears but its values no longer change, check whether StreamFlight is still receiving simulator telemetry.

If several unrelated telemetry values stop changing simultaneously, investigate the simulator connection before assuming that the browser source itself has failed.

Refreshing the Browser Source

If OBS / Streamlabs Desktop has retained an old or inactive browser-source session, refreshing or reloading the source can re-establish the connection to StreamFlight.

If necessary:

1. Copy the browser-source address from StreamFlight again.
2. Open the source properties in OBS / Streamlabs Desktop.
3. Verify the configured address.
4. Refresh or reload the source.

Further browser-source, port and Dual-PC troubleshooting is provided in Chapter 15 — Troubleshooting.

6. Control Input Display

StreamFlight includes a Control Input Display that provides a visual representation of the pilot's control inputs.

The display can show:

• Pitch
• Roll
• Rudder
• Throttle

This is particularly useful for streaming, where viewers can see the control inputs being made by the pilot in real time.

The Control Input Display is provided as a dedicated browser source, allowing it to be positioned independently from the main StreamFlight Live Flight Telemetry overlay.

6.1 What is the Control Input Display?

The Control Input Display converts control information received from the simulator into a graphical display.

Instead of showing the control positions as numerical values, StreamFlight provides visual indicators that respond as the controls are moved.

The display contains three principal areas:

Pitch and Roll

A movable indicator represents pitch and roll input.

Moving the flight controls left or right moves the indicator according to roll input, while forward and backward control movement represents pitch input.

Rudder

A horizontal indicator represents rudder input.

Throttle

A vertical indicator represents throttle position.

The display updates continuously while StreamFlight is connected to a supported simulator and valid control information is available.

The Control Input Display operates independently from Gamer Mode. You do not need to enable Gamer Mode to use the Control Input browser source.

6.2 Enabling the Control Input Browser Source

The Control Input Display is configured from the Overlays tab.

The interface identifies this feature as:

Control Inputs — MSFS 20/24

with X-Plane and Prepar3D indicated as coming later.

StreamFlight provides a dedicated browser-source address for the Control Input Display.

The primary service uses port:

• 38082

If that port is unavailable, StreamFlight can use the fallback port:

• 38083

The Control Input Display uses the:

• /controls

endpoint.

As with the other StreamFlight browser sources, use the COPY control in StreamFlight rather than manually constructing the address.

6.3 Pitch and Roll Display

Pitch and roll are displayed together using a two-dimensional control indicator.

The centre of the display represents the neutral control position.

As roll input is applied, the indicator moves horizontally.

For example:

• Left control input moves the indicator towards the left.
• Right control input moves the indicator towards the right.

Pitch input moves the indicator vertically.

The combination of the two allows simultaneous pitch and roll input to be represented.

For example, pulling back while applying right roll produces a corresponding diagonal movement of the indicator.

When the controls return to their neutral position, the indicator should return towards the centre.

Small Differences Around the Centre

The exact neutral position reported by an aircraft can vary slightly.

Different aircraft, control hardware and aircraft systems can apply:

• Dead zones
• Calibration
• Control filtering
• Custom control logic

As a result, a very small difference around the visual centre does not necessarily indicate a StreamFlight problem.

6.4 Rudder Display

The Control Input Display includes a separate indicator for rudder input.

When left rudder is applied, the indicator moves towards the left.

When right rudder is applied, the indicator moves towards the right.

Returning the rudder controls to neutral returns the indicator towards the centre.

The displayed value represents the rudder information available to StreamFlight from the simulator.

Pedal calibration, hardware dead zones and aircraft-specific control behaviour can therefore influence the exact position displayed.

6.5 Throttle Display

The Control Input Display also includes a visual throttle indicator.

The throttle display responds as the aircraft's throttle controls are moved.

Increasing the throttle moves the indicator towards the higher-power end of its range.

Reducing the throttle moves it towards the lower-power end.

This provides viewers with an immediate visual indication of changes being made to the aircraft's throttle controls.

Aircraft-Specific Throttle Behaviour

Throttle systems vary considerably between aircraft.

Examples include:

• Conventional general-aviation throttles
• Airliner thrust levers
• Multiple-engine throttle systems
• Throttle detents
• Idle and reverse ranges
• Aircraft with custom throttle implementations

Because of these differences, the StreamFlight throttle indicator should be considered a visual representation of the control information available from the simulator rather than a replacement for the aircraft's own throttle or engine instrumentation.

Some aircraft may not use the entire visual range in exactly the same way as another aircraft.

6.6 Invert Pitch Indicator

StreamFlight provides an Invert Pitch Indicator option.

This changes the visual direction used for pitch movement in the Control Input Display.

This option is useful if the displayed pitch movement feels visually opposite to the control movement you expect.

For example, depending on your preferred representation, pulling back on the controls may be expected to move the indicator upwards or downwards.

The invert option allows you to reverse that visual behaviour without changing the simulator's actual control configuration.

6.7 Adding Control Inputs to OBS / Streamlabs Desktop

The Control Input Display is added to streaming software as a Browser Source.

Step 1 — Start StreamFlight

Start StreamFlight and allow it to connect to Microsoft Flight Simulator.

Step 2 — Copy the Control Input Address

Open the Overlays tab.

Locate the Control Input browser-source section and select:

COPY

StreamFlight copies the current Control Input browser-source address.

Step 3 — Add a Browser Source

In OBS / Streamlabs Desktop:

1. Open the scene where you want the Control Input Display.
2. Add a new Browser Source.
3. Give the source a recognisable name, such as:

StreamFlight - Control Inputs

1. Paste the address copied from StreamFlight.
2. Confirm the browser source.

Step 4 — Position the Display

Resize and position the Control Input Display within the scene.

Because the Control Input Display is separate from the main Live Flight Telemetry browser source, the two displays can be positioned independently.

For example, you could place:

• Live Flight Telemetry across the bottom of the scene
• Control Inputs in a lower corner

The final layout is controlled entirely within OBS / Streamlabs Desktop.

6.8 Dual-PC Use

The Control Input Display supports the same Dual-PC / LAN concept described for StreamFlight browser sources in Chapter 5.

A typical configuration is:

Simulator PC

Runs:

• Microsoft Flight Simulator
• StreamFlight

Streaming PC

Runs:

• OBS / Streamlabs Desktop

Enable Dual PC Setup / LAN Mode in StreamFlight and use the COPY control to obtain the appropriate browser-source address.

Add that address as a Browser Source on the streaming computer.

StreamFlight remains responsible for communicating with the simulator and producing the Control Input Display.

The streaming computer only needs to display the browser source.

The Control Input service normally uses:

• 38082

with:

• 38083

available as the fallback port.

Detailed Dual-PC configuration is covered in Chapter 5 — Overlays & Gamer Mode.

6.9 Aircraft-Specific Control Behaviour

Not every aircraft exposes its controls to the simulator in exactly the same way.

This is particularly noticeable with sophisticated third-party aircraft that may use custom systems to implement flight controls or throttle behaviour.

StreamFlight reads the control information available through Microsoft Flight Simulator and converts it into the visual Control Input Display.

Consequently, small differences between aircraft are possible.

Pitch and Roll

Most aircraft should provide recognisable pitch and roll movement.

However, the precise neutral position or range can differ slightly depending on the aircraft's control implementation.

Rudder

Rudder behaviour can be influenced by:

• Hardware calibration
• Simulator assistance
• Dead zones
• Aircraft-specific control logic

Throttle

Throttle behaviour is the area most likely to differ between aircraft.

An aircraft may implement:

• Idle detents
• Reverse zones
• Thrust detents
• Multiple thrust levers
• Custom throttle mapping

The visual position shown by StreamFlight therefore may not correspond exactly to a particular percentage shown by the aircraft's own systems.

Testing a New Aircraft

When using the Control Input Display with an aircraft for the first time, it is useful to move the controls through their normal operating ranges while observing the display.

Check:

• Full left and right roll
• Forward and backward pitch
• Left and right rudder
• Idle to normal maximum throttle range
• Neutral control position

This provides a quick indication of how that particular aircraft reports its controls.

6.10 Simulator Support

The Control Input Display currently has the following simulator support in StreamFlight v3.0.0:

The StreamFlight interface identifies X-Plane and Prepar3D Control Input support as:

Coming Soon

The limitation applies specifically to the Control Input Display and does not mean that StreamFlight cannot obtain normal flight telemetry from those simulators.

X-Plane and Prepar3D continue to provide the supported standard telemetry described elsewhere in this manual.

6.11 Control Input Display Troubleshooting

If the Control Input Display does not behave as expected, first determine whether the problem affects the browser source itself or the control data being displayed.

Browser Source Does Not Appear

Check that:

• StreamFlight is running.
• The current Control Input address was copied from StreamFlight.
• The Browser Source is visible in the OBS / Streamlabs Desktop scene.
• The source has not been positioned outside the visible canvas.
• The required port is available.

If the primary port 38082 cannot be used, StreamFlight can use fallback port 38083.

Copy the address from StreamFlight again rather than manually changing the port.

Display Appears but Controls Do Not Move

Confirm that:

• Microsoft Flight Simulator 2020 or 2024 is running.
• StreamFlight has detected and connected to MSFS.
• The aircraft controls are responding normally inside the simulator.

If the browser-source graphic is visible but none of the control indicators move, investigate the simulator connection or control-data availability.

Pitch Moves in the Opposite Visual Direction

Use:

Invert Pitch Indicator

to reverse the visual pitch movement.

This does not alter the simulator controls.

Indicator Does Not Centre Exactly

A small offset can be caused by:

• Controller calibration
• Hardware dead zones
• Aircraft-specific control behaviour
• Simulator control processing

Check the controller calibration in the simulator before assuming that the StreamFlight display is incorrect.

Throttle Does Not Reach the Expected Endpoint

Test the display with another aircraft, particularly a default simulator aircraft.

If the behaviour changes between aircraft, the difference is likely related to the way the aircraft exposes its throttle or thrust-lever position.

Third-party airliners can use custom throttle logic, detents and reverse ranges that differ from conventional aircraft.

Works with One Aircraft but Not Another

This strongly suggests an aircraft-specific control implementation rather than a general StreamFlight connection problem.

Test the affected control using a default MSFS aircraft for comparison.

Dual-PC Display Does Not Appear

If the Control Input Display works locally but not on the streaming computer, check:

• Dual PC Setup / LAN Mode is enabled.
• Both computers are connected to the same local network.
• The correct LAN browser-source address is being used.
• Windows Firewall is not blocking StreamFlight.
• Port 38082 or the active fallback port 38083 is reachable.

General browser-source and Dual-PC troubleshooting is covered in Chapter 5 — Overlays & Gamer Mode and Chapter 15 — Troubleshooting.

7. Camera Control

StreamFlight includes integrated camera tools for Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024.

These tools allow you to create automated external camera movements without manually controlling the simulator camera throughout the sequence.

StreamFlight provides two camera modes:

• Orbit
• FlyBy

A dedicated STOP control returns control from an active StreamFlight camera sequence and attempts to return the view to the cockpit.

Camera Control is particularly useful for:

• Streaming
• Cinematic flight views
• Aircraft showcases
• Departure and arrival sequences
• Screenshots and video capture
• Adding automated external views during a flight

7.1 StreamFlight Camera Tools

The Camera Control tab contains the controls used to configure and operate StreamFlight's automated camera movements.

The two primary camera functions are:

Orbit

Moves the camera around the aircraft while maintaining an external view of it.

Orbit is useful when you want to showcase the aircraft from multiple angles without manually rotating the camera.

FlyBy

Creates a moving external camera sequence in which the aircraft passes the camera as the sequence progresses.

FlyBy is useful for creating cinematic views of the aircraft in motion.

Each mode has its own configuration settings so that the movement can be adjusted before the camera sequence is started.

StreamFlight also provides:

STOP

to end an active StreamFlight camera sequence.

7.2 Simulator Support

Camera Control currently supports:

StreamFlight communicates with the Microsoft Flight Simulator camera system through its MSFS integration.

The fact that StreamFlight can obtain standard telemetry from X-Plane and Prepar3D does not mean that the StreamFlight Camera Control feature is available with those simulators.

7.3 Orbit Camera

Orbit creates an automated camera movement around the aircraft.

Once started, StreamFlight positions and moves the external camera while keeping the aircraft as the focus of the sequence.

Orbit can be adjusted using three principal settings:

• Speed
• Distance
• Height

These determine how quickly the camera moves and where it is positioned relative to the aircraft.

A typical Orbit sequence can be used to provide a smooth moving view of the aircraft during:

• Cruise
• Climb
• Descent
• Ground operations
• Aircraft showcase sequences

7.4 Starting Orbit

Before starting Orbit, configure the required:

• Orbit Speed
• Orbit Distance
• Orbit Height

Then select:

START ORBIT

StreamFlight switches to the required external camera state and begins the Orbit sequence.

While Orbit is active, the camera continues moving according to the selected settings.

The StreamFlight camera status indicates that the Orbit function is active.

To end the sequence, use:

STOP

rather than manually attempting to terminate the StreamFlight camera movement.

7.5 Orbit Speed

Orbit Speed controls how quickly the camera moves around the aircraft.

A lower value produces a slower movement around the aircraft.

A higher value produces a faster orbit.

Slower settings are generally useful for:

• Cinematic shots
• Aircraft showcases
• Long external views

Faster settings may be useful where a more dynamic camera movement is desired.

The ideal value depends on:

• Aircraft size
• Desired visual effect
• Distance from the aircraft
• Length of time the Orbit sequence will remain active

The default Orbit Speed provides a useful starting point, after which the value can be adjusted to suit personal preference.

7.6 Orbit Distance

Orbit Distance determines how far the camera is positioned from the aircraft.

A smaller distance places the camera closer to the aircraft.

A larger distance provides a wider view.

Closer positions are useful when the aircraft itself should dominate the image.

Larger distances can provide more surrounding scenery and a broader view of the aircraft's environment.

The appropriate distance can vary considerably depending on the aircraft.

For example, a distance that works well with a small general-aviation aircraft may appear much closer when used with a large airliner.

7.7 Orbit Height

Orbit Height adjusts the vertical position of the Orbit camera relative to the aircraft.

Increasing the height places the camera higher relative to the aircraft.

Reducing the height produces a lower viewpoint.

This can significantly change the character of an Orbit sequence.

For example:

• A higher camera position can provide a better view of the upper fuselage and wings.
• A lower camera position can emphasise the underside, engines or landing gear.
• A moderate height provides a more conventional aircraft-viewing angle.

Orbit Height can be combined with Orbit Distance to create a wide variety of external views.

7.8 FlyBy Camera

FlyBy provides a different style of automated camera movement.

Rather than continuously moving around the aircraft, FlyBy positions and moves the camera so that the aircraft passes through the scene.

This can create views similar to watching an aircraft pass from a fixed or moving observation point.

FlyBy can be particularly effective during:

• Low-level flight
• Takeoff
• Approach
• Cruise
• Scenic flying
• Aircraft showcase sequences

The FlyBy system provides settings for:

• Speed
• Start Position
• End Position
• Distance

These values determine the movement and geometry of the sequence.

7.9 FlyBy Speed

FlyBy Speed controls the speed of the camera movement used during the FlyBy sequence.

Changing this value alters how quickly the camera progresses through the sequence.

Lower values create a slower movement.

Higher values create a faster movement.

The visual result also depends on:

• Aircraft groundspeed
• Start position
• End position
• Camera distance

Experimenting with these settings allows the FlyBy to be adapted to different aircraft and flight situations.

7.10 FlyBy Start Position

FlyBy Start defines the starting position used by the FlyBy camera sequence.

This determines where the camera movement begins relative to the aircraft and the FlyBy path.

Changing the start position affects how the aircraft first appears within the sequence.

A larger separation can provide more time for the aircraft to approach the camera view, while a shorter separation creates a more immediate FlyBy.

The best value depends on the aircraft's speed and the type of shot being created.

7.11 FlyBy End Position

FlyBy End defines the ending position of the FlyBy sequence.

Together, the Start and End settings define the overall movement of the FlyBy camera.

The end position determines how far the sequence continues after the aircraft has passed through the primary viewing area.

Adjusting both values allows the FlyBy to be made:

• Short and fast
• Long and cinematic
• Focused closely around the aircraft
• Extended to show more of the surrounding environment

7.12 FlyBy Distance

FlyBy Distance determines the lateral separation between the camera path and the aircraft.

A smaller value brings the camera closer to the aircraft's path.

A larger value creates a more distant view.

The appropriate distance depends heavily on aircraft size and speed.

For example:

• A small general-aviation aircraft may benefit from a relatively close FlyBy.
• A large airliner may require greater separation to remain comfortably within the camera view.

7.13 STOP and Returning to the Cockpit

Use the STOP control to terminate an active StreamFlight camera sequence.

When STOP is selected, StreamFlight:

1. Stops the active Orbit or FlyBy sequence.
2. Ends StreamFlight's active camera movement.
3. Attempts to return the simulator view to the cockpit.

The camera status changes while StreamFlight completes the stop and return sequence.

Returning the camera reliably is more complex than simply ending the movement because Microsoft Flight Simulator must transition away from the external camera state and restore the cockpit view.

StreamFlight includes dedicated return-to-cockpit handling for this purpose.

Returning to the Cockpit in MSFS 2024

Microsoft Flight Simulator 2024 has differences in camera behaviour compared with MSFS 2020.

StreamFlight includes additional handling intended to improve the reliability of returning to the cockpit after an automated camera sequence.

However, the final camera state can still be influenced by the simulator's own camera system.

This is discussed further in Section 7.16 — MSFS 2020 / MSFS 2024 Camera Considerations.

7.14 Disabling StreamFlight Camera Controls

StreamFlight provides an option to disable its camera controls.

This is useful when another application is responsible for controlling the Microsoft Flight Simulator camera.

When StreamFlight camera controls are disabled, StreamFlight does not attempt to operate its Orbit or FlyBy camera functions.

The StreamFlight interface indicates that camera control is disabled.

This setting is remembered so that users of an external camera application do not need to disable StreamFlight camera control every time the application starts.

7.15 Using StreamFlight with P42 ChasePlane

Users of P42 ChasePlane or another external camera-control application should disable StreamFlight's own camera controls.

StreamFlight provides the Disable StreamFlight Camera Controls option specifically to prevent competing applications from attempting to control the simulator camera.

When using ChasePlane:

1. Open the StreamFlight Camera Control tab.
2. Enable Disable StreamFlight Camera Controls.
3. Allow ChasePlane to manage the simulator camera.

Other StreamFlight functionality can continue to operate normally.

For example, disabling StreamFlight Camera Control does not disable:

• Flight telemetry
• Gamer Mode
• Browser-source overlays
• Flight progress
• Landing Rate
• Live ATC
• Passenger Manifest
• Other unrelated StreamFlight features

The option only prevents StreamFlight from controlling the simulator camera.

7.16 MSFS 2020 / MSFS 2024 Camera Considerations

Although StreamFlight supports Camera Control with both MSFS 2020 and MSFS 2024, the simulator camera systems are not identical.

Microsoft Flight Simulator 2020

StreamFlight can operate its Orbit and FlyBy sequences and return the camera after the sequence has been stopped.

As with any external camera-control system, simulator state and manual camera changes made during an active sequence can influence the final result.

Microsoft Flight Simulator 2024

MSFS 2024 introduced camera behaviour that differs in some respects from MSFS 2020.

StreamFlight includes additional handling to improve the reliability of returning to the cockpit after an Orbit or FlyBy.

In normal operation, selecting STOP should end the StreamFlight camera sequence and return the view.

However, if the simulator's camera state has been changed independently while the StreamFlight sequence is active, the final view can be affected by the state maintained by MSFS itself.

Manual Camera Changes During an Active Sequence

For the most predictable results, avoid manually switching between unrelated simulator camera modes while StreamFlight Orbit or FlyBy is active.

If you want to return to normal camera operation:

1. Select STOP in StreamFlight.
2. Allow StreamFlight to complete the return sequence.
3. Resume normal simulator camera control.

7.17 Camera Troubleshooting

If Orbit or FlyBy does not behave as expected, begin by checking the current simulator and StreamFlight camera state.

Camera Controls Are Unavailable

Confirm that:

• You are using Microsoft Flight Simulator 2020 or 2024.
• StreamFlight has detected and connected to MSFS.
• Disable StreamFlight Camera Controls is not enabled.

Camera Control is not currently available for X-Plane or Prepar3D.

Orbit Does Not Start

Check that:

• StreamFlight is connected to MSFS.
• Camera Control has not been disabled.
• No external camera application is attempting to take control of the simulator camera.

If using P42 ChasePlane, StreamFlight Camera Control should normally be disabled rather than used simultaneously.

FlyBy Does Not Look as Expected

The FlyBy appearance depends on the combination of:

• Aircraft speed
• FlyBy Speed
• Start Position
• End Position
• Distance

A configuration that works well with a slow general-aviation aircraft may not produce the same visual result with a fast airliner.

Adjust the values to suit the aircraft and flight situation.

Orbit Is Too Close or Too Far Away

Adjust Orbit Distance.

Remember that the same numerical distance can appear very different when used with aircraft of different physical sizes.

Orbit Is Too High or Too Low

Adjust Orbit Height.

Combine Height and Distance adjustments to achieve the desired viewing angle.

Camera Movement Is Too Fast

Reduce the appropriate:

• Orbit Speed
• FlyBy Speed

depending on the active camera mode.

STOP Does Not Immediately Return to the Expected View

Allow StreamFlight a moment to complete its camera-return sequence.

Avoid repeatedly pressing STOP or rapidly switching simulator camera modes while the return is being performed.

If necessary, return to the cockpit using the simulator's normal camera controls after the StreamFlight sequence has fully stopped.

MSFS 2024 Returns to an Unexpected External View

MSFS 2024 can retain camera state differently from MSFS 2020.

StreamFlight includes additional return-to-cockpit handling, but in some situations the simulator may restore an external state rather than the expected cockpit view.

If this occurs:

1. Confirm that the StreamFlight camera sequence has stopped.
2. Return to the cockpit using the simulator's normal camera control.
3. Avoid manually changing camera modes during the next StreamFlight Orbit or FlyBy sequence.

Camera Behaviour Becomes Unpredictable with Another Camera Application

Do not allow StreamFlight and another camera-control application to compete for the MSFS camera.

Enable:

Disable StreamFlight Camera Controls

and allow the external camera application to manage the camera.

Other StreamFlight Features Continue Working

A Camera Control problem does not necessarily indicate that StreamFlight has lost its simulator connection.

Check whether:

• Telemetry is still updating.
• Flight phase is still changing normally.
• Other StreamFlight features remain active.

If those features continue working, investigate Camera Control specifically rather than the general simulator connection.

Further simulator and camera troubleshooting is provided in Chapter 15 — Troubleshooting.

8. RAAS — Runway Awareness & Advisory System

StreamFlight includes a Runway Awareness & Advisory System (RAAS) designed to increase awareness of the aircraft's position and movement in relation to airport runways.

RAAS uses simulator aircraft information together with runway data to provide automatic spoken announcements during relevant stages of ground operation, approach, landing and rollout.

Depending on the enabled options and current situation, StreamFlight can provide announcements relating to:

• Approaching a runway
• Entering or occupying a runway
• Runway distance remaining
• Short runway conditions
• Long landings

RAAS operates automatically once enabled. You do not need to manually trigger announcements during normal flight operations.

8.1 What is RAAS?

RAAS stands for:

Runway Awareness & Advisory System

The purpose of the system is to provide additional awareness of the aircraft's relationship to runways.

Rather than requiring the pilot to constantly monitor a StreamFlight window, RAAS primarily communicates through spoken audio announcements.

For example, depending on the aircraft position and enabled features, StreamFlight may announce that the aircraft is:

• Approaching a runway
• On a runway
• Running out of available runway
• Operating on a runway considered short
• Landing significantly further along the runway than expected

The system monitors the aircraft automatically while StreamFlight is connected to the simulator.

RAAS is separate from StreamFlight's normal telemetry and overlays.

It is therefore possible to use RAAS without displaying Gamer Mode or an OBS / Streamlabs Desktop browser source.

8.2 Simulator Support

StreamFlight RAAS currently supports:

RAAS currently receives its required live aircraft information through StreamFlight's Microsoft Flight Simulator integration.

Although StreamFlight can obtain standard flight telemetry from X-Plane and Prepar3D, the RAAS feature itself is currently restricted to MSFS 2020 and MSFS 2024.

8.3 Enabling RAAS

RAAS is configured from the RAAS tab.

To activate the system, enable:

Enable RAAS

Once enabled and StreamFlight is connected to a supported simulator, RAAS begins monitoring the aircraft and its relationship to nearby runways.

Individual announcement types can then be enabled or disabled according to your preference.

This allows you to use the complete StreamFlight RAAS feature set or only the announcements you want.

8.4 Approaching Runway

The Approaching Runway option provides an announcement when StreamFlight determines that the aircraft is approaching a relevant runway.

The purpose of the announcement is to increase awareness of the runway the aircraft is approaching.

This can be useful during both ground operations and the approach environment.

StreamFlight evaluates the aircraft's position and relationship to the runway before determining whether an announcement should occur.

The announcement is generated automatically when the required conditions are satisfied.

8.5 On Runway

The On Runway option provides an announcement when StreamFlight determines that the aircraft has entered or is positioned on a runway.

This provides additional awareness that the aircraft has moved onto a runway.

The announcement can be particularly useful when:

• Taxiing for departure
• Entering the departure runway
• Crossing from a taxiway onto a runway
• Operating at an unfamiliar airport

8.6 Runway Remaining

The Runway Remaining function provides distance-related announcements as the aircraft progresses along a runway.

This is intended to improve awareness of the amount of runway remaining ahead of the aircraft.

The function is particularly relevant during:

• Landing rollout
• Continued movement towards the end of a runway
• Situations where runway remaining becomes operationally significant

StreamFlight monitors the aircraft's position along the runway and provides announcements at relevant remaining-distance points.

Why Runway Remaining Can Be Useful

During a landing rollout, it can be difficult to judge the remaining runway distance visually, particularly:

• At night
• In poor visibility
• On unfamiliar runways
• On unusually long or short runways

The spoken distance announcements provide an additional indication of how much runway remains.

8.7 Caution Short Runway

StreamFlight includes a Caution Short Runway option.

When enabled, RAAS can provide a caution when the runway situation meets StreamFlight's short-runway criteria.

The purpose of this function is to draw attention to a runway where the available length may warrant additional awareness.

The caution should prompt the simulator pilot to consider the runway being used and the aircraft's current operation.

Whether a runway is suitable for a particular takeoff or landing depends on many factors, including:

• Aircraft type
• Aircraft weight
• Weather
• Wind
• Runway condition
• Runway slope
• Aircraft configuration
• Airport elevation
• Required performance margins

StreamFlight RAAS does not replace the aircraft's performance calculations.

A short-runway caution should therefore be treated as an awareness advisory, not as a determination that the aircraft can or cannot use the runway.

8.8 Long Landing

The Long Landing option provides additional awareness when the aircraft touches down significantly further along the runway than expected.

A touchdown occurring well beyond the beginning of the available landing area leaves less runway available for deceleration.

StreamFlight monitors the touchdown position and can issue a Long Landing announcement when the required conditions are met.

The function is particularly useful for highlighting situations where the aircraft has floated considerably beyond the normal touchdown area.

8.9 Selecting RAAS Announcements

StreamFlight allows individual RAAS announcement types to be enabled or disabled.

Available user options include:

• Approaching Runway
• On Runway
• Runway Remaining
• Caution Short Runway
• Long Landing

This allows RAAS to be configured according to personal preference.

For example, you may want:

• Approaching Runway
• On Runway
• Runway Remaining

while choosing not to use the Short Runway or Long Landing announcements.

Disabling an individual option prevents that particular StreamFlight RAAS function from generating its normal announcement.

The overall:

Enable RAAS

setting remains the master control for the complete system.

8.10 Audio Output Device

StreamFlight allows the RAAS audio output device to be selected.

This determines where the RAAS announcements are played.

Depending on your Windows audio configuration, this could be:

• Headphones
• Desktop speakers
• Gaming headset
• Dedicated simulator audio device
• Another available Windows playback device

This is particularly useful for streaming setups.

For example, you may want RAAS audio to play through the same device captured by OBS / Streamlabs Desktop, or you may prefer it to be routed separately.

Select the appropriate device from the Audio Output Device control.

If an expected device does not appear, confirm that Windows recognises and has enabled the device.

8.11 RAAS Volume

The Volume control adjusts the playback level of StreamFlight RAAS announcements.

Use this to balance RAAS against:

• Simulator engine sounds
• ATC audio
• Voice chat
• Stream audio
• Other simulator warnings

The ideal level depends on your audio setup.

RAAS should normally be loud enough to be clearly understood without unnecessarily overpowering other important audio.

If you change the volume, use TEST AUDIO to confirm the resulting level before beginning a flight.

8.12 Testing RAAS Audio

StreamFlight provides:

TEST AUDIO

To confirm that RAAS announcements can be heard through the selected audio device.

Before relying on RAAS during a flight:

1. Enable RAAS.
2. Select the required Audio Output Device.
3. Set the desired Volume.
4. Select TEST AUDIO.
5. Confirm that the test announcement is clearly audible.

This is especially useful after:

• Changing headphones
• Changing Windows playback devices
• Reconfiguring streaming audio
• Moving StreamFlight to another computer
• Changing the RAAS volume

Test Audio Cannot Be Heard

If the test is not audible:

1. Confirm the correct output device is selected.
2. Check the StreamFlight RAAS volume.
3. Check the Windows volume for the selected device.
4. Confirm the device is not muted.
5. Confirm the device is still connected and available.

If TEST AUDIO works correctly but operational RAAS announcements do not occur during a flight, investigate the RAAS configuration or runway-detection conditions rather than the audio device.

8.13 When RAAS Announcements Occur

RAAS announcements are event-driven.

They are not played continuously simply because RAAS is enabled.

StreamFlight monitors the aircraft and waits until the conditions for a particular announcement are satisfied.

Depending on the announcement, this can involve factors such as:

• Aircraft position
• Runway proximity
• Runway alignment
• Whether the aircraft is on the ground or airborne
• Aircraft movement
• Remaining runway distance
• Touchdown position

This prevents RAAS from repeatedly announcing information when it is not relevant.

Announcements Are Context-Sensitive

Simply being near a runway is not necessarily sufficient to trigger every RAAS announcement.

For example, an aircraft may be taxiing close to a runway without actually approaching or entering it.

Likewise, during an arrival, StreamFlight evaluates the aircraft's relationship to the runway before generating the relevant announcement.

Not Every Flight Produces Every Announcement

The enabled options determine which RAAS features are available, but an enabled announcement is only heard if the appropriate conditions occur.

For example:

• A normal landing should not produce a Long Landing announcement.
• A runway that does not meet the short-runway criteria should not produce a Caution Short Runway announcement.
• Runway Remaining announcements depend on the aircraft progressing through the relevant runway-distance points.

8.14 RAAS During Departure

During departure operations, RAAS can provide runway-position awareness before takeoff.

A typical sequence may involve:

1. Taxiing towards the departure runway.
2. Approaching the runway.
3. Entering the runway.
4. Aligning for departure.
5. Beginning the takeoff roll.

Depending on the enabled RAAS options and the aircraft's position, StreamFlight may provide relevant runway announcements during this sequence.

For example, an Approaching Runway announcement can provide awareness as the aircraft approaches the runway, while On Runway confirms that StreamFlight has detected the aircraft on the runway.

The exact announcements depend on the situation and the RAAS options that have been enabled.

8.15 RAAS During Approach and Landing

RAAS also operates during the arrival phase.

As the aircraft approaches the destination runway, StreamFlight monitors the aircraft's relationship to the runway.

Depending on the enabled features and flight situation, this can result in:

• Approaching Runway awareness
• Short Runway caution
• Long Landing awareness
• Runway Remaining announcements during landing and rollout

After touchdown, StreamFlight continues monitoring the aircraft's progress along the runway.

This allows the appropriate landing and runway-remaining advisories to be generated as the rollout progresses.

A normal approach and landing will not necessarily generate every available RAAS announcement.

For example, Long Landing is only relevant when the touchdown meets the conditions for that advisory.

8.16 RAAS Limitations and Considerations

StreamFlight RAAS is designed to enhance situational awareness within a flight simulator.

There are several important limitations to understand.

RAAS Does Not Control the Aircraft

StreamFlight does not:

• Apply brakes
• Reject a takeoff
• Initiate a go-around
• Change aircraft configuration
• Control steering
• Prevent runway entry

RAAS provides information and announcements only.

RAAS Does Not Provide ATC Clearance

An announcement such as:

Approaching Runway

or:

On Runway

does not mean that ATC has cleared the aircraft to enter, cross, take off from or land on that runway.

RAAS Is Not a Performance Calculator

A short-runway or long-landing announcement should not be interpreted as an aircraft performance calculation.

StreamFlight does not use RAAS to determine whether the aircraft can safely:

• Take off
• Land
• Stop within the remaining runway

Use the appropriate aircraft performance tools where required.

Airport and Scenery Differences

The runway information used by StreamFlight may not always correspond perfectly with every simulator scenery package.

This is particularly relevant with:

• Add-on airports
• Recently modified airports
• Changed runway layouts
• Scenery containing inaccurate runway positioning

Such differences can affect whether an announcement occurs or the exact point at which it is triggered.

If RAAS behaves correctly at most airports but differently at one particular airport, the airport or scenery should therefore be considered when troubleshooting.

Simulator Data

RAAS depends on aircraft information supplied by Microsoft Flight Simulator.

Unusual or incorrect simulator data can therefore affect RAAS behaviour.

Simulator Use Only

StreamFlight is software for flight simulation.

8.17 RAAS Troubleshooting

If RAAS does not behave as expected, first determine whether the problem relates to:

• Simulator support
• RAAS configuration
• Audio
• A particular announcement
• A specific airport or scenery package

No RAAS Announcements

Confirm that:

• Enable RAAS is enabled.
• The required individual announcement option is enabled.
• Microsoft Flight Simulator 2020 or 2024 is connected.
• The aircraft is in a situation where the announcement would normally be expected.

RAAS is not currently supported with X-Plane or Prepar3D.

TEST AUDIO Cannot Be Heard

Check:

• Audio Output Device
• RAAS Volume
• Windows playback-device volume
• Windows mute state
• Headset or speaker connection

If TEST AUDIO cannot be heard, resolve the audio problem before investigating operational RAAS behaviour.

TEST AUDIO Works but Operational Announcements Do Not

If TEST AUDIO works, StreamFlight is capable of playing RAAS audio through the selected device.

Next confirm that:

• RAAS is enabled.
• The required announcement is enabled.
• MSFS is connected.
• The aircraft has actually encountered the conditions required for the announcement.

Remember that simply being near a runway does not necessarily trigger every RAAS event.

One Announcement Works but Another Does Not

Check the individual RAAS option.

For example, Approaching Runway can be enabled while Runway Remaining is disabled.

Each optional announcement should therefore be checked separately.

Incorrect Runway Is Announced

Consider whether the aircraft is:

• Close to another runway
• Approaching a runway intersection
• Operating at an airport with closely spaced runways
• Using modified or add-on scenery

Runway identification depends on the aircraft's position and the runway information available to StreamFlight.

RAAS Works at One Airport but Not Another

This may indicate an airport-data or scenery-specific issue.

Test the same RAAS function at another airport.

If the feature works elsewhere, record:

• Airport ICAO
• Runway
• Aircraft
• Direction of operation
• Expected announcement
• Announcement actually received, if any

This information can be useful when reporting the problem.

Runway Remaining Does Not Announce

Confirm that:

• Runway Remaining is enabled.
• RAAS has successfully identified the relevant runway.
• The aircraft has reached the appropriate runway condition.
• The aircraft is progressing through the relevant remaining-distance points.

Long Landing Does Not Announce

A Long Landing announcement is not generated for every landing.

The aircraft must meet the conditions used by StreamFlight to identify a sufficiently long touchdown.

A normal touchdown should therefore not generate a Long Landing announcement simply because the option is enabled.

Caution Short Runway Does Not Announce

The option must be enabled and the runway must meet the conditions required for StreamFlight's short-runway advisory.

Not every runway should produce this caution.

Announcements Are Too Loud or Too Quiet

Adjust the StreamFlight RAAS Volume control and use TEST AUDIO to verify the new level.

RAAS Works but Another StreamFlight Feature Does Not

RAAS operates independently from several other StreamFlight display features.

For example, RAAS audio does not require:

• Gamer Mode
• OBS / Streamlabs Desktop
• Live Flight Telemetry browser source
• Camera Control

A problem with one of those features does not necessarily indicate a RAAS problem.

Further RAAS and simulator troubleshooting is provided in Chapter 15 — Troubleshooting.

9. Landing Rate

StreamFlight includes a built-in Landing Rate feature that automatically detects touchdown and records the aircraft's vertical speed at landing.

The result is displayed in feet per minute (FPM) and assigned one of five StreamFlight landing classifications:

• BUTTER LANDING
• GOOD LANDING
• FIRM LANDING
• HARD LANDING
• SHOTDOWN

Landing Rate can be displayed directly on screen through StreamFlight's Gamer Mode landing graphic, through a dedicated OBS / Streamlabs Desktop Browser Source, or used by external applications through StreamFlight's output files.

For streamers, the landing result can also be passed to Streamer.bot or other compatible chatbot/automation software, allowing the result to be posted automatically to chat.

9.1 What is Landing Rate?

Landing Rate measures the aircraft's vertical speed at the moment StreamFlight detects touchdown.

The result is expressed in:

feet per minute (FPM)

For example:

-185 FPM

indicates that the aircraft was descending at approximately 185 feet per minute when the landing was detected.

StreamFlight then assigns a classification to the landing based on the detected rate.

For example, a landing may be displayed as:

-185 FPM
GOOD LANDING

The Landing Rate feature operates automatically once enabled. You do not need to press a button at touchdown.

9.2 Enabling Landing Rate

Landing Rate is controlled from the Overlays tab.

Enable:

Enable Landing Rate

This is the master control for Landing Rate detection.

When enabled, StreamFlight monitors the aircraft for a landing event.

When a landing is detected, StreamFlight can:

• Record the landing rate.
• Classify the landing.
• Update the Landing Rate output files.
• Publish the result to the dedicated Landing Rate Browser Source.
• Display the native landing graphic when Show In Gamer Mode is enabled.

The output files are updated when StreamFlight processes the detected landing.

9.3 How Landing Rate is Detected

StreamFlight monitors simulator aircraft data while the aircraft is airborne and detects the transition associated with touchdown.

At the landing event, the aircraft's vertical movement is captured and used to produce the Landing Rate result.

The value represents the touchdown rate at the point detected by StreamFlight rather than the aircraft's vertical speed several seconds before or after landing.

The result is then:

1. Recorded in FPM.
2. Assigned a landing classification.
3. Made available to the enabled StreamFlight display and integration features.

This process is automatic.

Touch-and-Go Operations

Landing Rate detection is based on the landing event itself, so a full shutdown at the destination is not required simply to obtain a Landing Rate result.

This makes the feature useful for operations such as:

• Normal destination landings
• Circuits
• Touch-and-go practice
• Repeated landing practice

9.4 Landing Rate in Feet per Minute

StreamFlight displays landing rate as a negative FPM value.

For example:

-95 FPM

represents a descent rate of 95 feet per minute at touchdown.

Likewise:

-320 FPM

represents a descent rate of 320 feet per minute.

The negative sign represents downward vertical movement.

StreamFlight uses the magnitude of this value to determine the Landing Rate classification.

The five classification ranges used by StreamFlight v3.0.0 are:

These classifications are StreamFlight's own presentation of the detected touchdown rate.

9.5 Landing Classifications

Every detected landing is assigned one of five classifications.

The classification provides an immediate, easy-to-understand interpretation of the recorded FPM.

The classifications progress from:

BUTTER LANDING

through:

GOOD LANDING

FIRM LANDING

HARD LANDING

to:

SHOTDOWN

The classification is displayed alongside the landing rate where supported and is also written separately to the StreamFlight Output Folder.

9.6 Butter Landing

A touchdown between:

-1 and -100 FPM

is classified as:

BUTTER LANDING

This is the softest StreamFlight Landing Rate classification.

For example:

-82 FPM — BUTTER LANDING

would fall within this range.

StreamFlight's RAAS Long Landing feature, when enabled and applicable, is separate from the Landing Rate classification.

9.7 Good Landing

A touchdown between:

-101 and -250 FPM

is classified as:

GOOD LANDING

For example:

-195 FPM — GOOD LANDING

falls within this classification.

This provides a broad range for normal touchdown rates before StreamFlight moves into the Firm Landing classification.

9.8 Firm Landing

A touchdown between:

-251 and -400 FPM

is classified as:

FIRM LANDING

For example:

-315 FPM — FIRM LANDING

falls within this range.

The classification describes the FPM recorded by StreamFlight and should not be interpreted as a maintenance determination for the simulated aircraft.

9.9 Hard Landing

A touchdown between:

-401 and -600 FPM

is classified as:

HARD LANDING

For example:

-485 FPM — HARD LANDING

falls within this range.

This represents a substantially higher touchdown descent rate than the Butter, Good or Firm classifications.

Again, this is a StreamFlight classification and not an aircraft-specific structural assessment.

9.10 Shotdown

A touchdown at:

-601 FPM or greater descent rate

is classified as:

SHOTDOWN

For example:

-725 FPM — SHOTDOWN

would fall within this classification.

SHOTDOWN is StreamFlight's highest Landing Rate category and is intentionally named to provide a distinctive and entertaining result for particularly heavy touchdowns.

9.11 Showing Landing Rate in Gamer Mode

StreamFlight can display the Landing Rate result directly on screen using its native landing graphic.

Enable:

Show In Gamer Mode

When enabled, the Landing Rate graphic appears automatically after StreamFlight detects a landing.

The graphic displays the landing result for the configured amount of time before disappearing automatically.

This provides immediate feedback without requiring OBS / Streamlabs Desktop.

It is particularly useful for:

• Users flying without streaming software
• Single-monitor flying
• Streamers who want the graphic visible directly on the simulator display
• Recording or capturing the simulator display itself

Gamer Mode Is Optional

Landing Rate detection does not depend on the Gamer Mode graphic being enabled.

You can disable Show In Gamer Mode and still use:

• The Landing Rate Browser Source
• Landing Rate output files
• External integrations

The native Gamer Mode graphic is simply one way of displaying the result.

9.12 Landing Rate Display Time

The Display Time setting determines how long the Landing Rate graphic remains visible after a landing.

The selected duration is shared by both the dedicated Landing Rate Browser Source and the native Landing Rate graphic.

This allows you to control how long viewers or the pilot have to read the result.

A shorter display time keeps the graphic brief.

A longer display time leaves the result visible for longer after touchdown.

Choose a duration appropriate to your overlay or streaming layout.

9.13 Positioning the Gamer Mode Landing Graphic

The native Landing Rate graphic can be repositioned using the positioning controls provided in the Landing Rate section.

Use the directional controls to move the graphic to the preferred location on the display.

This allows the Landing Rate result to be positioned so that it does not obscure important simulator information such as:

• Instruments
• Aircraft displays
• ATC windows
• Navigation displays
• Other StreamFlight overlays

The positioning controls affect the native StreamFlight Landing Rate graphic.

OBS / Streamlabs Desktop Positioning

The dedicated Browser Source is positioned separately within OBS / Streamlabs Desktop.

Moving the Gamer Mode landing graphic therefore does not require you to reposition the Browser Source in your streaming scene.

9.14 Changing Landing Graphic Size

StreamFlight provides + and − controls for changing the size of the native Landing Rate graphic.

The current size is shown as a percentage.

Use:

• +

to increase the graphic size.

Use:

• −

to reduce the graphic size.

This allows the Landing Rate display to be adjusted for:

• Different monitor resolutions
• Different simulator layouts
• Different viewing distances
• Personal preference

The size setting applies to the native Gamer Mode landing graphic.

The Browser Source can be resized independently in OBS / Streamlabs Desktop.

9.15 Landing Rate OBS Browser Source

StreamFlight provides a dedicated Browser Source specifically for Landing Rate.

This is separate from:

• Live Flight Telemetry
• Flight Progress
• Control Input Display

The Landing Rate Browser Source uses:

The Browser Source receives a landing result when StreamFlight detects a landing.

The result is then displayed for the duration selected in Display Time.

9.16 Adding Landing Rate to OBS / Streamlabs Desktop

To add the Landing Rate display to your streaming layout:

1. Open StreamFlight.
2. Go to the Overlays tab.
3. Locate the Landing Rate section.
4. Use the provided COPY control for the Landing Rate Browser Source.
5. Open OBS / Streamlabs Desktop.
6. Add a new Browser Source.
7. Paste the copied StreamFlight Browser Source address.
8. Set the Browser Source dimensions as required.
9. Position it within your scene.
10. Use StreamFlight's TEST function to confirm the result is displayed.

The Browser Source normally remains visually inactive until StreamFlight publishes a Landing Rate result.

After the configured display time expires, the landing graphic disappears automatically.

Dual-PC Streaming

The Landing Rate Browser Source can also be used in the dual-PC configuration described in Chapter 5.

In this arrangement:

Simulator PC

• Runs Microsoft Flight Simulator.
• Runs StreamFlight.
• Detects the landing.

Streaming PC

• Runs OBS / Streamlabs Desktop.
• Displays the Landing Rate Browser Source.

The Browser Source is delivered across the local network using StreamFlight's LAN mode.

9.17 Testing the Landing Rate Display

StreamFlight provides a TEST function for checking the Landing Rate display without having to perform an actual landing.

When TEST is selected, StreamFlight generates a test Landing Rate result.

The test deliberately selects from the five Landing Rate classifications and generates a corresponding FPM value within that classification's range.

The TEST function publishes the result to the Landing Rate Browser Source. If Show In Gamer Mode is enabled, the native Landing Rate graphic is also displayed.

This makes TEST useful when:

• Setting up the Browser Source for the first time
• Positioning the source in OBS / Streamlabs Desktop
• Checking Browser Source visibility
• Adjusting the native graphic position
• Adjusting the native graphic size
• Testing the configured Display Time

9.18 Landing Rate Output Files

When StreamFlight processes a detected landing, three Landing Rate files are updated in the user-selected Output Folder:

For example, following a landing, the files can provide the individual values needed by external applications.

Contains the numerical Landing Rate value.

Example:

• -195

This is useful where another application needs only the FPM value.

Contains the classification.

Example:

• GOOD LANDING

This allows the classification to be displayed or processed independently.

Contains the prepared Landing Rate message.

This is useful when an external application requires a ready-to-use landing result rather than constructing one from the separate FPM and classification files.

These files can be used with:

• OBS
• Streamer.bot
• Other compatible chatbot/automation software
• Custom overlays
• External applications
• User-created integrations

The complete StreamFlight Output Folder is documented in Chapter 13 — Output Files & External Integration.

9.19 Using Landing Rate with Streamer.bot / Chat

StreamFlight's Landing Rate output can be used with Streamer.bot or other compatible chatbot/automation software to publish the landing result to a streaming chat.

For example, a stream could automatically display a message based on:

• landingrate_message.txt

after the aircraft lands.

This allows viewers to see the landing result without requiring the streamer to manually type it into chat.

StreamFlight's Role

StreamFlight:

• Detects the landing.
• Calculates the Landing Rate.
• Determines the classification.
• Creates the Landing Rate output.
• Updates the relevant files.

The chatbot or automation software is responsible for:

• Reading or reacting to the StreamFlight output.
• Deciding where the message should be sent.
• Posting the message to the configured streaming platform.

This distinction is important.

StreamFlight does not require a Twitch, YouTube or other streaming account simply to calculate a Landing Rate.

Landing Rate works independently as a StreamFlight feature.

Streamer.bot Integration

Streamer.bot can be configured to use the Landing Rate output as part of a custom streaming automation.

This can be used to create workflows such as:

Aircraft touches down → StreamFlight records Landing Rate → Streamer.bot publishes result to chat

Depending on the user's streaming configuration, the automation can then determine which connected chat or platform receives the result.

This same principle applies to other compatible chatbot or automation software capable of consuming StreamFlight's output.

Landing Rate therefore provides several independent ways to use the same touchdown result:

For the pilot

• Gamer Mode landing graphic

For stream viewers

• OBS / Streamlabs Desktop Browser Source

For custom layouts

• StreamFlight output files

For chat interaction

• Streamer.bot or other compatible chatbot/automation software

These options can be used individually or together.

10. Live ATC: VATSIM & IVAO

StreamFlight includes a Live ATC information feature for VATSIM and IVAO.

When either of these networks is selected, StreamFlight monitors the aircraft’s active COM1 frequency and compares it with current controller information from the selected network.

When a matching controller is identified, StreamFlight can provide:

• Controller callsign
• Controller frequency

For VATSIM, StreamFlight can also recognise the relevant published CTAF where applicable.

StreamFlight does not connect the pilot to VATSIM or IVAO and does not transmit or receive ATC audio. The normal network pilot client remains responsible for communications.

10.1 What is Live ATC?

Live ATC allows StreamFlight to associate the frequency currently active on the aircraft’s COM1 radio with a controller operating on the selected online network.

The basic process is:

Select VATSIM or IVAO → Tune COM1 → StreamFlight checks network data → Matching station is identified

StreamFlight supplies the Live ATC system with the active COM1 frequency together with aircraft position and departure/destination information.

For example, if COM1 is tuned to:

• 118.500

and the selected network reports an appropriate controller operating on that frequency, StreamFlight may identify:

• EGLL_TWR | 118.500

The information changes automatically as the aircraft radio is retuned during the flight.

What Live ATC Does Not Do

Live ATC does not replace your VATSIM or IVAO pilot software.

StreamFlight does not:

• Log you into an ATC network
• Transmit voice
• Receive controller audio
• Send text messages to controllers
• File an online network flight plan
• Issue ATC clearances

Its purpose is to provide useful ATC identification information alongside the rest of the StreamFlight flight data.

10.2 Selecting a Network

The active flight network is selected using StreamFlight’s NETWORK control.

Available Network selections in v3.0.0 include:

• OFFLINE
• VATSIM
• IVAO
• PILOTEDGE
• BATC
• SI.AI
• JOINFS
• UNIFLY
• MSFS20
• MSFS24

These Network selections are used more broadly by StreamFlight for flight information, overlays and output data. The complete Network feature is documented later in Chapter 14 — User Settings & X-Plane Configuration.

For the purposes of Live ATC, however, there is one simple rule:

Only VATSIM and IVAO enable Live ATC.

The Live ATC tracker explicitly checks whether the selected Network is VATSIM or IVAO. If neither is selected, any current Live ATC result is cleared and controller matching stops.

Therefore:

Selecting another network does not mean that the Network selection itself is unused. It can still be displayed by StreamFlight and written to network.txt. It simply means that Live ATC controller detection is not active.

10.3 VATSIM

Select:

VATSIM

when flying on the VATSIM network and you want StreamFlight Live ATC information.

StreamFlight checks VATSIM controller information for the active COM1 frequency.

If only one controller is using that frequency, StreamFlight can identify that controller directly.

Where the same frequency is being used by multiple VATSIM controllers, StreamFlight can use geographic information associated with VATSIM transceivers to determine which controller is most relevant to the aircraft’s current position.

This is important because the same radio frequency may be reused in different geographic regions.

Example

A controller may be identified as:

• EGLL_TWR | 118.500

As the pilot changes frequency, StreamFlight checks the newly active COM1 frequency and updates the ATC result accordingly.

10.4 IVAO

Select:

IVAO

when flying on the IVAO network and you want StreamFlight Live ATC information.

When IVAO is selected, StreamFlight uses its IVAO controller provider rather than the VATSIM provider when performing the initial controller lookup.

The operating principle remains the same:

1. IVAO is selected.
2. StreamFlight reads the active COM1 frequency.
3. Current controller information is checked.
4. A matching station is identified where available.
5. The Live ATC result is updated.

StreamFlight remains an information companion only. The IVAO pilot client remains responsible for the actual connection and communications.

10.5 How COM1 Detection Works

StreamFlight’s Live ATC system uses the active COM1 frequency.

For Microsoft Flight Simulator, StreamFlight reads:

• COM ACTIVE FREQUENCY:1

directly from simulator telemetry.

StreamFlight also receives COM2 telemetry, but Live ATC matching specifically uses COM1.

Active and Standby Frequencies

Most aircraft radios have:

• Active frequency
• Standby frequency

Entering a controller frequency into the standby side is not sufficient.

It must normally be transferred to the active COM1 position before StreamFlight sees it as the radio frequency currently in use.

COM2

Although StreamFlight can receive the COM2 active frequency from supported simulator telemetry, COM2 is not used by the Live ATC matching system.

For Live ATC, use:

• COM1 ACTIVE

10.6 Matching Your Radio to a Controller

Once StreamFlight has the active COM1 frequency, it compares that frequency with controller information from the selected network.

For example:

VATSIM selected → COM1 tuned to 118.500 → StreamFlight checks VATSIM → Matching controller identified

or:

IVAO selected → COM1 tuned to 118.500 → StreamFlight checks IVAO → Matching controller identified

StreamFlight automatically detects COM1 frequency changes; the user does not enter the controller callsign manually.

Why Position Can Matter

A frequency may be used by more than one controller in different locations.

StreamFlight therefore also has access to the aircraft’s current latitude and longitude during ATC matching.

For VATSIM, this can be used to resolve duplicate-frequency situations by identifying the geographically relevant controller.

This helps avoid identifying a controller operating on the same frequency in an unrelated region.

10.7 Controller Callsign

When StreamFlight identifies a controller, it provides the controller’s network callsign.

Examples may include:

• EGLL_GND
• EGLL_TWR
• LON_CTR

The exact callsign depends on the controller currently operating on the selected network.

Depending on the airport and network, controller identifiers may represent positions such as:

• Delivery
• Ground
• Tower
• Approach
• Departure
• Centre

StreamFlight uses the controller information supplied by the relevant network.

10.8 Controller Frequency

The identified controller frequency is displayed to three decimal places.

For example:

• 118.500

The StreamFlight ATC output combines the controller callsign and frequency using:

CALLSIGN | FREQUENCY

For example:

• EGLL_TWR | 118.500

The same format is written to the user-facing atc_display.txt output file.

10.9 VATSIM CTAF Support

StreamFlight includes additional CTAF support for VATSIM.

CTAF means:

Common Traffic Advisory Frequency

At airports where no suitable live controller is operating, a published CTAF may be used for pilot-to-pilot traffic coordination according to current VATSIM procedures.

How StreamFlight Uses CTAF

StreamFlight first attempts to identify a live controller using the active COM1 frequency.

If no live controller is found and VATSIM is selected, StreamFlight can determine the relevant departure or destination airport and check whether the tuned frequency matches that airport’s published CTAF.

When a match is found, StreamFlight identifies the station as:

CTAF

together with the frequency.

For example:

• CTAF | 123.450

Which Airport Is Checked?

Where both departure and destination airport coordinates are available, StreamFlight determines which of those airports is geographically closer to the aircraft and uses that airport as the relevant CTAF candidate.

This makes CTAF useful around both ends of the flight.

CTAF Is Not a Controller

A CTAF result does not mean an ATC controller is online.

It identifies a published advisory frequency associated with the relevant airport.

IVAO

The published-airport CTAF lookup described here is specifically a VATSIM feature.

It is not applied to IVAO in the same way.

10.10 What Happens When No Controller is Available

There are several legitimate situations where no live controller will be identified.

For example:

• The required ATC position is closed.
• The controller has disconnected.
• The wrong frequency is tuned.
• The frequency is still in standby.
• COM2 rather than COM1 is being used.
• The wrong Network is selected.
• The aircraft is outside the relevant controller area.
• Current network information contains no appropriate controller.

When no usable ATC result exists, StreamFlight clears the Live ATC result and the user-facing ATC output becomes:

• N/A

This is normal behaviour.

• 122.800 Network Fallback

StreamFlight v3.0.0 also recognises 122.800 MHz as a special fallback frequency when Live ATC is active.

When no live controller or VATSIM CTAF has matched and COM1 is tuned to 122.800:

• VATSIM displays ADVISORY
• IVAO displays UNICOM

The current ATC tracker implements these network-specific labels directly.

For example:

• ADVISORY | 122.800

or:

• UNICOM | 122.800

10.11 ATC Information in StreamFlight

Once either VATSIM or IVAO is selected, Live ATC operation is automatic.

The normal workflow is:

Select Network → Tune COM1 → Fly normally → StreamFlight follows frequency changes

There is no need to manually enter:

• Controller callsign
• Controller frequency
• ATC station type

into StreamFlight.

During a typical online flight, the active COM1 frequency may change several times:

Ground → Tower → Departure → Centre → Approach → Tower → Ground

As COM1 changes, StreamFlight can update the associated ATC information.

If the Network selection is changed away from VATSIM or IVAO, Live ATC is immediately no longer applicable and the controller result is cleared.

10.12 ATC Information in Overlays

Live ATC information can be incorporated into StreamFlight’s overlay environment.

This allows a streamer to display the ATC station currently associated with the aircraft’s active COM1 frequency.

For example:

• LON_CTR | 127.825

The selected Network itself is also part of StreamFlight’s wider overlay/output system.

The distinction is:

Network information
Identifies the network or environment selected by the user.

Live ATC information
Identifies the ATC station associated with active COM1, but only when VATSIM or IVAO is selected.

The complete Network selection feature is covered in 10.2 Selecting a Network.

Custom Overlays

Users creating their own overlay can read:

• atc_display.txt

using an OBS Text (GDI+) source with:

Read from file

enabled.

The ATC result can then be combined with other StreamFlight information such as:

• Callsign
• Flight phase
• Altitude
• Speed
• Route
• Network
• ETA

Custom overlays are covered in Chapter 5 — Overlays & Gamer Mode.

10.13 ATC Output File

StreamFlight provides the following user-facing Live ATC output file:

• atc_display.txt

It is stored in the user-selected Output Folder.

When ATC information is available, the format is:

CALLSIGN | FREQUENCY

For example:

EGLL_TWR | 118.500

A VATSIM CTAF result may appear as:

CTAF | 123.450

A 122.800 fallback may appear as:

ADVISORY | 122.800

for VATSIM, or:

UNICOM | 122.800

for IVAO.

When no applicable ATC information exists:

N/A

StreamFlight initializes the file as N/A and updates it when the Live ATC result changes.

The file can be used with:

• OBS
• Streamer.bot
• Other compatible chatbot/automation software
• Custom overlays
• User-created utilities

The full Output Folder reference is provided in Chapter 13 — Output Files & External Integration.

10.14 Live ATC Troubleshooting

If Live ATC does not show the expected station, begin by checking the Network selection.

Live ATC requires:

VATSIM

or:

IVAO

If any other Network option is selected, Live ATC is deliberately disabled.

ATC Shows N/A

Check that:

• VATSIM or IVAO is selected.
• StreamFlight is connected to the simulator.
• COM1 data is being received.
• The required frequency is active on COM1.
• The expected controller is actually online.

N/A is a valid result when no matching station exists.

Correct Frequency Is Entered but No Controller Appears

Confirm the frequency is on:

COM1 ACTIVE

rather than:

COM1 STANDBY

Live ATC does not use the standby frequency.

COM2 Is Tuned

COM2 does not control Live ATC matching.

Move the desired frequency to active COM1.

Wrong Network Is Selected

If you are flying on VATSIM but StreamFlight is set to:

IVAO

StreamFlight will use IVAO information.

If StreamFlight is set to anything other than VATSIM or IVAO, Live ATC is disabled completely.

Controller Has Just Connected or Disconnected

Online controller information is dynamic.

Allow StreamFlight time to receive refreshed network information after a controller opens or closes a position.

Wrong Controller Appears

Check:

• COM1 frequency
• Aircraft position
• Selected Network

Frequencies may be reused geographically. StreamFlight can use aircraft position to help identify the relevant controller where multiple candidates use the same frequency.

VATSIM Airport Has No Controller

If VATSIM is selected and no live controller matches the active frequency, StreamFlight may check the published CTAF for the relevant departure or destination airport.

If the tuned frequency matches, the result will appear as:

CTAF | frequency

122.800 Shows ADVISORY or UNICOM

This is normal.

For the 122.800 fallback:

VATSIM → ADVISORY

IVAO → UNICOM

Neither represents a live controller.

atc_display.txt Does Not Update

Confirm that:

• A valid Output Folder is selected.
• The folder still exists.
• StreamFlight has permission to write to it.
• The Live ATC result has actually changed.

When no ATC information is available, the expected content is:

N/A

OBS ATC Display Does Not Change

If atc_display.txt is updating correctly:

1. Open the OBS Text (GDI+) source.
2. Confirm Read from file is enabled.
3. Confirm the correct atc_display.txt file is selected.
4. Confirm the source is visible in the current scene.

If the text file is updating correctly, StreamFlight’s Live ATC output is functioning and the issue is with the external display configuration.

StreamFlight Does Not Connect Me to ATC

This is expected.

StreamFlight does not provide the network connection or voice communications.

Continue using the appropriate VATSIM or IVAO pilot client for actual online ATC operations.

11. Passenger Manifest & Viewer Check-In

StreamFlight includes a Passenger Manifest system designed to add viewer interaction to a flight.

When a SimBrief flight containing passenger information is loaded, StreamFlight can create a passenger manifest for that flight. Viewers can then be checked in through compatible chatbot or automation software and automatically assigned a seat.

The system can provide:

• Planned passenger capacity
• Viewer check-in
• Automatic seat assignment
• Existing-seat lookup
• Checked-in passenger count
• Remaining seat count
• Persistent passenger assignments
• Automatic detection of a new flight
• A new-flight Check-In Open announcement trigger
• A readable passenger manifest output file
• Integration with Streamer.bot or other compatible chatbot/automation software

11.1 What is the Passenger Manifest?

The Passenger Manifest represents the viewers who have checked in for the currently loaded StreamFlight flight.

For each checked-in viewer, StreamFlight records:

Username + Assigned Seat

For example:

• Viewer01 1A
• Viewer02 1B
• Viewer03 1C

The manifest is associated with the active flight and uses the passenger quantity supplied by SimBrief as its planned capacity.

This allows a streamer to turn the passenger load from the flight plan into an interactive part of the stream.

A typical workflow is:

Load SimBrief Flight → Manifest Created → Check-In Opens → Viewers Check In → Seats Assigned → Manifest Updates

11.2 How a Manifest is Created

The Passenger Manifest is created when StreamFlight successfully retrieves a SimBrief flight that contains passenger information.

StreamFlight uses the retrieved:

• Callsign
• Departure airport
• Destination airport
• Aircraft type
• Passenger count

to initialise the manifest.

For example:

• FLIGHT: BAW123
• ROUTE: EGLL -> EHAM
• AIRCRAFT: B738
• PLANNED PASSENGERS: 164

SimBrief Is Required

The automatic Passenger Manifest feature depends on the SimBrief passenger count.

Entering departure, destination and aircraft information manually does not by itself create an equivalent passenger manifest.

11.3 Passenger Capacity

The maximum number of viewer check-ins is based on the planned passenger count supplied by SimBrief.

For example, if SimBrief reports:

• 156 passengers

the StreamFlight manifest capacity is:

• 156

The manifest then keeps track of:

Capacity
Total planned passengers.

Checked In
Number of viewers who have claimed a seat.

Remaining
Number of seats still available.

For example:

• PLANNED PASSENGERS: 156
• CHECKED IN: 24
• REMAINING: 132

Passenger Capacity Is Not Derived from Aircraft Type

StreamFlight uses the passenger figure from the loaded SimBrief flight rather than assuming a fixed passenger capacity based purely on the aircraft ICAO type.

This allows the planned passenger load to vary between flights using the same aircraft.

11.4 SimBrief Passenger Information

Passenger information is retrieved during the normal Fetch SimBrief Flight Plan process.

When passenger data is available, StreamFlight uses it to initialise the current Passenger Manifest.

The user does not need to manually enter passenger capacity into a separate StreamFlight control.

If the same flight is loaded again, StreamFlight can recognise that it is still the same passenger flight rather than automatically discarding all existing check-ins.

A new manifest is created only when StreamFlight determines that a different flight has been loaded.

This behaviour is explained further in 11.11 Manifest Persistence and 11.12 Starting a New Manifest.

11.5 Viewer Check-In

The most visible use of the Passenger Manifest is viewer check-in.

A streamer can configure a command such as:

• !checkin

in Streamer.bot or another compatible chatbot/automation application.

A viewer might enter:

• !checkin

The automation sends that viewer's username to StreamFlight's Passenger Check-In service.

StreamFlight then:

1. Checks whether an active passenger flight exists.
2. Checks whether the viewer is already on the manifest.
3. Checks whether seats remain available.
4. Assigns the next available seat where appropriate.
5. Stores the passenger.
6. Updates the passenger manifest.

The external chatbot can then use the response returned by StreamFlight to create a suitable chat message.

For example:

@Viewer04 checked in successfully — Seat 4C ✈

The wording of that chat response is controlled by the chatbot configuration, not by StreamFlight itself.

11.6 Automatic Seat Assignment

StreamFlight automatically selects the next available seat when a viewer checks in successfully.

The seat sequence uses six seat letters:

A B C D E F

and progresses through numbered rows.

For example:

1A

1B

1C

1D

1E

1F

...

Each successfully checked-in viewer receives the next available seat in the sequence.

The purpose of the seat assignment is to give each checked-in viewer a unique and persistent position on the current flight.

11.7 Duplicate Check-In

A viewer cannot consume multiple passenger positions simply by entering !checkin repeatedly.

If the username already exists in the current manifest, StreamFlight recognises the existing passenger and returns the seat that was already assigned.

For example:

First request:

• !checkin

Result:

• @Viewer05 checked in — Seat 4C

A later request from the same viewer can return:

• @Viewer05, you are already checked in — Seat 4C

The original seat remains unchanged.

Username matching is handled without requiring exact capitalisation, so variations in username letter case do not create another passenger.

11.8 Full Flights

Once the number of checked-in viewers reaches the planned passenger capacity, no further seats can be assigned.

The Passenger Check-In service reports that the manifest is:

• full

and the remaining seat count becomes:

• 0

A chatbot could convert this into a message such as:

• Sorry @Viewer06 — this flight is fully booked!

The wording is determined by the chatbot configuration.

StreamFlight itself enforces the manifest capacity.

11.9 Checking Your Seat

A separate viewer command can be configured to allow someone to check their existing seat.

For example:

• !seat

The automation asks StreamFlight for the seat associated with the viewer's username.

If the viewer is checked in, the existing seat is returned.

For example:

• @Viewer07 — your seat is 4C.

If the viewer has not checked in, StreamFlight returns a not-checked-in result which the chatbot can turn into a suitable response.

For example:

• @Viewer07, you haven't checked in for this flight yet. Use !checkin.

11.10 Passenger Counts and Remaining Seats

Streamer.bot or another compatible application can also request a summary of the current manifest.

The summary provides:

Capacity
Planned passenger count.

Checked In
Number of viewers currently assigned seats.

Remaining
Number of available passenger positions.

This is useful for a command such as:

• !passengers

A chatbot response might look like:

• Passengers: 43 / 156 checked in — 113 seats remaining.

11.11 Manifest Persistence

Viewer check-ins are not intended to disappear simply because the same flight information is loaded again.

StreamFlight keeps the manifest associated with the current flight.

The flight identity is based on:

Callsign + Departure + Destination

Therefore, if the same flight is reinitialised using the same combination, existing passenger assignments are retained.

Other flight metadata, including aircraft information and capacity, can still be refreshed without automatically removing the existing checked-in passengers.

This allows the manifest to survive normal reloading of the same flight information.

StreamFlight Restart

StreamFlight also maintains its own internal manifest state so that the current passenger list can be recovered rather than existing only while the application remains open.

This internal state is managed automatically by StreamFlight and is not part of the normal user-facing Output Folder reference.

11.12 Starting a New Manifest

A new passenger manifest is created when StreamFlight loads a flight whose identifying information differs from the current passenger flight.

The identity used by the manifest is based on:

Callsign | Departure | Destination

For example:

• BAW123 | EGLL | EHAM

If the next SimBrief flight is:

• BAW456 | EHAM | EGLL

StreamFlight recognises it as a different flight and creates a new empty passenger list.

Existing passengers from the previous flight are therefore not automatically carried into the new flight.

The new SimBrief passenger count becomes the capacity for the new manifest.

Aircraft Type Alone Does Not Define a New Flight

Changing only the aircraft information does not form the primary flight identity.

The manifest is centred on the:

callsign, departure and destination

combination.

11.13 Automatic Check-In Open Announcement

When StreamFlight detects that a new passenger flight has been created, it marks a new-flight announcement as available.

The announcement information contains:

• Callsign
• Departure ICAO
• Destination ICAO

This makes it possible for external automation to produce a message such as:

• ✈ Check-in is now OPEN for BAW123 — EGLL → EHAM! Type !checkin to board.

What Is Automatic?

The distinction is important.

Built into StreamFlight

StreamFlight detects the new passenger flight and makes the announcement information available.

Configured externally

Streamer.bot or another compatible automation application retrieves that information and posts the actual message to Twitch, YouTube or another configured chat.

StreamFlight itself does not log into Twitch or YouTube to post the announcement.

Once the automatic announcement has been retrieved, it is no longer marked as pending.

11.14 Passenger Manifest Output

StreamFlight creates:

in the user-selected Output Folder.

This provides a human-readable version of the active passenger manifest.

An example may look similar to:

• FLIGHT: BAW123
• ROUTE: EGLL -> EHAM
• AIRCRAFT: B738
• PLANNED PASSENGERS: 156
• CHECKED IN: 4
• REMAINING: 152

PASSENGER MANIFEST

------------------

Viewer01 1A

Viewer02 1B

Viewer03 1C

Viewer04 1D

The file is updated as viewers successfully check in.

It can be used for:

• Viewing the current passenger list
• OBS displays
• Streamer.bot integrations
• Other compatible automation software
• Custom utilities
• Post-flight records

The file will be documented again in Chapter 13 — Output Files & External Integration.

11.15 Passenger Check-In Service

StreamFlight v3.0.0 provides a dedicated local Passenger Check-In service.

The service uses:

• Port 38086

The available service paths are:

Viewer-specific requests use a:

user

parameter.

For example:

/checkin?user=Viewer01

Local Service Only

The Passenger Check-In service runs locally on the computer running StreamFlight.

This means that in v3.0.0, the application making the request should normally run on the same computer as StreamFlight.

This is particularly important in dual-PC streaming setups where Streamer.bot may otherwise be running on the streaming PC.

11.16 Streamer.bot Integration

Streamer.bot can act as the bridge between a viewer's chat command and StreamFlight's Passenger Check-In service.

The general flow is:

Viewer sends command → Streamer.bot receives command → Streamer.bot requests information from StreamFlight → StreamFlight returns result → Streamer.bot sends chat response

What StreamFlight Provides

StreamFlight provides:

• Manifest creation
• Passenger capacity
• Duplicate detection
• Seat assignment
• Seat lookup
• Passenger summary
• Full-flight detection
• Manifest persistence
• New-flight announcement trigger
• Passenger Check-In service

What Streamer.bot Provides

Streamer.bot can provide:

• Twitch or YouTube command detection
• Viewer username
• Request to StreamFlight
• Interpretation of the returned result
• Chat response
• Moderator permissions
• Command cooldowns
• Scene-based restrictions
• Automatic announcement workflow

This separation allows the streamer to customise the chat experience without requiring StreamFlight to control the streaming account.

11.17 Creating !checkin

A !checkin command can be created in Streamer.bot to request StreamFlight's:

/checkin

function.

The invoking viewer's username should be supplied as the user value.

Conceptually:

Viewer: !checkin

Streamer.bot:

Send viewer username to StreamFlight

StreamFlight:

Check manifest

Assign or return seat

Return result

Streamer.bot:

Send suitable response to chat

Possible results include:

checked_in
A new passenger was successfully checked in.

already_checked_in
The viewer already has a seat.

full
There are no remaining passenger positions.

no_active_flight
No valid passenger manifest is currently active.

invalid_user
No usable viewer username was supplied.

Streamer.bot can create a different chat response for each result.

11.18 Creating !seat

The !seat command can use:

/seat

to retrieve the seat currently assigned to the invoking viewer.

A typical workflow is:

Viewer: !seat

If checked in:

@Viewer08 — you're sitting in 12A.

If not checked in:

@Viewer08 — you're not checked in yet. Type !checkin.

The same username used by the chat platform should be sent to StreamFlight so that it can locate the passenger.

11.19 Creating !passengers

A !passengers command can use:

/passengers

to obtain the current manifest summary.

No individual viewer username is required for the passenger summary itself.

The returned information includes:

• Capacity
• Checked-in count
• Remaining count

A typical response could be:

✈ 47 of 156 passengers checked in — 109 seats remaining.

The streamer can decide whether this command remains available throughout the whole flight or only during check-in.

11.20 Creating !checkinopen

!checkinopen can be configured as a streamer or moderator convenience command.

For example:

✈ Check-in is OPEN for BAW123 — EGLL → EHAM. Type !checkin to get your seat!

This is separate from StreamFlight's automatic new-flight announcement.

The automatic announcement mechanism provides:

• Callsign
• Departure
• Destination
• Pending announcement state

A Streamer.bot setup can therefore use the automatic announcement when a new flight is loaded while also providing !checkinopen as a manual command to repeat the boarding message.

11.21 Moderator Permissions

The streamer may not want every viewer to trigger administrative passenger messages.

Streamer.bot permissions can therefore be used to separate ordinary viewer commands from management commands.

A sensible arrangement is:

This is only a suggested configuration.

Permissions are controlled by Streamer.bot, not StreamFlight.

The streamer may choose a different arrangement to suit the channel.

11.22 Restricting Commands to the Appropriate OBS Scene

Streamer.bot can also be used to control when passenger commands are available.

For example, a streamer may only want check-in to operate while an:

Airport / Boarding

or:

Pre-Flight

scene is active.

An external automation can check the current OBS scene before allowing the command to proceed.

A possible workflow is:

Viewer uses !checkin

↓

Streamer.bot checks active OBS scene

↓

Correct boarding scene?

↓

YES → Send request to StreamFlight

NO → Ignore or send suitable message

For example:

Check-in is currently closed.

StreamFlight Does Not Control This Restriction

OBS scene awareness, permissions and command availability are all Streamer.bot-side configuration.

StreamFlight simply responds to a valid Passenger Check-In request.

This allows different streamers to create different workflows without forcing a single command policy into StreamFlight.

11.23 Passenger Manifest Troubleshooting

!checkin Does Nothing

Check that:

• A SimBrief flight has been fetched.
• The flight contains passenger information.
• StreamFlight is running.
• Streamer.bot is running.
• Streamer.bot is using port 38086.
• Streamer.bot and StreamFlight are running on the same computer.

No Active Flight

If StreamFlight reports:

no_active_flight

confirm that a SimBrief passenger flight has been loaded.

Simply entering flight details manually is not sufficient to initialise the Passenger Manifest.

Viewer Is Already Checked In

This is normal.

StreamFlight does not assign another passenger position. The viewer's existing seat is returned.

Flight Is Full

The planned passenger capacity has been reached.

No additional viewer seats can be assigned until a new passenger flight is loaded.

Viewer Cannot Find Their Seat

Confirm that the same chat username is being passed to StreamFlight.

If that username is not present in the manifest, StreamFlight reports that the viewer is not checked in.

Passenger Count Looks Wrong

The capacity comes from the passenger count supplied by the current SimBrief flight.

Check the passenger quantity in the SimBrief OFP and fetch the current plan again if necessary.

Previous Passengers Are Still Present

Check the flight information.

If the callsign, departure and destination still identify the same passenger flight, StreamFlight deliberately preserves the existing manifest.

A different flight identity creates a new manifest.

Manifest Reset Unexpectedly

Check whether one of the flight identity fields changed:

• Callsign
• Departure
• Destination

Changing one of these can cause StreamFlight to recognise the loaded SimBrief flight as a new passenger flight.

passenger_manifest.txt Does Not Update

Confirm:

• A valid Output Folder is selected.
• The Output Folder exists.
• StreamFlight can write to it.
• A passenger has successfully checked in.

Automatic Check-In Announcement Does Not Appear in Chat

StreamFlight does not directly post the announcement.

Streamer.bot or another compatible automation system must retrieve the available new-flight announcement and post the message to chat.

Announcement Only Appears Once

This is expected for the automatic announcement.

Once the pending announcement has been retrieved, it is cleared.

Use a separate manual !checkinopen command if moderators need to repeat the boarding announcement later.

Streamer.bot Is Running on the Second PC

The Passenger Check-In service is different from StreamFlight's LAN-enabled Browser Sources.

In v3.0.0, Passenger Check-In runs locally on the StreamFlight computer.

Therefore, a Streamer.bot installation running only on another PC cannot directly access the standard Passenger Check-In service across the LAN.

Commands Work but Chat Wording Is Wrong

The visible chat response is configured in Streamer.bot or the chosen automation application.

Change the chatbot action rather than StreamFlight.

The Passenger Manifest system therefore consists of two complementary parts:

StreamFlight manages the flight, capacity, passengers, seats, manifest, persistence and Passenger Check-In service.

Streamer.bot or other compatible chatbot/automation software turns that information into viewer-facing commands, permissions, announcements and chat responses.

This keeps StreamFlight independent of any particular streaming platform while still providing the data needed for an interactive passenger experience.

12. Live Moving Map

The Live Moving Map provides a real-time graphical view of the aircraft's position during the flight.

The map follows the aircraft as it moves and displays its current heading together with the available flight route. It can be displayed directly on the simulator computer through Gamer Mode or added to compatible streaming software such as OBS / Streamlabs Desktop as a browser source.

The Moving Map controls are located on the Flight Plan tab.

12.1 Enabling the Moving Map

To use the Moving Map:

1. Open the Flight Plan tab.
2. Locate MOVING MAP OVERLAY.
3. Select Enable Moving Map.

Once enabled, StreamFlight makes the Moving Map available for use in Gamer Mode and through its browser source.

The Moving Map requires valid aircraft position data from the connected simulator before it can follow the aircraft.

12.2 Aircraft Position and Heading

While StreamFlight is connected to the simulator, the Moving Map follows the aircraft's current position.

An aircraft symbol is displayed in the centre of the map and rotates according to the aircraft's current heading.

As the flight progresses, the map automatically moves with the aircraft rather than requiring you to manually reposition it.

The aircraft position displayed by the Moving Map is updated approximately once per second.

12.3 Flight Route

The Moving Map can also display the route associated with the current flight.

The route appears as a line on the map, providing a visual indication of the planned journey while the aircraft's current position remains centred on the display.

The amount of route detail available depends on how the flight was loaded into StreamFlight.

12.4 Using a SimBrief Route

When a flight is fetched from SimBrief, StreamFlight can use the waypoint information contained in the SimBrief flight plan to display the planned route on the Moving Map.

This allows the map to show the route through the available flight-plan waypoints rather than simply drawing a direct line between the two airports.

For the most useful route display:

1. Generate the required flight in SimBrief.
2. Open StreamFlight.
3. Select Fetch SimBrief.
4. Confirm that the correct departure and destination have been loaded.
5. Enable the Moving Map.

The Moving Map will then use the available SimBrief route information.

NOTE: The Moving Map displays the route information available to StreamFlight. It is not intended to replace the aircraft's navigation system, flight-management system or simulator flight planner.

12.5 Using the Moving Map Without SimBrief

SimBrief is not required to use the Moving Map.

When a flight is configured manually and StreamFlight has valid coordinates for both the departure and destination airports, the Moving Map can display a direct route between them.

For example, entering:

Departure: EGLL
Destination: EGPH

allows StreamFlight to use its airport information to draw a direct departure-to-destination route.

This provides a useful visual reference for manually configured flights, although it does not represent a detailed en-route flight plan.

12.6 Map Zoom

The Zoom setting controls how closely the Moving Map is centred around the aircraft.

Available values range from:

3 to 16

The default setting is:

8

A lower value displays a wider geographical area around the aircraft.

A higher value provides a closer view of the aircraft and its immediate surroundings.

You can adjust the Zoom value while using the Moving Map. StreamFlight remembers the selected setting for future sessions.

12.7 Showing the Moving Map in Gamer Mode

The Moving Map can be displayed directly on the simulator computer without requiring OBS / Streamlabs Desktop.

To enable this:

1. Select Enable Moving Map.
2. Select Show in Gamer Mode.

The Moving Map will appear as a separate on-screen display while you fly.

This makes the feature useful for users who want a live map available during normal simulator flying as well as for streamers.

12.8 Gamer Map Position

The Gamer Map Alignment controls determine where the Moving Map appears on the selected monitor.

Four positions are available:

• MID LEFT
• MID RIGHT
• BOTTOM LEFT
• BOTTOM RIGHT

Select the required position and StreamFlight moves the Gamer Mode map accordingly.

The monitor itself is determined by the existing Gamer Mode Overlay Position setting:

• DEFAULT
• LEFT
• CENTRE
• RIGHT

This means the monitor and the position of the map on that monitor can be controlled separately.

For example, with a multi-monitor setup you could select the RIGHT monitor and then position the Moving Map at BOTTOM LEFT on that screen.

StreamFlight remembers the selected Moving Map position.

12.9 Moving Map Browser Source

StreamFlight provides a dedicated browser source for the Moving Map.

The address is displayed in the MOVING MAP OVERLAY section:

Rather than entering the address manually, select:

COPY

StreamFlight copies the Moving Map browser-source address to the Windows clipboard.

You can then paste it into OBS / Streamlabs Desktop or another compatible application.

IMPORTANT: In StreamFlight v3.0.0, the Moving Map browser source is available on the same computer running StreamFlight. It is not exposed through the Dual-PC / LAN Mode used by some of StreamFlight's other browser sources.

12.10 Adding the Moving Map to OBS / Streamlabs Desktop

To display the Moving Map in OBS / Streamlabs Desktop:

1. Make sure Enable Moving Map is selected in StreamFlight.
2. Select COPY beside the Moving Map Browser Source.
3. Open OBS / Streamlabs Desktop.
4. Add a new Browser Source.
5. Paste the copied address into the URL field.
6. Set the browser source to the required size.
7. Position it within your stream layout.

The browser source will then display the live Moving Map while StreamFlight is running and receiving simulator position data.

Because the Moving Map is supplied as a browser source, you can resize and position it independently from StreamFlight's other overlays.

NOTE: If OBS / Streamlabs Desktop is running on a separate streaming PC, the Moving Map browser source cannot be accessed directly from that computer in StreamFlight v3.0.0.

12.11 Internet and Map Requirements

The Moving Map obtains its map display from online mapping services.

An active internet connection is therefore required for the map itself to load correctly.

StreamFlight must also be running because the aircraft position, heading, route and Moving Map settings are supplied by StreamFlight.

The Gamer Mode Moving Map uses the Microsoft WebView2 component to display the map within its on-screen window.

12.12 Moving Map Troubleshooting

The Map Does Not Appear

Check that:

• Enable Moving Map is selected.
• StreamFlight is running.
• A supported simulator is connected.
• StreamFlight is receiving valid aircraft position data.
• The computer has an active internet connection.

The Gamer Mode Map Does Not Appear

Check that both:

Enable Moving Map

and:

Show in Gamer Mode

are selected.

Also check the selected Gamer Mode monitor and Gamer Map Alignment. On a multi-monitor system, the map may be appearing on a different display.

The Aircraft Does Not Move

The Moving Map requires live latitude, longitude and heading information from the simulator.

Confirm that StreamFlight has successfully detected the simulator and that normal telemetry is updating.

The Route Does Not Appear

If using SimBrief, confirm that the correct flight has been generated and fetched into StreamFlight.

If the flight was entered manually, make sure valid four-character departure and destination ICAO codes have been entered and recognised by StreamFlight.

A manually configured flight normally displays a direct departure-to-destination route rather than the detailed waypoint route available from SimBrief.

The Browser Source Does Not Appear

Confirm that StreamFlight is running and Enable Moving Map is selected.

Use the COPY button in StreamFlight rather than manually entering the address.

The Moving Map uses:

Port 38088

If another application is already using that port, the Moving Map browser source may be unable to start correctly.

The Map Background Does Not Load

Check the computer's internet connection.

The geographical map itself is loaded from an online map service, so simulator telemetry may be available even when the map background cannot be retrieved.

Moving Map on a Dual-PC Setup

In StreamFlight v3.0.0, the Moving Map service uses the local computer only.

If StreamFlight is running on the simulator PC and OBS / Streamlabs Desktop is running on a separate streaming PC, the Moving Map browser source is not available across the LAN in the same way as StreamFlight's supported Dual-PC browser sources.

13. Flight Information Display System (FIDS)

13.1 What is FIDS?

Introduced in StreamFlight 3.1.5, the Flight Information Display System (FIDS) provides airport-style Departures and Arrivals boards for flight simulation streams.

FIDS integrates with live VATSIM and IVAO network traffic, displaying flight information for your departure and destination airports.

Your own flight is highlighted, and StreamFlight automatically controls which board is visible as your flight progresses.

FIDS is compatible with both Normal Mode and Gamer Mode.

13.2 Accessing the FIDS Tab

Open StreamFlight and select the FIDS tab.

The FIDS interface provides access to the Departures and Arrivals display functionality, including the configurable arrival activation distance.

The default arrival activation distance is 100 nautical miles (NM) and can be adjusted between 20 and 500 NM.

13.3 Departures Board

The Departures Board displays your flight alongside available departing traffic at your departure airport.

The board automatically:

• Activates when a new flight plan is registered.
• Remains visible during PREFLIGHT, TAXI OUT and TAKEOFF.
• Disappears when the aircraft enters CLIMB.

A new flight plan must be registered before the Departures Board becomes active again.

13.4 Arrivals Board

The Arrivals Board displays your flight alongside available incoming traffic at your destination airport.

The board automatically:

• Activates when your aircraft is airborne and within the configured arrival distance.
• Supports activation during APPROACH.
• Displays available incoming flights ordered by estimated arrival time.
• Highlights your own flight.
• Disappears when your flight is completed.

Incoming network aircraft within approximately 40 NM of their destination are classified as ARRIVING.

13.5 Live VATSIM and IVAO Traffic

FIDS supports live traffic information from both VATSIM and IVAO.

Select your preferred network in StreamFlight.

When traffic information is available, FIDS displays airport activity including flight numbers, destinations or origins, estimated times and flight status.

Network information refreshes approximately every 60 seconds.

NOTE: You do not need to be connected as a VATSIM or IVAO pilot to display publicly available network traffic.

13.6 Flight Plan Requirements

FIDS requires three pieces of flight information:

• Callsign
• Departure airport ICAO code
• Destination airport ICAO code

This information can be supplied using either of the following methods.

SimBrief

Open the Flight Plan tab and fetch your SimBrief flight plan. FIDS automatically receives the relevant flight information.

Manual Entry

Enter your callsign, departure airport and destination airport directly into StreamFlight.

Once the required information is available and a new flight plan is registered, FIDS can activate the appropriate board.

13.7 Adding FIDS to OBS Studio

StreamFlight automatically generates two HTML files in its FIDS folder:

• FidsDepartures.html
• FidsArrivals.html

Each file is added to OBS as a separate Browser Source using the Local file option.

Step 1 — Add the Departures Board

1. Open OBS Studio and select your scene.
2. Under Sources, click + → Browser.
3. Name the source StreamFlight FIDS - Departures.
4. Enable Local file.
5. Browse to FidsDepartures.html in your StreamFlight FIDS folder.
6. Set Width to 350.
7. Set Height to 300.
8. Enable Refresh browser when scene becomes active.
9. Click OK.

Step 2 — Add the Arrivals Board

1. Open OBS Studio and select your scene.
2. Under Sources, click + → Browser.
3. Name the source StreamFlight FIDS - Arrivals.
4. Enable Local file.
5. Browse to FidsArrivals.html in your StreamFlight FIDS folder.
6. Set Width to 350.
7. Set Height to 300.
8. Enable Refresh browser when scene becomes active.
9. Click OK.

Step 3 — Position the Boards

Position both Browser Sources in your OBS scene.

Both boards can occupy exactly the same position.

Keep both Browser Sources enabled. StreamFlight automatically controls their visibility by making inactive boards transparent.

There is no need to manually switch between the Departures and Arrivals sources during a flight.

IMPORTANT: FIDS uses local HTML files. Do not enter an HTTP address in the Browser Source URL field.

13.8 FIDS in Gamer Mode

FIDS is fully compatible with StreamFlight Gamer Mode.

13.9 Automatic Board Visibility

FIDS follows the progress of your flight without requiring manual intervention.

Inactive boards remain transparent in OBS.

13.10 FIDS Troubleshooting

Departures Board not appearing

Check that a valid callsign, departure airport and destination airport have been registered. Confirm that the flight is in the appropriate departure phase.

Arrivals Board not appearing

Check your arrival activation distance, current distance to destination and flight phase.

No VATSIM or IVAO traffic

Confirm that the correct network is selected and that an internet connection is available. Traffic will only appear when suitable network information is available.

OBS Browser Source is blank

Check that the Browser Source is configured as a Local file and points to the correct HTML file in the StreamFlight FIDS folder. Also confirm whether the board is currently supposed to be visible.

OBS board not updating

Ensure StreamFlight is running, both Browser Sources remain enabled, and Refresh browser when scene becomes active is selected.

NOTE: FIDS automatically manages board visibility. A transparent board does not necessarily indicate a problem.

14. Output Files & External Integration

StreamFlight can make flight information and simulator data available to other applications through a user-selected Output Folder.

The folder contains simple text files that are automatically maintained by StreamFlight. These can be used to create custom displays, chat commands, automation and other integrations.

Common uses include:

• Custom OBS / Streamlabs Desktop overlays
• Streamer.bot commands and actions
• Other compatible chatbot/automation software
• Custom applications and utilities

14.1 Understanding the Output Folder

The Output Folder is the location where StreamFlight stores information that can be used by other applications.

For example:

or:

Once the folder has been selected, StreamFlight creates the required files and keeps their contents updated.

Typical files include:

• callsign.txt
• altitude.txt
• flight_phase.txt
• network.txt
• atc_display.txt
• landingrate.txt

Most contain a single piece of information.

For example:

callsign.txt, might contain:

• BAW123

while:

• flight_phase.txt

might contain:

• CRUISE

Other applications can read these files and use the information without having to communicate directly with the flight simulator.

14.2 Selecting or Changing the Output Folder

The Output Folder is configured from the User Settings tab.

Select:

Browse

and choose the folder StreamFlight should use.

If you want the output files stored alongside StreamFlight, create a separate subfolder.

For example:

• C:\StreamFlight\Output

Alternatively, use a completely separate location such as:

• Documents\StreamFlight Output

Changing the Output Folder

The Output Folder can be changed later if required.

Remember that external applications may still be looking at files in the previous location.

For example, if an OBS Text source reads:

• C:\Old StreamFlight Output\callsign.txt

and the StreamFlight Output Folder is moved, the OBS source must also be changed to point to the new file.

The same applies to Streamer.bot and other external integrations.

14.3 Using StreamFlight Output Files

StreamFlight output files are designed to be simple.

StreamFlight writes the information and the external application reads it.

The basic relationship is:

Simulator / Flight Plan → StreamFlight → Output Folder → External Application

There is normally no need to edit the files manually.

For example, if an OBS overlay needs the current callsign, it can read:

• callsign.txt

If a Streamer.bot command needs the route, it can read:

• flightplan.txt

If another application needs the current flight phase, it can read:

• flight_phase.txt

StreamFlight keeps the relevant values updated as the flight progresses.

14.4 Flight Information Files

StreamFlight provides individual output files for the main details of the current flight.

These include information such as:

• Aircraft type
• Callsign
• Departure airport
• Destination airport
• Departure and destination city
• Destination coordinates
• Cruise altitude
• Flight route

Common examples include:

• aircrafttype.txt
• callsign.txt
• departureicao.txt
• destinationicao.txt
• cruise_altitude.txt
• flightplan.txt

The filenames are deliberately descriptive, making it straightforward to identify the information required for an overlay or external integration.

Flight information and SimBrief are covered fully in Chapter 3 — Flight Planning & SimBrief.

14.5 Telemetry Files

Live simulator information is also available through individual telemetry files.

These include:

• Altitude
• Speed
• Heading
• Vertical speed
• Outside air temperature
• Wind
• Aircraft latitude and longitude
• Distance to destination
• ETE
• ETA

Common examples include:

• altitude.txt
• speed.txt
• heading_magnetic.txt
• vspeed.txt
• wind.txt
• dtg_destination.txt
• ete.txt
• eta.txt

These values are automatically updated as StreamFlight receives and processes simulator information.

The meaning and behaviour of the telemetry itself is covered in Chapter 4 — Flight Telemetry & Flight Progress.

14.6 Weather Files

When a SimBrief flight is fetched, StreamFlight can provide the departure and destination METAR through:

• departure_metar.txt

and:

• destination_metar.txt

These contain the weather information retrieved with the SimBrief flight.

SimBrief weather is covered in Chapter 3 — Flight Planning & SimBrief.

14.7 Flight Progress and Phase Files

One of the most useful output files for external automation is:

It contains the current StreamFlight flight phase.

For example:

• PREFLIGHT
• TAXI OUT
• CLIMB
• CRUISE

or:

• APPROACH

This can be useful for custom overlays and automation that should respond to different stages of a flight.

For example, Streamer.bot or another compatible automation application could perform an action when the flight enters TAKEOFF, CRUISE or LANDING.

Flight Progress Bar

Users wishing to display StreamFlight's normal visual flight-progress bar should use the supplied browser-source progress display.

There is no need to work with StreamFlight's internal progress calculation files.

Flight progress and automatic phase detection are covered in Chapter 4 — Flight Telemetry & Flight Progress.

14.8 ATC Output

Live ATC information is available through:

• atc_display.txt

When a controller is identified, this contains the controller callsign and frequency.

For example:

• EGLL_TWR | 118.500

Depending on the current VATSIM or IVAO situation, it may also contain information such as:

• CTAF | 123.450

or:

• ADVISORY | 122.800

When there is no applicable Live ATC information:

• N/A

This makes atc_display.txt useful for custom ATC displays without requiring the external application to communicate directly with VATSIM or IVAO.

Live ATC is covered fully in Chapter 10 — Live ATC: VATSIM & IVAO.

14.9 Landing Rate Output

The Landing Rate feature provides three useful output files:

• landingrate.txt

Contains the detected landing rate.

• landingrate_classification.txt

Contains the corresponding StreamFlight classification, such as:

GOOD LANDING

• landingrate_message.txt

Provides a prepared landing-rate result that can be useful for external integrations.

These files can be used with custom overlays, Streamer.bot or other compatible chatbot/automation software.

Landing Rate behaviour and classifications are covered fully in Chapter 9 — Landing Rate.

14.10 Passenger Manifest Output

The Passenger Manifest provides:

Unlike most StreamFlight output files, this contains several lines of information.

It includes details such as:

• Flight
• Route
• Aircraft
• Planned passengers
• Checked-in passengers
• Remaining seats
• Viewer usernames
• Assigned seats

For example:

• FLIGHT: BAW123
• ROUTE: EGLL -> EHAM
• AIRCRAFT: B738
• PLANNED PASSENGERS: 156
• CHECKED IN: 4
• REMAINING: 152

PASSENGER MANIFEST

------------------

Viewer01 1A

Viewer02 1B

Viewer03 1C

Viewer04 1D

The file updates as viewers successfully check in.

Passenger check-in is covered fully in Chapter 11 — Passenger Manifest & Viewer Check-In.

14.11 Using Output Files with OBS

Output files provide a simple way to create completely custom flight overlays in OBS.

OBS can read a StreamFlight text file using a:

Text (GDI+)

source.

Create a Text (GDI+) source and enable:

Read from file

Then select the required StreamFlight output file.

For example:

• callsign.txt

If the file contains:

• BAW123

the OBS source displays:

• BAW123

When StreamFlight updates the file, the displayed information can update automatically.

Creating a Custom Overlay

Multiple Text (GDI+) sources can be combined to create a completely custom flight display.

For example, an overlay could use:

• callsign.txt
• departureicao.txt
• destinationicao.txt
• altitude.txt
• speed.txt
• eta.txt
• flight_phase.txt

OBS remains responsible for the visual design, including:

• Fonts
• Size
• Position
• Background graphics
• Animations
• Scene composition

StreamFlight supplies the data.

This allows users to create overlays that look completely different from StreamFlight's built-in Gamer Mode templates.

Custom overlays are also covered in Chapter 5 — Overlays & Gamer Mode.

14.12 Using Output Files with Streamer.bot

Streamer.bot can use StreamFlight output files as part of commands and automation.

For example, a custom:

• !flight

command could use the current callsign, aircraft, route and flight phase to produce a message such as:

• BAW123 | B738 | EGLL → EHAM | Currently CRUISE

A:

• !route

command could read:

• flightplan.txt

A landing result could use:

• landingrate_message.txt

And flight-phase information could be used as part of automated actions.

For example, an action might occur when the current phase becomes:

• TAKEOFF

or:

• LANDING

The exact commands, actions and responses are configured in Streamer.bot.

14.13 Using Output Files with Other Applications

StreamFlight output files are not limited to OBS or Streamer.bot.

Any application capable of reading ordinary text files can potentially use the information.

Examples include:

• Custom dashboards
• Desktop displays
• Automation tools
• Hardware-display software
• User-created utilities
• Custom streaming applications

Because the files are standard text files, the external application does not need to understand how StreamFlight communicates with the simulator.

It simply reads the information it requires from the Output Folder.

14.14 File Update Behaviour

StreamFlight automatically updates output files when the corresponding information changes.

Some values, such as altitude, speed and position, may change frequently during a flight.

Other information, such as callsign, departure, destination and route, normally changes only when the flight information changes.

Feature-specific information updates when appropriate. For example, landing-rate files update following a landing result, while the passenger manifest changes as viewers check in.

Users normally do not need to manage these updates themselves.

14.15 N/A, ----, 00:00 and Other Default Values

Some output files exist even when the corresponding information is not currently available.

StreamFlight therefore uses several simple default values.

N/A

Usually means that the information is not currently available.

For example:

• N/A

in atc_display.txt means there is currently no applicable Live ATC result.

• ----

Used for some fields where no applicable identifier or selection is currently available.

For example, departure or destination information may initially appear as:

----

00:00

May be used when no valid ETE is currently being calculated.

00:00z

May be used when no valid ETA is currently being calculated.

These values are normal, particularly before a flight has started or before StreamFlight has received the information required to calculate a result.

PREFLIGHT

flight_phase.txt normally begins with:

PREFLIGHT

because PREFLIGHT is a valid StreamFlight flight phase.

OFFLINE

network.txt may contain:

OFFLINE

when OFFLINE is the selected Network.

14.16 Output Folder Troubleshooting

No Output Files Are Being Created

Confirm that a valid Output Folder has been selected under:

User Settings

Also confirm that the folder still exists and that StreamFlight has permission to write to it.

StreamFlight Rejects the Folder

Do not select the main StreamFlight application folder itself.

Choose another folder or create a separate subfolder such as:

• C:\StreamFlight\Output

Files Contain N/A

This does not necessarily indicate a problem.

N/A normally means that StreamFlight does not currently have applicable information for that particular output.

For simulator telemetry, confirm that the simulator is running and has been detected by StreamFlight.

For feature-specific information, confirm that the corresponding feature has the information it requires.

OBS Shows Old Information

Open the actual output file in Windows.

If the file contains the correct current value, StreamFlight is updating correctly and the OBS configuration should be checked.

Confirm that:

1. Read from file is enabled.
2. The correct file has been selected.
3. OBS is pointing to the current StreamFlight Output Folder.
4. The source is visible in the active scene.

Output Files Stopped Updating After Changing the Folder

External applications do not automatically follow the StreamFlight Output Folder if it is moved.

Update any:

• OBS Text (GDI+) sources
• Streamer.bot actions
• Other automation
• Custom applications

that still reference the previous folder.

Live ATC Shows N/A

Remember that Live ATC operates only when the selected Network is:

VATSIM

or:

IVAO

A suitable active COM1 result must also be available.

See Chapter 10 — Live ATC: VATSIM & IVAO.

Landing Rate Information Is Missing

Landing-rate information becomes available when the Landing Rate feature produces a landing result or when its test function is used.

See Chapter 9 — Landing Rate.

Passenger Manifest Is Missing

The Passenger Manifest is associated with the SimBrief passenger workflow.

Confirm that a suitable SimBrief flight containing passenger information has been loaded.

See Chapter 11 — Passenger Manifest & Viewer Check-In.

The Output Folder provides a simple way to take information already being processed by StreamFlight and use it elsewhere.

StreamFlight handles the simulator connection, flight information and calculations. OBS, Streamer.bot and other compatible applications can then use the resulting output to create custom displays, commands and automation.

For users who require a detailed list of individual output filenames, the complete reference is provided in Appendix 15.7 — Output File Reference.

15. User Settings & X-Plane Configuration

The User Settings tab contains StreamFlight's general application settings together with the configuration required for X-Plane 11 and X-Plane 12.

For most users, these settings only need to be configured once. StreamFlight remembers the relevant preferences for future sessions.

15.1 User Settings Tab

Open the:

⚙ User Settings

tab to access StreamFlight's general configuration options.

The tab is primarily used for:

• Selecting the StreamFlight Output Folder
• Configuring X-Plane support
• Checking XPUIPC configuration status
• Accessing StreamFlight licence information

Settings relating specifically to overlays, such as Network, MSFS Server and dual-PC Browser Source options, are located on the Overlays tab and are covered in Chapter 5 — Overlays & Gamer Mode.

15.2 Output Folder

The Output Folder is the location where StreamFlight creates the user-accessible files used by OBS, Streamer.bot and other external applications.

Select:

Browse

to choose the folder.

A suitable location might be:

• C:\StreamFlight\Output

or:

• Documents\StreamFlight Output

Once configured, StreamFlight remembers the selected location.

The Output Folder and its contents are covered fully in Chapter 13 — Output Files & External Integration.

15.3 X-Plane Configuration

StreamFlight supports:

X-Plane 11

and:

X-Plane 12

through XPUIPC.

Unlike Microsoft Flight Simulator, which communicates with StreamFlight through SimConnect, X-Plane requires the XPUIPC plugin to provide the simulator information required by StreamFlight.

The User Settings tab therefore provides an X-Plane installation path together with a configuration

The status helps identify whether X-Plane is ready for use with StreamFlight.

Possible statuses include:

Not Set

No X-Plane installation path has been configured.

Invalid Path

The selected folder does not appear to be a valid X-Plane installation.

Missing XPUIPC

StreamFlight has found the X-Plane installation, but the required XPUIPC plugin has not been detected.

Restart X-PLANE

A plugin or configuration change has been made and X-Plane needs to be restarted.

Ready

The X-Plane installation and required XPUIPC components have been detected successfully.

When the status shows:

Ready

no further X-Plane configuration should normally be required.

15.4 Selecting the X-Plane Installation Path

StreamFlight needs to know where X-Plane is installed.

Use the X-Plane Browse control and select the main X-Plane installation folder.

For example:

• C:\X-Plane 12

The selected location should be the main X-Plane folder rather than one of its subfolders.

Do not select:

• C:\X-Plane 12\Resources

or:

• C:\X-Plane 12\Resources\plugins

StreamFlight checks the selected location to determine whether it appears to be a valid X-Plane installation.

If the wrong folder has been selected, the status may show:

Invalid Path

Select the correct X-Plane installation folder and StreamFlight will check the configuration again.

15.5 Installing XPUIPC

XPUIPC is required for StreamFlight to communicate with X-Plane 11 and X-Plane 12.

If StreamFlight cannot find the plugin, the X-Plane configuration status displays:

Missing XPUIPC

StreamFlight includes the required XPUIPC files with its distribution.

To install XPUIPC:

1. Open the main StreamFlight folder.
2. Open the supplied XPUIPC folder.
3. Copy its contents.
4. Open the X-Plane installation folder.
5. Open:

Resources\plugins

1. Paste the supplied XPUIPC files into the plugins folder.
2. Restart X-Plane.

For example, if X-Plane is installed at:

• C:\X-Plane 12

the plugin destination will be:

• C:\X-Plane 12\Resources\plugins

If X-Plane was running while XPUIPC was installed, it must be restarted before the newly installed plugin can be loaded.

15.6 StreamFlight XPUIPC Configuration

XPUIPC requires certain configuration information so that StreamFlight can receive the simulator data it needs.

StreamFlight checks the XPUIPC configuration and can apply the required configuration automatically.

Users therefore do not normally need to manually edit XPUIPC configuration files.

If StreamFlight makes a configuration change while X-Plane is already running, the User Settings tab may display:

Restart X-PLANE

This indicates that the configuration has been prepared, but X-Plane needs to reload XPUIPC before the changes become active.

15.7 Restarting X-Plane After Configuration

X-Plane loads its plugins and their configuration when the simulator starts.

For this reason, installing XPUIPC or changing its configuration may require X-Plane to be restarted.

If StreamFlight displays:

Restart X-PLANE

close X-Plane completely and then start it again.

After X-Plane restarts, return to the User Settings tab and check the X-Plane status.

A correctly configured installation should show:

Ready

Typical First-Time X-Plane Setup

The normal first-time setup is:

Select X-Plane Installation Folder → Install XPUIPC if Required → Restart X-Plane → Ready

Once the status shows Ready, this setup does not normally need to be repeated before each flight.

If the status continues to show Invalid Path, Missing XPUIPC or Restart X-PLANE, see Chapter 15 — Troubleshooting.

15.8 Saved Preferences

StreamFlight remembers relevant user settings so that the application does not need to be reconfigured every time it starts.

This includes settings such as the selected Output Folder and X-Plane installation location, together with preferences used by other StreamFlight features.

Settings for features such as Gamer Mode, Camera Control and RAAS are also retained where applicable.

Users do not normally need to locate, open or edit StreamFlight's internal configuration files.

15.9 About / Licence

The User Settings tab provides access to:

ABOUT / LICENCE

This opens the StreamFlight licence information window.

The window provides information about the installed StreamFlight version and current licence.

Information displayed may include:

• Product
• Application version
• Licence ID
• Customer
• Email
• Licence version
• Licence status

The available licence controls include:

TRANSFER LICENCE

Used when moving StreamFlight to another computer.

DEACTIVATE LICENCE

Deactivates StreamFlight on the current computer.

CLOSE

Closes the Licence Information window.

Transferring StreamFlight

If StreamFlight is being moved to another computer, select:

TRANSFER LICENCE

and follow the instructions provided by StreamFlight.

After the current installation has been released, StreamFlight can be installed and activated on the new computer using the original licence information.

Deactivating StreamFlight

Select:

DEACTIVATE LICENCE

when you want to deactivate the licence on the current computer.

StreamFlight asks for confirmation before proceeding.

After deactivation, the application will require activation before it can be used again on that computer.

Installation, activation, deactivation and licence transfer are covered in more detail in Chapter 2 — Installation, Licensing & First Launch.

The User Settings tab is intentionally straightforward. For most users, the Output Folder is the only general setting that needs to be configured, while X-Plane users also need to establish the X-Plane installation path and ensure that XPUIPC reports Ready.

Other operational settings remain with the features to which they belong—for example, Network and MSFS Server selection on the Overlays tab—rather than being part of User Settings.

16. Troubleshooting

StreamFlight is designed to detect supported simulators and manage most connections automatically. If something does not work as expected, the cause can often be identified by checking a few basic items before changing any configuration.

This chapter covers the most common problems that may occur when using StreamFlight.

16.1 StreamFlight Does Not Detect the Simulator

If StreamFlight does not detect the simulator:

1. Confirm that the simulator is running.
2. Allow the simulator to finish loading.
3. Load into an aircraft.
4. Leave StreamFlight running for several seconds while it attempts to establish the connection.

StreamFlight supports:

• Microsoft Flight Simulator 2020
• Microsoft Flight Simulator 2024
• X-Plane 11
• X-Plane 12
• Prepar3D

There is no simulator selector that normally needs to be changed before each flight.

If the simulator is still not detected, continue with the simulator-specific sections below.

16.2 MSFS Connection Problems

Microsoft Flight Simulator 2020 and 2024 communicate with StreamFlight through SimConnect.

If MSFS is running but StreamFlight does not connect:

• Confirm that MSFS has fully loaded.
• Load an aircraft into a flight.
• Allow StreamFlight several seconds to establish the connection.
• Restart StreamFlight if necessary.
• If the problem continues, restart MSFS and StreamFlight.

StreamFlight does not require installation into the MSFS Community folder.

16.3 X-Plane Connection Problems

X-Plane 11 and X-Plane 12 require XPUIPC.

If StreamFlight does not receive information from X-Plane, open:

⚙ User Settings

and check the X-Plane configuration status.

A correctly configured installation should show:

Ready

If another status is displayed, use the appropriate section below.

16.4 XPUIPC Not Found

If the User Settings tab displays:

Missing XPUIPC

StreamFlight has found the X-Plane installation but cannot find the required XPUIPC plugin.

To install it:

1. Open the StreamFlight folder.
2. Open the supplied XPUIPC folder.
3. Copy its contents.
4. Open the X-Plane installation folder.
5. Open:

Resources\plugins

1. Paste the XPUIPC files into the plugins folder.
2. Restart X-Plane.

For example:

After restarting X-Plane, check the status again.

It should show:

Ready

See Chapter 14 — User Settings & X-Plane Configuration for the complete setup procedure.

16.5 XPUIPC Configuration Problems

The X-Plane configuration area may display several different statuses.

Not Set means an X-Plane installation folder has not yet been selected.

Invalid Path means the selected location does not appear to be the main X-Plane installation folder. Select the X-Plane root folder rather than Resources or Resources\plugins.

Missing XPUIPC means the X-Plane installation has been found but the required plugin is missing.

Restart X-PLANE means StreamFlight has detected a change that requires X-Plane to reload XPUIPC. Close X-Plane completely and restart it.

Ready means the required X-Plane configuration has been detected successfully.

16.6 Prepar3D / FSUIPC Problems

StreamFlight communicates with Prepar3D through FSUIPC6.

If Prepar3D is running but StreamFlight does not connect:

• Confirm that FSUIPC6 is installed.
• Confirm that FSUIPC6 is available within Prepar3D.
• Load into an aircraft before testing the StreamFlight connection.
• Restart Prepar3D and StreamFlight if necessary.

16.7 SimBrief Cannot Fetch a Flight

If Fetch SimBrief does not retrieve the expected flight:

• Confirm that a valid SimBrief Pilot ID has been entered.
• Confirm that a flight has been generated in SimBrief.
• Confirm that the computer has an Internet connection.
• Confirm that a valid StreamFlight Output Folder has been selected.
• Try fetching the flight again.

Remember that the Pilot ID is the numeric SimBrief identifier used by StreamFlight.

If a newly generated flight is not returned immediately, confirm that the flight has actually been generated and saved by SimBrief before trying again.

See Chapter 3 — Flight Planning & SimBrief.

16.8 Incorrect or Missing Flight Information

If the aircraft, callsign, departure, destination or other flight information is missing, first determine how the flight was entered.

If using SimBrief, fetch the flight again and confirm that the expected information appears in StreamFlight.

If entering information manually, check the fields on the Flight Plan tab.

For airport information, use valid ICAO identifiers.

Values such as:

----

or:

N/A

may simply indicate that the information is not currently available.

16.9 Telemetry Not Updating

If altitude, speed, heading, vertical speed or other telemetry appears frozen:

1. Confirm that the simulator is still running.
2. Confirm that StreamFlight has detected the simulator.
3. Check whether other telemetry values are changing.
4. Allow a few seconds for StreamFlight to reconnect if the simulator connection was temporarily interrupted.

If all telemetry has stopped, the problem is more likely to be the simulator connection than an individual telemetry value.

For X-Plane, also confirm that the User Settings status shows:

Ready

16.10 Flight Phase Problems

StreamFlight automatically determines the current stage of flight.

Normal phases include:

PREFLIGHT

TAXI OUT

TAKEOFF

CLIMB

CRUISE

DESCENT

APPROACH

LANDING

TAXI IN

Phase changes depend on simulator information and the progress of the flight.

If the automatic phase is temporarily incorrect, allow StreamFlight time to receive and process the current simulator state.

Starting StreamFlight Mid-Flight

If StreamFlight is started or restarted while already airborne, it may take several seconds to reconstruct the current flight state.

This is normal.

Manual Phase Override

If necessary, the flight phase can be overridden using the controls provided by StreamFlight.

Remember that a manual override may affect features that use the current flight phase.

See Chapter 4 — Flight Telemetry & Flight Progress.

16.11 Progress Bar Problems

If the flight progress bar does not appear correct, first confirm that the departure and destination information is correct.

When available, StreamFlight can also use flight-plan information to establish the planned journey and track progress.

If StreamFlight is restarted during a flight, it attempts to reconstruct the existing flight rather than automatically treating the current aircraft position as the beginning of a new flight.

Circuits, Touch-and-Go Flights and Re-Departures

Some flights do not follow the normal pattern of:

PREFLIGHT → Departure → Arrival → Engines Off

For example:

• Circuits
• Touch-and-go training
• Multiple departures without shutting down
• Repositioning and immediately departing again

If a new flight needs to begin without the normal end-of-flight reset, use:

Reset Progress Bar + Flight Phase

This gives StreamFlight a clean starting state for the next flight.

See Chapter 4 — Flight Telemetry & Flight Progress.

16.12 Gamer Mode Problems

If Gamer Mode does not appear:

• Confirm that Gamer Mode is enabled.
• Confirm that the required template has been selected.
• Confirm that StreamFlight is connected to the simulator.
• Check the selected Gamer Mode position.
• If using a separate display, confirm that the StreamFlight window or Gamer Mode display has not opened somewhere unexpected.

If the display appears but information is missing, check whether the corresponding information is available in StreamFlight itself.

For example, missing route or airport information may indicate a flight-plan issue rather than a Gamer Mode problem.

See Chapter 5 — Overlays & Gamer Mode.

16.13 OBS Browser Source Not Displaying

If a StreamFlight Browser Source does not appear in OBS / Streamlabs Desktop, first use the COPY function in StreamFlight to obtain the correct Browser Source address.

Then confirm that the address has been entered correctly into the Browser Source.

Also check that:

• StreamFlight is running.
• The appropriate StreamFlight feature is enabled.
• The Browser Source is visible in the current scene.
• The Browser Source dimensions are appropriate.
• The correct computer address is being used for a dual-PC setup.

If necessary, refresh the Browser Source.

16.14 Browser Source Port Conflicts

StreamFlight normally uses:

If a primary port is already in use, StreamFlight can use its corresponding fallback port.

For this reason, use the Browser Source address provided by StreamFlight rather than assuming that a particular port is active.

If a Browser Source stops working after another application has been installed or started, copy the Browser Source address from StreamFlight again and update the source if necessary.

16.15 Dual-PC / LAN Problems

In a dual-PC setup, StreamFlight runs on the simulator PC and OBS / Streamlabs Desktop can run on the streaming PC.

If the Browser Source works on the simulator PC but not the streaming PC, check:

• Both computers are connected to the same local network.
• The LAN Browser Source address from StreamFlight is being used.
• StreamFlight is running on the simulator PC.
• Windows Firewall or other security software is not blocking the connection.
• The streaming PC can communicate with the simulator PC over the local network.

Do not use a local-only address intended for the simulator PC when the Browser Source is being opened from another computer.

See Chapter 5 — Overlays & Gamer Mode for dual-PC setup.

16.16 Control Input Display Problems

The Control Input Display is available for:

Microsoft Flight Simulator 2020 / 2024

If it does not respond:

• Confirm that StreamFlight is connected to MSFS.
• Confirm that the Control Input Display is enabled.
• Check whether pitch, roll, rudder and throttle inputs are being received.
• If using the Browser Source, copy the current address from StreamFlight again.
• Refresh the Browser Source if necessary.

Pitch Appears Reversed

Use:

Invert Pitch Indicator

This changes the visual direction of the pitch indication.

It does not alter the aircraft controls.

Different Aircraft Behave Differently

Control ranges can vary between aircraft and add-ons, particularly throttle implementations.

A visual difference between aircraft does not necessarily indicate that StreamFlight has lost the simulator connection.

See Chapter 6 — Control Input Display.

16.17 Landing Rate Problems

If no landing rate is displayed after touchdown:

• Confirm that the Landing Rate feature is enabled.
• Confirm that StreamFlight is receiving simulator telemetry.
• Confirm that the aircraft has actually transitioned from airborne to on-ground.
• Check the configured display time if the result disappeared sooner than expected.

The TEST function can be used to confirm that the Landing Rate display itself is working.

If the test result appears correctly but an actual landing does not, the problem is more likely related to landing detection or simulator data than the overlay display.

For Browser Source problems, copy the current Landing Rate Browser Source address from StreamFlight again.

See Chapter 9 — Landing Rate.

16.18 RAAS Problems

RAAS is available with:

Microsoft Flight Simulator 2020 / 2024

If RAAS announcements are not heard:

• Confirm that Enable RAAS is selected.
• Confirm that StreamFlight is connected to MSFS.
• Check the selected RAAS Audio Output Device.
• Check the RAAS volume.
• Confirm that the required individual RAAS announcements are enabled.

Use:

TEST AUDIO

to verify the selected audio device and volume.

If TEST AUDIO cannot be heard, check the audio-device configuration before troubleshooting individual runway announcements.

If TEST AUDIO works but operational announcements do not occur, confirm that the relevant RAAS option is enabled.

See Chapter 8 — RAAS — Runway Awareness & Advisory System.

16.19 Live ATC Problems

If Live ATC displays:

N/A

first confirm that the Network selection on the Overlays tab is:

VATSIM

or:

IVAO

Live ATC is not active for the other Network selections.

Then check:

• The aircraft's active COM1 frequency.
• Whether a suitable controller is currently available on the selected network.
• Whether the computer has an Internet connection.
• Whether StreamFlight has had enough time to retrieve current network information.

For VATSIM, StreamFlight can also provide CTAF/advisory behaviour where applicable.

See Chapter 10 — Live ATC: VATSIM & IVAO.

16.20 Camera Problems

StreamFlight Camera Control is available for:

Microsoft Flight Simulator 2020 / 2024

If Orbit or FlyBy does not work:

• Confirm that StreamFlight is connected to MSFS.
• Confirm that StreamFlight camera controls have not been disabled.
• Stop any existing StreamFlight camera movement before trying another mode.
• Return to the cockpit and try again if the simulator camera is in an unexpected state.

External Camera Software

If using software such as ChasePlane, enable:

Disable StreamFlight camera controls

This prevents StreamFlight's camera system from interfering with the external camera application.

STOP Does Not Return to the Expected View

Allow StreamFlight a moment to complete the camera stop and return process.

Camera behaviour can differ slightly between MSFS versions and simulator camera states.

See Chapter 7 — Camera Control.

16.21 Passenger Check-In Problems

Passenger Check-In requires an active StreamFlight passenger manifest created from suitable SimBrief flight information.

If viewers cannot check in:

• Confirm that a SimBrief flight containing passenger information has been loaded.
• Confirm that StreamFlight is running.
• Confirm that Streamer.bot or the compatible chatbot/automation software is configured correctly.
• Confirm that the integration is using StreamFlight's Passenger Check-In service on port 38086.

Streamer.bot Is on Another Computer

In StreamFlight v3.0.0, Passenger Check-In on port 38086 is a local-only service.

Streamer.bot should therefore normally run on the same computer as StreamFlight when using Passenger Check-In.

Viewer Is Already Checked In

A viewer cannot receive multiple seats simply by repeating the check-in command.

If the same username checks in again, StreamFlight retains the existing seat assignment.

Flight Is Full

Once the planned passenger capacity has been reached, additional check-ins cannot be assigned another seat.

No Active Flight

If the integration reports that there is no active flight, load the required SimBrief flight and confirm that the Passenger Manifest has been initialised.

See Chapter 11 — Passenger Manifest & Viewer Check-In.

16.22 Output Files Not Updating

If files in the selected Output Folder are not updating:

1. Confirm that the correct Output Folder is selected in User Settings.
2. Confirm that StreamFlight can write to that folder.
3. Confirm that the simulator is connected if the file contains simulator telemetry.
4. Check the file directly in Windows to determine whether the problem is StreamFlight or the application reading the file.

If the file itself contains the correct information but OBS or another application displays an old value, check the external application's configuration.

Output Folder Was Changed

If the Output Folder has been changed, existing OBS Text (GDI+) sources, Streamer.bot actions or custom applications may still point to the old folder.

Update them to use the new location.

See Chapter 13 — Output Files & External Integration.

16.23 Resetting a Flight

Most normal flights reset automatically as the flight completes and StreamFlight returns to its normal preflight state.

A manual reset may be useful when:

• Performing circuits
• Performing repeated touch-and-go landings
• Starting another flight without shutting down
• Repositioning the aircraft
• Testing StreamFlight features
• The previous flight state should no longer be retained

Use:

Reset Progress Bar + Flight Phase

when a clean flight state is required.

16.24 Where to Get Further Help

If a problem cannot be resolved using this chapter, collect the basic information needed to describe the issue clearly.

Useful information includes:

• StreamFlight version
• Simulator and simulator version
• Aircraft being used
• Whether the problem occurs with a default aircraft
• Feature affected
• What StreamFlight displays when the problem occurs
• Whether the problem occurs every time
• Any error message displayed
• Whether StreamFlight was started before or after the simulator
• Relevant screenshots

For X-Plane problems, also note the status shown under User Settings.

For Browser Source problems, note whether OBS / Streamlabs Desktop is running on the same PC or a second PC.

For Live ATC problems, note the selected Network and active COM1 frequency.

For Passenger Check-In problems, note whether Streamer.bot is running on the same PC as StreamFlight.

Providing this information makes it considerably easier to identify the cause of a problem.

StreamFlight Discord

For additional help, support, discussion and information about StreamFlight, join the StreamFlight Discord community:

Join the StreamFlight Discord

When requesting help on Discord, provide as much relevant information as possible, including the StreamFlight version, simulator, aircraft and a description of the problem. Screenshots can also be helpful when diagnosing configuration or display issues.

Most StreamFlight problems can be separated into one of four areas: simulator connection, feature configuration, external application configuration, or network access. Checking which part of the chain has stopped working is usually the quickest way to identify the cause.

17. Quick Reference

This chapter provides a small number of quick-reference tables for StreamFlight v3.0.0. For instructions on using individual features, refer to the relevant chapters of this manual.

17.1 Simulator Compatibility

✓ Supported
— Not Supported

17.2 Browser Source & Integration Ports

Passenger Check-In port 38086 is local-only in StreamFlight v3.0.0.

17.3 Landing Rate Classification

17.4 Output File Reference

The following files are available in the StreamFlight Output Folder for use with OBS / Streamlabs Desktop, Streamer.bot and other compatible applications.

For instructions on using these files, see Chapter 13 — Output Files & External Integration.

One Companion. Every Sim. Every Flight.

Disclaimer

StreamFlight is intended solely for flight simulation and entertainment purposes and must not be used for real-world aviation or navigation.

StreamFlight is an independent product and is not affiliated with or endorsed by Microsoft, Laminar Research, Lockheed Martin, VATSIM, IVAO, SimBrief, OBS, Streamlabs, Streamer.bot, or other third-party products and services referenced in this manual. All trademarks and product names remain the property of their respective owners.

Features that rely on third-party software, simulators, networks or online services may be affected by changes to those services.

© 2026 StreamFlight. All rights reserved.