On Monday 21 July 2003 23:55, Jim Wilson wrote: > Lawrence Manning <[EMAIL PROTECTED]> said: > > > Running latest CVS now (well, as of yesterday). Flying 747 out of default > > airport. I did not know autopoilot could take off. No idea if this is a > > designed feature, but it is nice. > > > > After flying around for a little while to look at the Golden Gate Bridge > > (VERY nice), I paused to take some screenshots with the outside view. > > Upon restarting with P, everything went black. Everything, that is, > > except for the hud. Switching to outside views showed everything except > > the tower view to be completely black. Zooming etc showed nothing except > > the hud. Interestingly, the tower view appeared ok, *except* for the > > space between the clouds being black (looked kind of freaky...) Anyone > > seen this? Is it worth syncing to the latest code? Wild guess, but could > > this be related to the replay code? > > There is a bug. I've noticed this from time to time lately, but haven't had a > chance to track it down. It's been there for a two or three weeks now. It > isn't any one aircraft or fdm involved, but there are a few things I've > noticed might be pattern related: > > 1) The tile loader blows up. > > 2) The viewer seems to be broken recently (pause screws up something). > > 3) The failure could be happening with autothrottle engaged. > > In any case I'll investigate further, if anyone has more info it would be > appreciated. > > Best, > > Jim
I noticed that the lat and lon were getting corrupted (nans) so the tiles couldn't be found and the same time relative (to loc) views were getting screwed. Monitoring a plot in Atlas showed this too. I haven't tried the patch yet so you've probably already figured this:) LeeE _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
