> My hypothesis is that something in the AI-Traffic code doesn't like being > re-positioned;
Maybe related to issue #133 in bug tracker: http://code.google.com/p/flightgear-bugs/issues/detail?id=133 The AI code corrupts memory when the plane leaves the range of an ATC station. It usually happens when flying. Haven't tested repositioning too much, but I guess it could trigger the same scenario, when the new position is several miles away... I added two patches to the tracker to fix memory corruption in the AI code, but they are not in GIT yet. I guess the tracker is not really used too much. Maybe s.o. could have a closer look at this issue, since this corruption problem happened *really* often to me. I never managed to fly more than 40-50 miles away from an airport when AI was enabled. The patches in the tracker fixed the issues for me. Another workaround is to disable AI traffic right from the start. Thorsten ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
