Hi Shelton, Well, I guess David Luff and David Culp have already explained quite a bit. If you're interested in helping with AI traffic generation, you're mostly welcome. I do have some documentation concerning the generation of traffic files that I could send you off-list if you're interested (It's not quite ready for general release). In addition, as I mentioned earlier, I am currently working on a traffic pattern editor that should eliminate the need to understand the details of the AI traffic files. So if you would like to test out an early alpha version, I'm more than happy to send you a pre-release. This might take a while though, as I just started this project last weekend... :-)
As for your question why we have only 737's for AI traffic. The reason is that most of the traffic manager AI is in a relatively early stage of development and the supplied patterns serve mainly as a proof of principle. The 737 is one of the aircraft that is supplied by default in the base package. With the new traffic pattern editor, I'm moving away from the idea of using regular aircraft for AI traffic, but use dedicated AI models, which are somewhat lower in detail, because they're not regularly seen from small distances. However, this is again still in it's early stages. Cheers, Durk On Monday 31 October 2005 01:25, [EMAIL PROTECTED] wrote: > Hi Durk > > Thank you very much for the explanation - Let me know if you need a hand > with the AI part of FlightGear. I have some knowledge in XML. BTW, how is > the AI traffic generated in FlightGear - is there somewhere where I can > take a look, I would like to see some more heavy traffic landing in KSFO. I > mean if the 737s are implementated in KSFO, why not the A320? Let me know > if you want a hand at this. > > I used to play Flight Unlimited 2 and 3 before I moved onto Linux, and they > did an exceptional job when it came to AI traffic. > > Regards, > Shelton. > _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
