OpenRadar Change Log: Difference between revisions

Jump to navigation Jump to search

OpenRadar Change Log (view source)

Revision as of 10:49, 2 January 2015

59 bytes removed ,  2 January 2015
Added new features for next release
(Added new features for next release)
Line 1: Line 1:
[[OpenRadar| Back to mainpage]]
[[OpenRadar| Back to mainpage]]


* I am working on (on a slower pace, not contained in next update)
{{TOC limit|2}}
:* Flightplan exchange server
 
::* Prototype for a common backend for FlightGear (I need someone to add it to FG), ATC apps like OR and Website like lennys FP landing page
== Next update COMMING SOON ==
::* First stage: Implement and test with OR without full persistence to a database
::* Second stage: Implement database interface
::* Thirst stage: Permanent availability by running on a public server


:* Flightplan integration into OR
* call sign can be set before OR is launched
::* Destination airport is displayed in data block
* chat history can be re-used via up and down keys
::* Assigned runway replaces destination airport in data block, if the contact it targeted to the current airport
* contact tails are back (flight history marks)
::* Flightplans are stored on the server, so if the contact arrives anywhere else, the ATC can re-use the existing data
* better handling of map data issues
::* Handover (offer) and TakeOver (realisation of the hand-over offer) to ATCs in range, otherwise release contact from control until he reaches the range of another ATC. FP data survives this uncontrolled phase.
* alternative radio text that is sent with ATIS (to publish the mumble server, for instance)
::* Auto release from control, if contact leaves the range of the controlling ATC.
::* All other ATCs see the current flightplan of contacts that are controlled by someone else.


* Integration with http://flightgear-atc.alwaysdata.net/
:* Flightplans can be maintained by pilots at website
:* ATC can select and download the flightplan
:* After download the flightplan is exchanged and shared between all OR ATCs that have the contact in range
:* ATC can close flightplan


{{TOC limit|2}}
* Routes
:* If routes are split into real world routes and have a name, they can be selected and assigned in flightplan dialog
:* Shared route parts can be defined separately and included into other routes
:* If a selected contact has got a route assigned, this route is hightlighted too
:* Route <text> can be defined to be clickable. Then the nw hotspot can be used to assign a route to the selected contact quickly.


== Next update ==
* change: The purple contact coloring (when an assigned squawk is not tuned in) has been removed.
* new possibility to download flightplans from server http://flightgear-atc.alwaysdata.net/ using a button in flightplan dialog
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for sporadic problems when displaying the flightplan dialog over the radar screen triggered by mouse
* fix for disturbing many screen changes when new METAR is received
* fix for disturbing many screen changes when new METAR is received
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix: the transition altitude field was restricted to Squawk values, now it is numeric and accepts more digits
* fix sounds, that have been disabled by default, when launching at a new airport
* many other fixes and improvements


== Published updates ==
== Published updates ==
Wagnerw
292

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/78727"

Navigation menu