Curtis L. Olson wrote: > I agree that random/periodic bugs are insidious and frustrating and > makes the software look like crap; therefore we should have a > 'culture' of agressive pursuit of these problems. But, unfortunately > I can't replicate your particular problem here which makes it > difficult for me to do anything about it.
I've been playing around a bit and have a somewhat simpler test case that I can reproduce consistently. These coordinates place you immediately (100m or so) in front of the tile boundary that Melchior originally posted. On my graphics card, it's visible as a tiny white crack. fgfs --lon=-122.498813 --lat=37.586699 --heading=275 Just roll along for a little bit and you'll crash when you hit the tile boundary. I tried this with a few aircraft, and they all seem to see the same bump. Sticking a printf in YASim's update method (or actually uncommenting one that someone else added, heh) I see the terrain elevation leap by about 2 meters as you cross the tile boundary. Now, 2m doesn't sound like a lot to worry about, but clearly the terrain rendering isn't showing anything near a 2 meter difference, so the problem isn't with the scenery data itself. If there's a bug in the collision detection, it's possible that it has higher magnitudes elsewhere. I have to go back to work now, but maybe this will help someone else track down the issue. Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
