Re: Pegasus/vamsys support for FlightGear

I've seen you in Discord, and I have worked with this quite a bit to power external flight displays, so if you have any 'stupid' questions you can always ask me there 🙂 I haven't tried to have it output JSON. When I did my project, I had FlightGear spit out predefined chunks of binary that I then parsed based on their location within the chunk. It goes relatively fast compared to other interface methods like Telnet or HTTP, but it just blasts packets as fast as specified over the port without waiting for you to query it. Depending on what Vamsys wants, UDP might not be the best solution. Anyhow, you can message me here or in Discord, and I'll try and get you set up with the connection.

________________________________
From: menr0 <[email protected]>
Sent: Friday, July 3, 2026 1:55 PM
To: Israel Emmanuel <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: [Flightgear-devel] Pegasus/vamsys support for FlightGear

I have seen that commandline argument before, but I wasn't exactly sure, what it does. If you could point out the documentation for this argument, I think it is --generic, that would be greatly appreciated. "Open connection using a predefined communication interface and a preselected communication protocol." from the wiki doesn't quite cut it, we should explain what the different parameters do as well.
So that means all of the chunks defined in the protocol xml will be automatically sent (in json format?) to the target address?
If so, that is not perfectly ideal since they would rather poll than receive, but technically it would still fulfill their requirement.
If all of what I just layed out is true, we would then just need to clarify how to write the chunks for the xml such that you actually get what you want and then we can go ahead with mapping/documenting all of the required nodes. All of the entries, that make up one chunk should be explained along with their impact on the received packets.
If nobody else wants to do it, I could volunteer to write the documentation and make possibly required adjustments for the required nodes, but I would need someone to do sanity checks on what I am doing and having some channels, where I can ask stupid questions would also be very nice! I have done modding and scripting for aircraft before, but I am new to to actually developing the base game.

Sounds good?
On Friday, July 3rd, 2026 at 8:37 PM, Israel Emmanuel <[email protected]> wrote:
Ahhh, that's really simple to do. There is a command line argument that you start FlightGear with (if you don't know what it is, I can find it for you), and it will automatically start sending out UDP packets to the specified IP address and port at either the specified frequency or the simulator frame rate, whichever is lower. There should be some documentation for that, but if not, I can walk you through it.
________________________________
From: menr0 <[email protected]<mailto:[email protected]>>
Sent: Friday, July 3, 2026 10:52 AM
To: Israel Emmanuel <[email protected]<mailto:[email protected]>>
Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>
Subject: Re: [Flightgear-devel] Pegasus/vamsys support for FlightGear

They want to know how to connect to our UDP server. Documentation.
On Friday, July 3rd, 2026 at 4:08 PM, Israel Emmanuel <[email protected]<mailto:[email protected]>> wrote:
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]<mailto:[email protected]>>
Sent: Thursday, July 2, 2026 7:05 AM
To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>
Cc: menr0 <[email protected]<mailto:[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