David Culp <[EMAIL PROTECTED]> said: > > Ok -- all you have done is state that takeoff is a procedure to be followed > > without defining the procedure (i.e. its hard coded and there is no > > variation from that procedure) > > Actually, I don't see a need for the AI airplanes to have brakes, elevators, > flaps and such. Our visions of AI traffic are much different.
Agreed. It isn't practical with standard hardware to run a full fdm/ap for each AI instance. There needs to be a very rudementary fdm for AI aircraft. No fancy atittude and control stuff. Ground traffic is potentially very complex but in air behavior should be fairly easy. Fly! used to run their AIs for approaches and basically just do a series of touch and gos. This would be easy enough to accomplish by adapting the ils/gs and ap code. But the commands for adjustments should just involve direct changes to attitude and speed (smoothed in a linear fashion), rather than translating control inputs into aerodynamic responses. Otherwise we'll all need a cluster of 3ghz pc's just to run this thing. It certainly would be the only way to mix AI traffic with live pilots when one participant is running in a non-dedicated peer host server mode (which is, IMHO, a worthy goal). Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
