ATC-pie: Difference between revisions

Jump to navigation Jump to search
Version 1.9.2
mNo edit summary
(Version 1.9.2)
 
Line 10: Line 10:
| developedby            = Michael Filhol
| developedby            = Michael Filhol
| initialrelease        = February 1, 2015
| initialrelease        = February 1, 2015
| latestrelease          = 1.9.1 (March 25, 2025)
| latestrelease          = 1.9.2 (Nov. 29, 2025)
| writtenin              = Python
| writtenin              = Python
| writteninversion      = 3
| writteninversion      = 3
Line 35: Line 35:
* flight plan operations;
* flight plan operations;
* CPDLC...
* CPDLC...
Development is on GitLab: https://gitlab.com/atc-pie/atc-pie


== Screenshots ==
== Screenshots ==
Line 60: Line 58:
* FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
* FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
* teaching service (spawn and simulate traffic visible to a connected student)
* teaching service (spawn and simulate traffic visible to a connected student)
* student session (control traffic simulated by teacher)
* student session (control traffic simulated by a teacher)


Location modes:
Location modes:
Line 82: Line 80:
! Voice radio
! Voice radio
| voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back
| voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back
| colspan="2" | [[FGCom-mumble]] integration
| colspan="2" | integrated [[FGCom-mumble]]
| teacher simulates pilots
| teacher simulates pilots
|-
|-
! ATC phone lines
! ATC phone lines
| N/A
| N/A
| colspan="2" | integrated Mumble connection
| colspan="2" | integrated VoIP support
| teacher simulates ATCs
| teacher simulates ATCs
|-
|-
Line 114: Line 112:
| style="text-align:left" |
| style="text-align:left" |
* exact aircraft rendering in views (incl. control surfaces, etc.)
* exact aircraft rendering in views (incl. control surfaces, etc.)
* historic [[FGCom_3.0|FGCom executable]] alternative supported
* RDF supported even without FGCom enabled
| style="text-align:left" |
| style="text-align:left" |
* frequency tuning system for radio text chat
* frequency tuning system for text radio
* text ATIS repeatedly sent through radio chat on recorded frequency
* text ATIS repeatedly sent through text radio on recorded frequency
| style="text-align:left" |
| style="text-align:left" |
* traffic snapshots and recall to repeat situations with the student
* traffic snapshots and recall to repeat situations with the student
Line 169: Line 167:
* voice radio with 8.33 kHz frequency spacing, multiple radio transmissions and monitoring
* voice radio with 8.33 kHz frequency spacing, multiple radio transmissions and monitoring
* [[controller-pilot data link communication]] (CPDLC), incl. DEP clearance delivery, multi-element messages...
* [[controller-pilot data link communication]] (CPDLC), incl. DEP clearance delivery, multi-element messages...
* text radio chat with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist
* text radio with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist


ATC coordination:
ATC coordination:
Line 175: Line 173:
* CPDLC authority transfers
* CPDLC authority transfers
* telephone lines and switchboard (direct voice communication)
* telephone lines and switchboard (direct voice communication)
* text messaging (private channels and general ATC chat room)
* text messaging (private channels and public ATC chat room, with alias substitution)
* "who has?" requests
* "who has?" requests


Line 202: Line 200:


=== OpenRadar ===
=== OpenRadar ===
[[OpenRadar]] is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's philosophies differ in several ways:
[[OpenRadar]] is another stand-alone program for 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;
274

edits

Navigation menu