Added Simbrief Intergration, Extended dispatch form with network prefile and several bugfixes.
What's new
-
SimBrief OFP Generation
Dispatch can now generate a SimBrief flight plan instead of only importing one you built yourself beforehand. Ticking "Generate via SimBrief" when confirming a booking opens SimBrief in your browser with the flight pre-filled; the generated route, altitude, runways, alternate, and fuel breakdown are pulled back into the booking automatically once ready. Requires a SimBrief username saved in your vAOMS profile settings. The existing "Load SimBrief OFP" button is unchanged for pilots who prefer to plan in SimBrief first.
-
Extended Dispatch Form
The pre-booking briefing panel now covers the full dispatch, not just network and time: route, cruise altitude, cost index, payload (passengers, hold luggage, cargo), and SimBrief options — Navlog, ETOPS, Stepclimbs, TLR, NOTAMs, FIR NOTAMs, plus taxi out/in, extra fuel, contingency, reserve, alternates, and units. Settings can be saved as your default for future dispatches.
-
Payload & Zero Fuel Weight
Passenger, luggage, and cargo figures are generated automatically when left blank, and each can be regenerated individually. A running ZFW readout is shown while editing a dispatch, with a warning when the payload exceeds the aircraft's maximum zero fuel weight.
-
Network Prefile
Once a dispatch is released on VATSIM or IVAO, a "Prefile on Network" button opens the network's own flight plan form in your browser with the flight details already filled in.
What's improved
-
Network Selection
VATSIM and IVAO are now sent to vAOMS as distinct networks rather than collapsing into a single "online" value, so the correct network is recorded against the flight. Networks vAOMS does not yet track separately (POSCON, PilotEdge, FSCloud, SayIntentions, Other) still report as "online". The Bookings network toggle has been replaced with the same picker used on the Timetable page.
-
Booking Data Fidelity
Route, cost index, network, and SimBrief OFP details sent by vAOMS were previously discarded when loading a booking and are now retained, which is what allows the dispatch form to show existing values rather than starting empty.
What's fixed
- Dispatch Update UI Bug - Dispatch Update had a UI bug where the times would appear out of the card, this has been solved.
- UTC Times Off By Timezone Offset — Booking and dispatch times could display shifted by your PC's UTC offset (for example, a 15:20Z departure showing as 17:20Z on a UTC+2 machine), because timestamps carrying a numeric offset were being converted into local time and then still labelled UTC. All API timestamps are now pinned to UTC on arrival, so displayed times match the web app exactly regardless of your machine's timezone.