On Wednesday 25 February 2004 11:17, David Luff wrote: > The code to generate the random AI lives in AIMgr.cxx in the ATC directory. > At the moment they get generated between 6 and 25km or so from the airport > and then arrive and land, either staight-in or via a downwind entry > depending on direction of approach w.r.t. the active runway. They're a bit > hard to follow at the moment since at one point in the flight they suddenly > change direction without banking to approach the airport, I'll try and fix > that ASAP. You should be able to hear them more easily than seeing them if > you tune your comm radio to the tower frequency.
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)? > > In addition to Atlas, there is also another open-source flight planner for > MSFS, called 'Nav'. It's written in MFC for windows only, but I was > wondering how much work it would be to port to wxWindows and convert to > reading FlightGear data. Probably a lot and not much respectively. > Sounds interesting. The fact that' its written in MSVC is a big showstopper for me though, as I'm only using gcc these days > 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. > > Cheers - Dave > > PS. Did you ever finish your round the world FG flight? > Hmm, do you mean in FlightGear, or in real life? :-) The answers are "no" and "yes" respectively. My FlightGear flights ended ion Hokkaido Island, after running out of fuel over the pacific, hacking a saved flight, restarting (this was already before we had a public interface to the property tree) to refuel, and still making it. This was around the time of defending my dissertation, after which I soon left Amsterdam for a two year stay in Durham, North Carolina. During my time in the USA, I only had one laptop at home, which was slightly under powered for FlightGear, and I also found out that I wasn't able to edit my homepage from a domain other than that of my ISP. In the meantime, my ISP has taken that site off-line, so consequently the project slowly died. I'd like to see if I can find some notes somewhere, so I can pick-up where I left off. But if not, I'll call it a day. In real life, however, after my two years in Durham, I left North Carolina, driving cross-country to Davis, California (with a few huge detours, including Cape Canaveral, Houston, TX, New Mexico, Aspen, Colorado; Yellowstone Park, Salt lake city and southern Utah. In Davis, I took the train to San Fransisco, and from there I flew to Honolulu, to Auckland, New Zealand (via Sydney), to Canberra, Australia, to Alice Springs, to Darwin (all in Australia), and from there to Singapore, to Hong Kong, to Delhi (India) to Cairo (Egypt; via Bahrain, and Abu Dhabi). And finally from Cario to London, and from London to Amsterdam, where I arrived back, November 30th, last year. So, if you're interested in recreating these Flights in FG, you need (hint, hint) :-) - a British Airways 737 (Amsterdam - London Gatwick) - an American Airlines 777 (London Gatwick - Raleigh Durham Intl) - an American Airlines 767 (San Fransisco - Honolulu) - a Qantas Airways 767 (Honolulu - Sydney, Sydney Auckland, Auckland Sydney) - a Qantaslink Dehavilland Dash-8 (Sydney - Canberra, and Canberra Sydney: three weeks later - a Qantas 737: Sydney Alice Springs, and Alice Springs - Darwin) - again a Qantas 767 (Darwin - Singapore) - a Cathay Pacific Airbus A330 (Singapore - Hong Kong and Hong Kong - Delhi) - a Gulf air Airbus A330 (Delhi, Bahrain, Bahrain - Abu Dhabi, and Abu Dhabi - Cairo) - a British Airways 747-400 (Cairo - London Heathrow) - and finally, a British Airways Airbus A319 Anyways, I'm going off topic here. Time to quit, Cheers, Durk _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
