Hi Alasdair, I also do not think it is OS related, since I have seen this 'sometimes' in Windows 7 64-bit, with AMD Radeon HD 7700 Series with (I hope) the latest Catalyst driver!
At the time I thought little of it since it seemed to go away a few seconds later... by itself... In the Catalyst Control Center it shows a Driver Package Version 8.961-120405a-137813C-ATI, Catalyst Version 12.1, dated 29-Feb-2012... Hmmm, contrary to last time I checked for updates, it does now report a later Catalyst version 12.8 available... will download and try that... Now shows driver 8.982-120727a-145524C-ATI in Catalyst 12.8, dated today... Just tried FG 2.8.9.4 with 777-200 and no problem, but as indicated it only happened 'sometimes' and was never able to isolate the specific scenario that caused it... maybe as you indicate it is a/c specific... Found any reason why adding the radar to the aircraft made it go away... Will keep testing with different aircraft... Regards, Geoff. On Mon, 2012-09-03 at 09:39 -0600, syd adams wrote: > Im running Ubuntu , still get that problem.I've added the radar to my > intrumentation file in my affected aircraft , and the problem is > gone.Strange. > Syd > > On Mon, Sep 3, 2012 at 2:23 AM, Alasdair <ali...@btinternet.com> wrote: > > On Mon, 2012-09-03 at 01:06 +0200, ThorstenB wrote: > >> > On Sun, Sep 2, 2012 at 11:31 AM, Alasdair <ali...@btinternet.com> wrote: > >> >> After git pull (sg,fg,fgdata) a couple of days ago, I was presented > >> >> with a > >> >> strange screen which I had not seen before. My regular was shown as a > >> >> sub-screen in the bottom-left corner. Clicking the maximise widget > >> >> restores > >> >> full screen, but any click on a menu item returns me to this stupid > >> >> screen. > >> >> Is this infuriating behaviour deliberate, or has my graphics driver gone > >> >> walk-about? > >> >> > >> >> https://dl.dropbox.com/u/15936159/fg_quarter-screen.png > >> > >> Unfortunately a long standing issue. This affects ATI graphics cards > >> when running newer drivers. It can be "fixed" by reverting to an older > >> ATI driver (see link below). To me it looked like a genuine OSG or ATI > >> driver bug (the size of the graphics view port doesn't properly resize > >> to the size of the window), but it's likely triggered by something > >> "special" we're doing in FG, since other applications don't seem to have > >> this issue. > >> > >> Also, it's timing-/sequence dependant: it only affects certain aircraft > >> (aircraft using wxradar, which changes/delays the OSG init sequence on > >> startup, are less likely to have the issue) - and for some people it > >> dis- and reappears with certain FG builds. > >> > >> It would be really good if someone seeing the issue locally could > >> properly debug this - even if it means digging into OSG - since a larger > >> number of people are affected. I tried "remote debugging" this a while > >> ago, but gave up after being unable to narrow it down inside FG. Maybe > >> someone else has better luck. > >> > >> For more see here: > >> http://code.google.com/p/flightgear-bugs/issues/detail?id=385 > >> > >> cheers, > >> Thorsten > >> > > Thanks very much for the link, Thorsten, it is a good start. But strange > > that this problem, should just appear without any driver change. But I > > am using Debian SID, and update my system daily, so it could be > > OS-related. > > I will install UBUNTU and try the same build under that OS. > > > > regards, > > 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