On Tue, 2012-09-04 at 15:00 +0200, Anders Gidenstam wrote:

> 
> Try checking out the c172p as of the commit before
> caeebdbd935015fd7b2bb3071e5f09b1b7815415
> 
> E.g.
> 
> git checkout caeebdbd935015fd7b2bb3071e5f09b1b7815415^ -- Aircraft/c172p
> 
> That commit, from Aug 23, switches the c172p to use its own 
> instrumentation file rather than using the generic one. While the generic 
> one contains the wxradar instrument, the specific (naturally) doesn't.
> 
> IIRC enabling the wxradar instrument is a well/long-known work-around for 
> this problem on ATI hardware?
> 
> Also try changing the default window size settings in preferences.xml - to 
> see if the frame buffer for some reason reverts to the default/startup 
> size after the windows is resized to fullscreen.
> 
> 
> Cheers,
> 
> Anders

I reckon you are on the right track, Anders. I have already narrowed
narrowed the problem down to fgdata, as building "next" of yesterday
against with an older fgdata  checkout works just fine. I shall fast
forward to the commit you suggest. Grr, I am beginning to enjoy this
here git, it's cool - even for a senile old bugger like me :-)

Alasdair


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to