Euroscope support

[trinhxuanson]

I tried to run the OpenFSD successully; I wonder if if I can run Euroscope via this FSD server? since the built-in FSD server of Euroscope only restricted 2 controller connections only.

[renorris]

Currently, ATC connections aren't supported. Eventually it may be added; I'll keep this issue open as a feature request.

[jhl-hk]

When will ATC connect be available

[Misaka-Nnnnq]

Currently, ATC connections aren't supported. Eventually it may be added; I'll keep this issue open as a feature request.

There is a way to work with Euroscope by replacing the URL in Euroscope, but it may be against EULA.

[renorris]

Currently, ATC connections aren't supported. Eventually it may be added; I'll keep this issue open as a feature request.

There is a way to work with Euroscope by replacing the URL in Euroscope, but it may be against EULA.

Maybe so, but to be clear: there's no openfsd support for the ATC-specific FSD protocol. There are also other API endpoints hardcoded into Euroscope & other clients (aside from the plain FSD server address) that need to be addressed as well.

[Misaka-Nnnnq]

Currently, ATC connections aren't supported. Eventually it may be added; I'll keep this issue open as a feature request.

There is a way to work with Euroscope by replacing the URL in Euroscope, but it may be against EULA.

Maybe so, but to be clear: there's no openfsd support for the ATC-specific FSD protocol. There are also other API endpoints hardcoded into Euroscope & other clients (aside from the plain FSD server address) that need to be addressed as well.

Yeah. But I have implemented some protocols with C++, I can share them with you.

[trinhxuanson]

Currently, ATC connections aren't supported. Eventually it may be added; I'll keep this issue open as a feature request.

There is a way to work with Euroscope by replacing the URL in Euroscope, but it may be against EULA.

Maybe so, but to be clear: there's no openfsd support for the ATC-specific FSD protocol. There are also other API endpoints hardcoded into Euroscope & other clients (aside from the plain FSD server address) that need to be addressed as well.

Yeah. But I have implemented some protocols with C++, I can share them with you.

Yeahhh, could you share for me please l, i really want to test the FSD server for ATC clients

[renorris]

@Misaka-Nnnnq Feel free to email whatever you'd like to mail (at) reesenorr.is.

Full protocol documentation is in the works on my end. Will be shared once complete & used for the next openfsd iteration.

[jhl-hk]

Currently, ATC connections aren't supported. Eventually it may be added; I'll keep this issue open as a feature request.

There is a way to work with Euroscope by replacing the URL in Euroscope, but it may be against EULA.

Maybe so, but to be clear: there's no openfsd support for the ATC-specific FSD protocol. There are also other API endpoints hardcoded into Euroscope & other clients (aside from the plain FSD server address) that need to be addressed as well.

Yeah. But I have implemented some protocols with C++, I can share them with you.

May I have one copy plz.

[michael-filhol]

Hello,
I was going to contact the author to know more about this project's user base, usage, support, etc. because:

1. I thought plain old FSD (i.e. outside of Vatsim) was barely living any more, and virtually only hanging on the old kuroneko/fsd fork, whereas this repo looks pretty active and relevant;
2. I authored and maintain an ATC simulation program (ATC-pie) which can connect to FSD networks, at least those served by the kurenoko version, a feature I added as I met a flight sim group that took interest in it.

So this begs questions from me... Is openfsd meant to be a continuation of FSD, or does it redefine things fresh or in a non-compatible way?

In the former case, ATC-pie could be the already available solution that people in this thread are looking for (replacing Euroscope). In the latter, I would be very interested in studying renorris's work here and why not add yet another connection type in ATC-pie to support ATC roles on openfsd networks.

[renorris]

1. Yes, FSD is barely living anymore outside of VATSIM and IVAO. (Not even sure about IVAO... do they still use FSD?)
   This is a personal project that I work on during my free time (which is quite limited these days.) I just think network protocols, airplanes, and computers are cool. That's pretty much why I spend time on this.
   Since the last major public release, there's been lots of programming behind the scenes working towards a fully-functional ATC system. No ETA at all for this though.

2. Very cool. I will check out your ATC client and see how I can support it one day. Is there any way to view it?

The philosophy of openfsd is simply meant to be an open-source alternative reimplementing VATSIM's version of FSD. There's no major reinventing the wheel or "redefining" anything. If a VATSIM client exists, I'd eventually like to support it on openfsd. I don't intend to "replace" Euroscope, or any other client. I want to support them.

[michael-filhol]

Of course you can have a look: see the project page, and a description of the features on the wiki page.
My point was that ATC-pie might already work transparently, regardless of Euroscope, provided that you have as little as position packet forwarding and the text chat system covered. This even includes the top features such as 3D tower view (through FlightGear), CPDLC (through Hoppie like Vatsim does), and phone land lines. The last section of the wiki page is a note on interoperability with Euroscope. It is limited, but programs can still coexist. I am happy to extend support here if you provide a way to work around their NDA, but I don't think this is possible.
We can take this to a separate thread as soon as you believe it becomes appropriate (e.g. off topic here).