Re: Pegasus/vamsys support for FlightGear

So what is Vamsys looking for here? Do they want an included protocol file with the rest of them in FGDATA? AS long as they know what properties they want, that should be pretty simple to do. The port you communicate on shouldn't matter for Vamsys, and shouldn't be a rigid thing either, in the event that another application is using that port to do anything.
________________________________
From: menr0 via Flightgear-devel <[email protected]>
Sent: Thursday, July 2, 2026 7:05 AM
To: [email protected] <[email protected]>
Cc: menr0 <[email protected]>
Subject: [Flightgear-devel] Pegasus/vamsys support for FlightGear

  *
Hello Everyone!
  *

  *
I just got involved with vamsys to possibly get their Pegasus 2 client to support FlightGear. Now that Pegasus 2 runs on all platforms, this would open up the world of virtual airlines to us FlightGear enthusiasts!
  *

  *
Pegasus is able to connect via UDP, much like the now antiquated Barrys Blackbox. They are interested in pursuing this and I feel like effort wise this is completely free, since FlightGear already supports UDP sockets with custom protocols (Barrys Blackbox actually uses exactly the same mechanism). The user would just have to copy the protocol into the protocol folder and add the server options into the commandline section, or you could of course add a similar option like the start swift server, just for pegasus.
  *

  *
Because I am not part of your development team, I would like to consult you guys, who actually know this stuff, but from everything I could gather so far:
  *
FlightGear already supports this, we just need to talk with them to figure out the protocol and ports.

If you are interested in contacting vamsys directly, you can join the conversation here: https://vamsys.co.uk/feedback/give-us-the-pegasus-udp-protocol

Best regards,
Menro

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel