After giving this some good thought i think the most proper way to deal with
this is to allow only 1 instance of an aircraft based on it's tail
registration PH-ONE for example. In doing so, we hand responsibility over to
the creator of the traffic file.
This will make sure (just like in real life) a unique aircraft can only
exists once in the (AI) 3d world.
An other problem needs to be solved though. If only 1 instance of a unique
aircraft can exist than this means that at some point the traffic manager
needs to:
1) Clean up to current instance before creating the next (not very elegant
but could be necessary if arrival and departure airport are not the same).
2) Reset fuel etc and overwrite it's "flight plan". (there should be a
minimum amount of time between recovery and departure)
I'll have to see what the possibilities are though.
-Jorg
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
