On 5 Sep 2008, at 07:30, Durk Talsma wrote: > Your bug report reminds me of a similar one that was reported a few > weeks ago. > We recently overhauled the runway search code, and in the process it > is > possible that either a new bug was introduced, or that the new code > exposed > existing bugs that didn't occur before. > > We had some previous reports. IIRC, Gerard Robin, reported having > problems > starting from another French airport, and eventually this could be > traced back > to a data error.
Right, the actual assertion is happening in the code I changed - as I said at the time, I tried to catch all the places where people pass in invalidated runway identifiers, but the AI traffic code surprised me on this matter already. I've applied fixed where I know the cause, obviously I have missed one, apologies for that. Of course this is a totally separate issue to the *long* start up times due to static scenery complexity - I think that has caused some confusion in this area. I'll look over the code ASAP and get a patch to Durk (unless he beats me to it). Just to be clear, what are the exact steps to reproduce the crash? If you're using fgrun, I really need to see the actual command line passed to fgfs. Cheers, James ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
