20,741
edits
Stand Alone ATC Control Development: Difference between revisions
Jump to navigation
Jump to search
Stand Alone ATC Control Development (view source)
Revision as of 11:00, 23 September 2010
, 23 September 2010→Open questions
| Line 50: | Line 50: | ||
== Open questions == | == Open questions == | ||
* should atlas connect to fgms as a server (relay?) or a client (observer), or should it just poll fgms for updates? | * should atlas connect to fgms as a server (relay?) or a client (observer), or should it just poll fgms for updates? | ||
* how about using texture packs to make atlas symbols more customizable? | |||
* can atlas also render detailed airport overviews (taxiways), the corresponding code is available in taxidraw and fgsd if needed, and also the fgfs ground radar instrument | |||
* how about reusing data that is already sent to FlightGear (that would require a running FlightGear instance) | * how about reusing data that is already sent to FlightGear (that would require a running FlightGear instance) | ||
== Atlas features that should eventually become more configurable == | == Atlas features that should eventually become more configurable == | ||