Hi all, I've found a repeatable FG scenario that's causing a system hang & crash on my system. I strongly suspect it's due to the ATI drivers for my ATI9200 256MB video card but it's interesting that it was so repeatable.
It would be handy to have something a little more solid to beat ATI around the head with so any comments, observations or confirmations about it would be handy. Without going into fine detail, I was flying out of KSFO 28L in the TSR-2 after setting NORMM, KSFO & KINW as AP waypoints. The most important factor appears to have been the time of day - I was setting a time equivilent to just before sun-rise i.e below the horizon (although I didn't use the time-of-day menu entry but by supplying a specific offset - the 'actual' time varied by about 30 mins). In chase view, as the a/c reached NORMM it banked to the right to come around to KSFO and it was once the a/c had banked that I noticed that the pale orange band of haze on the horizon was flickering slightly, to a darker shade. It wasn't a very noticable flicker and I didn't see it the first time, but saw and confirmed it on the two subsequent runs I did. the a/c carried on flying ok through this but coming out of the bank, and just about when the a/c had levelled up, the horizon still flickering, the system display hung. I could ssh into it but issuing a shutdown just caused a complete hang. The flight profiles were almost identical - the a/c track and 'crash' points being monitored with Atlas. When I then tried the same profile, but effectively about an hour later, the flight went fine. There was no flickering but by this time the sun had arisen and the haze band was now pale yellow. As I say, I suspect this is a problem with the ATI drivers not handling the OpenGL correctly, but if any one has any possible ideas what it might be that's failing, I can try to pass it on to ATI. Ta LeeE _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
