265
edits
ATC-pie: Difference between revisions
Jump to navigation
Jump to search
v1.8.4
Mickybadia (talk | contribs) (v1.8.3, moving sections across articles to balance sizes) |
Mickybadia (talk | contribs) (v1.8.4) |
||
| Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = 1.8. | | latestrelease = 1.8.4 (Aug. 14, 2021) | ||
| writtenin = Python | | writtenin = Python | ||
| writteninversion = 3 | | writteninversion = 3 | ||
| Line 193: | Line 193: | ||
== Interoperability with other software == | == Interoperability with other software == | ||
=== | === OpenRadar === | ||
ATC-pie and OpenRadar's philosophies differ in several ways: | OpenRadar is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's philosophies differ in several ways: | ||
* OpenRadar's basic processing unit is the FGMS callsign, whereas ATC-pie's is the strip; | * OpenRadar's basic processing unit is the FGMS callsign, whereas ATC-pie's is the strip; | ||
* OpenRadar's concept of handover is based on a shared notion of aircraft ownership, whereas ATC-pie allows any controller to pull out a strip and write a callsign on it; | * OpenRadar's concept of handover is based on a shared notion of aircraft ownership, whereas ATC-pie allows any controller to pull out a strip and write a callsign on it; | ||
* in OpenRadar, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring users to see it complete, whereas ATC-pie considers that a strip sent is gone and assumed to land on the receiver's rack, without anybody else necessarily to know. | * in OpenRadar, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring users to see it complete, whereas ATC-pie considers that a strip sent is gone and assumed to land on the receiver's rack, without anybody else necessarily to know. | ||
For most interactions to work while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange: | For most interactions to work in FlightGear sessions while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange between the two programs: | ||
* ATC-pie users can only hand over strips to OpenRadar that are linked to a radar contact; | * ATC-pie users can only hand over strips to OpenRadar that are linked to a radar contact; | ||
* aircraft under ATC-pie control are not shown as "owned" to OpenRadar users; | * aircraft under ATC-pie control are not shown as "owned" to OpenRadar users; | ||
| Line 218: | Line 218: | ||
Note that who-has requests are fully supported. | Note that who-has requests are fully supported. | ||
=== | === Euroscope === | ||
Euroscope is a popular program to control on VATSIM, a flight simulation network whose protocol is historically based on FSD | Euroscope is a popular program to control on VATSIM, a flight simulation network whose protocol is historically based on FSD. For a long time Euroscope allowed to connect to "plain" FSD servers, although being increasingly tailored for VATSIM, until it discontinued operability outside of VATSIM all together. | ||
Older versions of Euroscope are still around and connecting to FSD networks. ATC-pie is able to interact with them in FSD sessions, but only to a limited extent: | |||
* sending a strip to Euroscope will result in a loss of all strip details but the callsign (which must be connected), the only information left to the recipient being the FPL details for that callsign if any (strip changes made after FPL data retrieval are therefore lost); | * sending a strip to Euroscope will result in a loss of all strip details but the callsign (which must be connected), the only information left to the recipient being the FPL details for that callsign if any (strip changes made after FPL data retrieval are therefore lost); | ||
* receiving a strip from Euroscope is supported, but the sender will see the hondover pending (never "assumed"); | * receiving a strip from Euroscope is supported, but the sender will see the hondover pending (never "assumed"); | ||