On Tue, 4 Sep 2012, Alasdair wrote: > Thanks for the words of wisdom, James, but I am still curious to > determine when the problem began for me on the c172p. I don't think > Fred's suggestion for git bisect will work because I have to bisect fg, > sg and data and keep them in sync, so I reckon I will have to do the > binary chop manually. This is really a labour of love & curiosity, cos > all is ok on another more powerful m/c with nvidia graphics + 4 > monitors.
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 -- --------------------------------------------------------------------------- Anders Gidenstam WWW: http://gitorious.org/anders-hangar http://www.gidenstam.org/FlightGear/ ------------------------------------------------------------------------------ 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
