292
edits
(→Radar Contact handling: Added SID/STAR filter request) |
m (Removed implemented or outdated text) |
||
Line 7: | Line 7: | ||
:(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 control with similar callsigns? (E.g. LSZH_APP_EAST,LSZH_APP_WEST) | ::Well this should be fixed. What if multiple controllers control with similar callsigns? (E.g. LSZH_APP_EAST,LSZH_APP_WEST) | ||
* Wider radar range for CTR controllers (FGCom radio & visibility range) | * Wider radar range for CTR controllers (FGCom radio & visibility range) | ||
:ww:I need to validate, but to my current knowledge, FGCOM is restricted on server side and the contact visibility by the MP server. I thought already about a special mode for CTR, that registers OR as MP server (proxy). Then it would get all contacts worldwide. For FGCOM we could add these special frequencies to the list of frequencies that are available everywhere at the FGCOM server. | :ww:I need to validate, but to my current knowledge, FGCOM is restricted on server side and the contact visibility by the MP server. I thought already about a special mode for CTR, that registers OR as MP server (proxy). Then it would get all contacts worldwide. For FGCOM we could add these special frequencies to the list of frequencies that are available everywhere at the FGCOM server. | ||
* Controlling multiple airports (CTR controller) | * Controlling multiple airports (CTR controller) | ||
:ww: To be able switch some features from airport to airport (METAR, runways, FGCOM, StdRoutes) I need to rework some parts of the application (relocation of OR multiplayer client to new airport, loading of different METAR, runways, routes etc). It would work like an hopping from airport to airport. Something for future releases, I think. | :ww: To be able switch some features from airport to airport (METAR, runways, FGCOM, StdRoutes) I need to rework some parts of the application (relocation of OR multiplayer client to new airport, loading of different METAR, runways, routes etc). It would work like an hopping from airport to airport. Something for future releases, I think. | ||
* ATIS recording feature | * ATIS recording feature | ||
:ww: Recording and then replay over the ATIS frequency? This might be possible | :ww: Recording and then replay over the ATIS frequency? This might be possible. | ||
::mc: Yes. compare with VRC (VatSim Virtual Radar Client), which has a recording option and EuroScope which does generate if from recorded fragments. - Text to speech (Espeak/Festival) integration would be the "tripple-A" feature!1!! ;) | ::mc: Yes. compare with VRC (VatSim Virtual Radar Client), which has a recording option and EuroScope which does generate if from recorded fragments. - Text to speech (Espeak/Festival) integration would be the "tripple-A" feature!1!! ;) | ||
* Give the fullname of a VOR when going over it with the cursor (MLN = Melun, LGL = L'Aigle) as ATC and pilot use also VOR names in real life. (Do the same for Airports and NDB?) | * Give the fullname of a VOR when going over it with the cursor (MLN = Melun, LGL = L'Aigle) as ATC and pilot use also VOR names in real life. (Do the same for Airports and NDB?) | ||
:ww: technically possible, but tooltips disturb usability very much. Please open a thread in forum and discuss is with the users! | :ww: technically possible, but tooltips disturb usability very much. Please open a thread in forum and discuss is with the users! | ||
* Traffic counter | * Traffic counter | ||
== Aircraft/Pilot Flag == | == Aircraft/Pilot Flag == | ||
* See assigned flightlevel (according to flightplan) | * See assigned flightlevel (according to flightplan) | ||
== METAR == | == METAR == | ||
* METAR of nearby airports | * METAR of nearby airports => right click on the METAR lines and define them. | ||
== Messages == | == Messages == | ||
Line 47: | Line 31: | ||
* additional deselect button below the map | * additional deselect button below the map | ||
* (via Standard routes, have no other data source) Show Restricted, Prohibited and Danger Areas | * (via Standard routes, have no other data source) Show Restricted, Prohibited and Danger Areas | ||
== Route Editing == | == Route Editing == | ||
* Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute <code>text=""</code> is not enough?) | * Speed limitation point tag for Elements, similar to the arrows. Requires text for speed. (ww: the attribute <code>text=""</code> is not enough?) | ||
== FGCom Integration == | == FGCom Integration == | ||
* Add "set PTT | * Add "set PTT shortcut key" feature | ||
* Change volume of fgcom channel | |||
== ATC Coordination == | == ATC Coordination == | ||
Line 66: | Line 46: | ||
:* (mp data) See to which frequency the Pilot is connected to (com1 & com2) | :* (mp data) See to which frequency the Pilot is connected to (com1 & com2) | ||
::ww: the frequency transmitted by FG via MP is not correct, is already implemented in background) | ::ww: the frequency transmitted by FG via MP is not correct, is already implemented in background) | ||
:* See on the map what regions are "controlled" by who (dark grey if an area is controlled, so the ATC knows to whom he can do the handoff) | :* See on the map what regions are "controlled" by who (dark grey if an area is controlled, so the ATC knows to whom he can do the handoff) | ||
== Missing/incomplete FG MP protocol data == | == Missing/incomplete FG MP protocol data == |
edits