Stand Alone ATC Control Development: Difference between revisions

Stand Alone ATC Control Development (view source)

809 bytes added , 3 December 2010

Add flight plan support to ideal ATC client

7

edits

@@ Line 235: / Line 235: @@
 '''Chat messages''' to/from other pilots and controllers.
+'''Flight plans''' will be the trickiest part. Not only should the ATC client have the ability to understand things like the route (to draw it on screen if needed; though this is quite optional at the beginning), but it will pose on Flightgear itself the need to support flight plans, with a standard form to be filled in by pilots prior to the flight; additionally, the MP protocol will have to implement it so that "flight plan packets" can be sent (by pilots) and received (by controllers). Additionally, as seen in other environments (optional at the beginning also), the controller should have the authority of correcting that FP, which would be sent back to the pilot with the modifications. This can apply either to aircrafts under the sontrol of the particular ATC, or to all the aircrafts in scope.
 I don't think the radar client should connect as a fake pilot. In my opinion, the MP protocol should be extended so that controllers could login as such.