Ground Services: Difference between revisions

Jump to navigation Jump to search
Line 239: Line 239:
* Make it a Flightgear addon.  {{Progressbar|100}} {{done}}
* Make it a Flightgear addon.  {{Progressbar|100}} {{done}}
* Add a canvas GUI for monitoring vehicles  {{Progressbar|100}} {{done}}
* Add a canvas GUI for monitoring vehicles  {{Progressbar|100}} {{done}}
* Retrieve door positions from AI model. AI jetways apparently know how to do this. If not, extend AI core code for saving model origin information to the property tree.  {{Progressbar|20}}
* Retrieve door positions from AI model like [[Howto:Animated jetways|animated jetways]] does. AI aircraft should contain a piece of nasal code that adds door information to the property tree when loaded. However, extending AI core code for saving model origin information to the property tree could still be useful, eg. for defining cockpit positions in addon [[Model Cockpit View]].  {{Progressbar|20}}
* Extend AI core code for saving departure/arrival information of AI aircrafts to the property tree. Thus arrived parking aircrafts can be detected for service more reliably. Such an extension might also be helpful for the [[Howto:Animated jetways|animated jetways]]. {{Progressbar|10}} {{pending}}
* Extend AI core code for saving departure/arrival information of AI aircrafts to the property tree. Thus arrived parking aircrafts can be detected for service more reliably. Such an extension might also be helpful for the [[Howto:Animated jetways|animated jetways]]. {{Progressbar|10}} {{pending}}
* Unify AI traffic categories for avoiding manual patches to [[Model Cockpit View]] and [[Phi]] by a Nasal registry for all kinds of AI/MP traffic, eg. AI.nas or Traffic.nas. <ref>{{cite web
* Unify AI traffic categories for avoiding manual patches to [[Model Cockpit View]] and [[Phi]] by a Nasal registry for all kinds of AI/MP traffic, eg. AI.nas or Traffic.nas. <ref>{{cite web
183

edits

Navigation menu