Commands and Troubleshooting

Commands and troubleshooting

Enter vSMR commands in EuroScope's command/message bar. Commands are case-insensitive. Routine airport, profile, mode, AVISO, RIMCAS, inset and PDC tasks belong in the Runtime Menu or Control Center; the command set is intentionally small.

Supported commands

Control Center and data

Command	Effect
.smr	Open Settings in the Control Center for the first available vSMR radar screen or attached inset host.
.smr editor	Open Display in the Control Center for the first available vSMR radar screen or attached inset host.
.smr insets	Show the runtime rail on attached CoFrance inset hosts and report host/refresh status.
.smr reload	Reload configuration and data on open vSMR radar screens.

The two window commands require a vSMR screen or an attached inset host. They do not necessarily target the currently focused ASR when several screens are open. .smr reload does not install a release or bypass validation; use it after correcting a valid local Profiles or AVISO file outside the Control Center.

Diagnostics and logging

Command	Effect
.smr diagnostics	Write a redacted support report and display its path.
.smr diag	Alias for .smr diagnostics.
.smr log	Toggle normal logging on or off.
.smr log status	Show the logging state, level, and path.
.smr log normal	Enable concise operational logging.
.smr log verbose	Enable detailed trace logging for a short reproduction.
.smr log off	Disable logging.

vsmr.log is written beside the loaded vSMR.dll and rotates to vsmr.log.1 at about 4 MiB. Start with normal logging; use verbose only long enough to reproduce the issue once.

Native RDF

Command	Effect
.smr rdf on	Enable the native RDF overlay and remember the setting.
.smr rdf off	Hide the native RDF map overlay and remember the setting; RDF list detection/reset stay active.

There is no .smr rdf status command. See Native RDF for TrackAudio requirements.

RDF list operation with the overlay off is included in v2.0.1; older builds without this fix may require the overlay enabled for list TX.

First response to a problem

1. Note the symptom, approximate UTC time, active airport, and the action that triggered it.
2. Run .smr diagnostics while EuroScope is still running, if possible.
3. For a repeatable issue, enable .smr log normal and reproduce it once.
4. Copy the report, vsmr.log, and any matching crash report before changing the installation.
5. Review every file for callsigns, local paths, and operational or personal information before sharing it.

Caution

Do not mix files from different releases, bypass update verification, disable Windows security globally, or delete updater transaction files one by one.

Common problems

Symptom	Checks and next action
vSMR.dll will not load	Confirm 32-bit EuroScope, the x86 Visual C++ Redistributable, the complete matching package, and Windows Security history. Use Installing and Updating for a complete repair.
The loader starts but no vSMR display appears, or diagnostics shows an older version	Confirm that the loaded vSMR.dll has its matching vSMR_Data folder, including Runtime\vSMR.Runtime.dll and RELEASE-METADATA.json. EuroScope may be loading another plug-in directory, or the files may be mixed.
.smr reports no active SMR radar screen	Create or open EuroScope's SMR radar display, then retry.
The Control Center is blank	Install the x86 WebView2 Evergreen Runtime and confirm that vSMR_Data\vSMR_webUI came from the complete package.
The Control Center opens off-screen	Close EuroScope, move %LOCALAPPDATA%\vSMR\control-center-window.json aside, then reopen it.
A configuration change does not persist	Check the save/status message and the active profile or airport. Correct invalid input. If another editor changed the file, preserve needed text, then Revert or reload before editing again.
Reset leaves some selected AVISO styles unchanged	Only styles with matching bundled defaults for the same airport can be reset. Custom styles remain intact; inspect the status message and reset scope.
Profiles or an AVISO map fail to load	Check the active paths on Control Center — Settings, then inspect Profiles or AVISO. Restore only from a known backup.
Aircraft are unexpectedly hidden	Check the active profile, mode statuses, requirements, altitude, and speed limits; see Targets and Tags.
RIMCAS or an inset behaves unexpectedly	Verify the active airport and configuration in RIMCAS or Insets before changing data.
LFPG arrows are hidden or change after a manual toggle	Check ARR and DEP runways, opposing-direction exclusions and runway_group_visibility. Manual choices remain until the source runway selection/rule changes; see group visibility.
AVISO inset tag clicks do nothing	Use a complete build containing the inset tag-action fix; check the painted field and configured action. Right-click background drag is panning, not a tag click.
SRW Assume/Handoff does not open	Right-click the aircraft tag background rather than an editable field. The corrected interaction is included in the 2.0.2 stable feed and next-airac pack.
METAR shows only ICAO, wind and QNH	This is the expected smallest responsive layout. Resize for more detail; no manual Full/Compact/Mini selector remains.
An open airport is not on the METAR page	Check Settings → METAR airports, title-bar arrows and the open AVISO views. Stations are deduplicated and may be on another page.
Timers differ between AVISO and CoFrance	Use the same complete updated runtime for every view in one EuroScope session; countdowns are shared, not per-window. Separate EuroScope processes are separate sessions.
vSID is Online but CONFIG buttons are unavailable	Online does not imply required rules/areas are published. Check the provider snapshot, supported airport and pending command. NOT LOADED/MANUAL ONLY describe automatic-configuration availability, not network connectivity.
CDM, vSID or Ramp Agent values are empty	Check the bridge, compatible provider schemas and matching flight plan; see Integrations. Legacy AOBT/ATOT/AORT/event-booking tokens are currently empty by design.
An aircraft disappears with Ready/TSAT/TOBT required	Check CDM-published data and mode requirements; missing data can filter the aircraft.
A profile selection differs between ASRs	Active profiles are intentionally independent. Save each ASR; shared profile edits are a separate operation.
A map/palette/group is missing	Check the selected source and current bundle. The source contains 161 GeoJSON files, including the LFPO works variant; Real is airport-specific. LFPG provides separate East Arrows and West Arrows groups.
Looking for PDC reminders, Auto runways or the vSID Auto mode button	Those controls were removed. Manual Hoppie remains; vSID owns automatic SID assignment and runway-driven configuration. Current vSMR displays config status and Resume auto config when supported.
PDC or native RDF is unavailable	Follow the connection checks in Datalink or Native RDF.
RDF list TX stays blank	Configure vSMR RDF (width 2) and RDF reset. Check that the aircraft transmits on a frequency open for reception (RCV TXT or RCV VOICE) in this EuroScope instance, then check TrackAudio/callsign/correlated target/ground-speed eligibility. The current feed supports list operation with the map overlay off. See RDF list setup.
An update is blocked, deferred, or requests a manual loader update	Preserve diagnostics and check the installed package's release instructions. Per-file updates require loader 1.3.0 and the matching runtime/helper. Signing is optional unless explicitly required by that installation; failure to find a published channel manifest is separate from signature validation.

If antivirus quarantines a component, record the exact detection, verify the official release source, then re-extract and reinstall the complete package. Restoring one DLL can leave the loader, runtime, and data mismatched; do not create a broad exclusion simply to make it load.

If EuroScope rewrites active airports/runways on connection, check Set Active APT by Owned sector in EuroScope itself. Neither vSMR map-group rules nor vSID-panel actions should be used to lock those selections. For CoFrance attachment, load vSMR before reopening the ASR; Insets explains the host boundary and rail recovery.

Create a diagnostics report

Run:

.smr diagnostics

EuroScope displays the exact output path. vSMR first uses:

<EuroScope plug-in directory>\vSMR_Data\Diagnostics\

and falls back to %TEMP%\vSMR_Diagnostics\ when necessary. The report records the vSMR version and architecture, important paths, logging and crash-report status, active airport, bounded integration state, worker counts, open radar-screen count, and recent bounded log entries.

Secrets, message payloads, endpoint query strings, and the known Hoppie password are omitted or redacted. Callsigns and local paths can still remain, so inspect the report before sharing it.

Crashes and hangs

Nothing is uploaded automatically. A vSMR-related crash can produce a text summary and a matching .dmp file. The preferred directory is %LOCALAPPDATA%\vSMR\CrashReports\; .smr diagnostics reports the directory actually selected.

A frozen process does not create a crash report. Before ending EuroScope, use Task Manager's Create memory dump file if support asks for a hang dump, and record the UTC time.

Crash and hang dumps can contain process memory, typed text, callsigns, paths, credentials, and network data. Share them only through a trusted private channel.

What to include in a support report

• vSMR and EuroScope versions, Windows version, and the approximate UTC time.
• A short sequence of steps, plus expected and actual behavior.
• Active airport/profile/mode when relevant.
• The reviewed diagnostics report and matching vsmr.log files.
• A genuine screenshot of the symptom, when safe to share.
• Crash text and dump, or hang dump, only through a private channel.

Preserve the exact installed package metadata and affected Profiles or AVISO files when the issue depends on them. Remove credentials and operationally sensitive content before sharing.

Safe recovery order

1. Preserve diagnostics, logs, crash information, and the affected data.
2. Close EuroScope and copy the complete installation plus active external sources.
3. Revert reloads the last validated saved configuration, not an undo history. Use a known Profiles/AVISO backup to recover earlier custom data; Bundled defaults restores supplied configuration.
4. Restore a complete installer backup for a package-level failure.
5. Reinstall the complete matching package if files are missing or mixed.
6. Re-run .smr diagnostics and verify the airport, profile, mode, AVISO, RIMCAS, and insets away from live traffic.

See Installing and Updating for backup, restore, rollback, and reinstall procedures.