On 2/25/04 at 8:34 PM Durk Talsma wrote:

>On Wednesday 25 February 2004 11:17, David Luff wrote:
>
>I'll had a quick glance at the code yesterday, but couldn't really figure
>out 
>how it worked, given the time I had. So do you consider generating AI
>traffic 
>that starts on the ground (i.e. parked at the terminal/apron/gate)?

Yes, but that requires an infrastructure to describe logical gates and
taxiways to the AI traffic, which is currently very much in it's infancy.
You can see the only plane that currently starts on the ground at KEMT.
I'm sort of attacking the problem from both ends, both improving the code
for starting and finishing traffic properly on the ground, and improving
the code for planes that simply appear at the start of the runway to
takeoff, or simply disappear following landing.

>> Give me a shout if you're going to seriously hack at the ATC/AI code so
>we
>> don't end up duplicating...
>
>Yep, will do.  I'm thinking about approaching the problem from the other
>end 
>though. First specify the requirements of the database that stores flight 
>plans and then find a way to feed these data into the AI traffic manager,
>_in 
>addition_ to the randomly generated flights.

That sounds like a good plan.  It could get very complicated very quickly!
In the vicinity of an airport, figuring out the other arrivals and
departures shouldn't be too tricky, but if the user is flying an airway in
the middle of the US, say, then working out which flights from disparate
sources and destinations would be close (within radio range and on the same
frequency) could be an algorithmic nightmare!!  Good luck :-)  It would be
very cool to have working nicely though.  If you don't want radio
communication and interaction with ATC or the user from your models you
could also consider feeding the data into Dave Culp's AI tree as well.  At
some point in the future they'll probably merge.

>> PS.  Did you ever finish your round the world FG flight?
>>
>Hmm, do you mean in FlightGear, or in real life? :-)

I was thinking of the FlightGear one.  I had a feeling that something I did
to the engine might have disrupted it.  Was probably the fuelling!

Cheers - Dave




_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to