A settings and connection release, including API v2.
What's new
-
Simbrief v2 API
Dispatching with SimBrief no longer opens a browser window for you to fill in. vAOMS now builds the OFP server-side through SimBrief's new API, so the dispatch returns immediately and the SimBrief panel waits for the finished plan on its own. The completed briefing is shown in the app under View OFP instead of on simbrief.com. Generating requires a linked Navigraph account — the option is disabled with an explanation until you link one in the web app under Settings → Integrations.
-
Per-Phase Announcement Control
abin Crew Announcements now expands into a Per-Phase Announcements section where each of the nine cabin announcements — Boarding, Pushback, Taxi Out, Climb, Cruise, Descent, Approach, Landing, and Deboarding — can be switched on or off individually. The section header shows how many are enabled at a glance, and Cabin Crew Announcements acts as the master switch: turning it off silences every phase without losing your individual choices.
-
X-Plane Auto-Discovery Toggle
The X-Plane connection settings now include an auto-discover option alongside the address and port, so multicast discovery can be turned on without editing settings by hand.
What's improved
-
One Settings Location
Settings, logs, and custom sound packs now all live under `%APPDATA%\VAOMS Connect`. Previously settings were split across two files in two differently-named folders, which is what allowed the Connection Mode setting to be silently ignored. Your existing settings, sound packs, and preferences are moved across automatically the first time you launch this version, nothing to do by hand.
-
Connection Mode — FSUIPC Preferred
Automatic mode connects through FSUIPC, or X-Plane UDP, and keeps retrying until one of them is available. Both report more aircraft detail than SimConnect (livery, aircraft file, flap detents), so your aircraft is matched more accurately on the PIREP. SimConnect is never selected automatically, because it answers as soon as the simulator reaches the menu while FSUIPC cannot connect until the simulator has fully loaded, so an automatic fallback would take over during every startup and hold the connection for the whole flight. Pilots who do not use FSUIPC select SimConnect in Settings, and that choice is always honoured.
-
Connection Troubleshooting
The X-Plane address and port entered in Settings are now actually used when connecting. They previously wrote to a value the connector never read, so the app always used its built-in defaults.
-
Connection Badge Shows Your Simulator
The status badge in the top bar named only the connector ("FSUIPC CONNECTED"), which did not tell you which simulator it had found. It now reads the simulator and the connector together — "MSFS 2024 (SimConnect)", "Prepar3D v5 (FSUIPC)", "X-Plane 12" — so a wrong simulator or connector is visible at a glance before you depart. Hovering gives the connector version, and an outdated connector shows the version you need.
What's fixed
- The status badge in the top bar named only the connector ("FSUIPC CONNECTED"), which did not tell you which simulator it had found. It now reads the simulator and the connector together — "MSFS 2024 (SimConnect)", "Prepar3D v5 (FSUIPC)", "X-Plane 12" — so a wrong simulator or connector is visible at a glance before you depart. Hovering gives the connector version, and an outdated connector shows the version you need.
- The status badge in the top bar named only the connector ("FSUIPC CONNECTED"), which did not tell you which simulator it had found. It now reads the simulator and the connector together — "MSFS 2024 (SimConnect)", "Prepar3D v5 (FSUIPC)", "X-Plane 12" — so a wrong simulator or connector is visible at a glance before you depart. Hovering gives the connector version, and an outdated connector shows the version you need.
- The Connection Mode picker in Settings had no effect. The app read a separate stored value that no part of the interface could change, so MSFS was always connected through FSUIPC and Automatic mode never fell back between connectors as described. The picker now drives the connection.
- The "Sync Route" and "Sync Cruise Altitude" toggles had no effect; a SimBrief import always applied both. They are now honoured. Both are left enabled when upgrading, so importing behaves as it did before
- Flights connected through SimConnect were always recorded as Microsoft Flight Simulator 2020, because the connector never established which simulator had answered. The running simulator is now detected, so MSFS 2024 is filed correctly. Connections made through FSUIPC were already correct.