34
edits
OpenRadarFeatureWishlist: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
* (by design) Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10 | * (by design) Callsign greater than 7 characters, cannot even have ICAO_TWR as callsign. Would like at least 10 | ||
:(comment ww: The flightgear MP protocol supports only 7 chars (max. 7 chars plus trailing zero equals 8 bytes, see [[Multiplayer protocol]]) | :(comment ww: The flightgear MP protocol supports only 7 chars (max. 7 chars plus trailing zero equals 8 bytes, see [[Multiplayer protocol]]) | ||
::Well this should be fixed. What if multiple controllers controll with similar callsigns? (E.g. LSZH_APP_EAST,LSZH_APP_WEST) | |||
* Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers | * Inter ATC communication. Some method of talk/text just between ATC controllers would be nice, to coordinate handovers | ||
:(ww: yes, but as much as I know they use mumble right now... I am looking for a smart way to do this) | :(ww: yes, but as much as I know they use mumble right now... I am looking for a smart way to do this) | ||
| Line 12: | Line 13: | ||
* (done: SHIFT+F12) The ability to reload the airport without having to restart the whole application. This is while I am developing Routes, it's a pain to constantly have to restart the entire thing. | * (done: SHIFT+F12) The ability to reload the airport without having to restart the whole application. This is while I am developing Routes, it's a pain to constantly have to restart the entire thing. | ||
:(ww: yes, pretty useful, I think about it. Reloading the routes would be enough I think...) | :(ww: yes, pretty useful, I think about it. Reloading the routes would be enough I think...) | ||
* Wider radar range for CTR controllers | * Wider radar range for CTR controllers (FGCom radio & visibility range) | ||
* Squawk / Transponder codes | * Squawk / Transponder codes | ||
* Private message feature | * Private message feature | ||
* Intercom FGCom frequency call GND to GND to call other ATC's | * Intercom FGCom frequency call GND to GND to call other ATC's | ||
* Controlling multiple airports (CTR controller) | |||
== Aircraft/Pilot Flag == | == Aircraft/Pilot Flag == | ||
* See assigned flightlevel (according to flightplan) | * See assigned flightlevel (according to flightplan) | ||
* Squawk/Transponder Code | * Squawk/Transponder Code | ||
* "True" altitude according to local air pressure below transition level and flightlevel according to standard pressure (QNH 1013/ | * "True" altitude according to local air pressure below transition level and flightlevel according to standard pressure (QNH 1013/2992) above transition level | ||
* Red colored flags for emergency codes such as 7500 (hijack), 7600 (radio failure) and 7700 (general emergency MAYDAY, PAN PAN) | * Red colored flags for emergency codes such as 7500 (hijack), 7600 (radio failure) and 7700 (general emergency MAYDAY, PAN PAN) | ||
* Voice, Text ability of Pilot (FGCom) | * Voice, Text ability of Pilot (FGCom) | ||
== METAR == | |||
* Winds below 100 degrees with preceeding 0/00, so that wind directions are read in 3 numbers. (E.g. wind 9@3 is read as "wind zero-zero-niner at tree") | |||
* METAR of nearby airports | |||
* Full METAR code | |||
== Radar Map == | == Radar Map == | ||
| Line 36: | Line 43: | ||
== Radar Contact handling == | == Radar Contact handling == | ||
== FGCom Integration == | == FGCom Integration == | ||
* (Done) Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift (ww: but the right hand is occupied with the mouse. maybe we move the neglected key to the right SHIFT. SH: If using FGcom, most of the time there would be no need to use anything but single key presses, so therefore any button would be fine. Remember LShift is the primary key for PTT2. Fn keys?) | * (Done) Remove CTRL as PTT button, clashes with CTRL-Left click for "neglect", suggest Right Shift (ww: but the right hand is occupied with the mouse. maybe we move the neglected key to the right SHIFT. SH: If using FGcom, most of the time there would be no need to use anything but single key presses, so therefore any button would be fine. Remember LShift is the primary key for PTT2. Fn keys?) | ||
:ww: removed CTRL+CLICK, there is a textbutton above the flightstrips now, to toggle neglect | :ww: removed CTRL+CLICK, there is a textbutton above the flightstrips now, to toggle neglect | ||
* Add "set PTT button" feature | * Add "set PTT button" feature | ||
=== Missing/not working frequencies === | === Missing/not working frequencies === | ||
* 118.10 seems not to work at LSZH TWR. - Maybe there is a collision with the frequency of another airport? | * 118.10 seems not to work at LSZH TWR. - Maybe there is a collision with the frequency of another airport? | ||