Connect EuroScope

The web app waits for a matching EuroScope connection before it opens an operational board. Set up EuroScope first, then open the app from the plugin.

Note

Your vACC may distribute the plugin with its sector-file package. If FlightStripsPlugin.dll is already loaded in EuroScope, go directly to Connect for a session.

Install a release manually

Use these steps only when you need to install a release yourself.

1. Download both release files. Open the Flight Strips releases page and download FlightStripsPlugin.dll and flightstrips_config.ini from the required plugin release.

2. Unblock the downloaded files. In Windows, right-click each file, open Properties, select Unblock when that option is present, and apply the change.

3. Install both files together. Close EuroScope, then place the DLL and INI file in the plugin directory used by your EuroScope setup. Keep flightstrips_config.ini beside FlightStripsPlugin.dll.

4. Load the DLL. Start EuroScope and load FlightStripsPlugin.dll from EuroScope’s plug-in dialog.

The release workflow publishes those two files together. The INI file contains the authentication and Flight Strips server endpoints used by the plugin; do not substitute a development configuration on an operational setup.

Connect for a session

Tag and list fields

Select the Flight Strips plugin as the provider in EuroScope’s tag editor or flight-list column setup. The same item works in both places:

Item	Value	Edit function
EAT	Holding release time (estimated approach time), in UTC HHMM	Managed by the holding/AMAN workflow
FS scratch pad	Shared controller text, up to 15 bytes (the EuroScope item limit)	Edit FS scratch pad

Any connected operational controller can edit the FS scratch pad, including controllers who do not track the aircraft. Submit an empty value to clear it. Flight Strips saves edits in its database and pushes the saved value to the other controllers in the session. Reconnecting restores the saved text. This field is separate from EuroScope’s native scratch pad.

Sign in

1. Connect EuroScope normally. Use the callsign and primary frequency for the position you are working. The plugin derives the relevant airport and position from the EuroScope connection.

2. Open the Flight Strips panel. Enter .fs open in EuroScope’s command line.

3. Sign in. Select Login in the panel and complete the browser sign-in with your VATSIM account. The panel changes to Logged in as followed by your name.

4. Wait for Connected. The panel reports Connecting, Syncing, Retrying or Connected. Continue only when it shows Connected.

5. Open the board. Select Open App in the panel. Sign into the web app with the same VATSIM account if prompted.

The plugin automatically sends its authentication token and session login after its WebSocket connects. The login includes the relevant airport, session mode, primary frequency, callsign, range, observer state and local IP address.

Read the panel

Panel state	Meaning
Logged out	Select Login before the plugin can connect.
Connecting / Syncing	The plugin is establishing the server connection or waiting for initial synchronization.
Connected	The plugin is connected; open the web app and verify the board.
Retrying	A connection attempt failed and the plugin is waiting before its next attempt.
Disconnected	One or more connection requirements are missing. Check authentication, EuroScope connection, airport and primary frequency.

Expand Stats when support asks for connection details. It shows the callsign, primary frequency, relevant airport, plugin role, session mode and message counters.

While connected, Master below the connection status identifies the current FS Master by callsign, even with Stats collapsed. Runway mismatch warnings also name the master alongside the expected and current runways.

Useful commands

• .fs open shows the Flight Strips panel.
• .fs close hides it.

The cdm master and cdm slave commands also exist in the plugin, but they are operational controls rather than onboarding steps. Do not use them unless the relevant local procedure tells you to.

If sign-in does not complete

The plugin starts a temporary local callback listener and tries ports 27015, 32015, 37015, 42015 and 47015. If every callback port is occupied, follow Authentication troubleshooting.

Next, complete the First-session checklist.