On Wed, 2012-09-05 at 15:06 +0100, Alasdair wrote:
> On Wed, 2012-09-05 at 15:47 +0200, Anders Gidenstam wrote:
> > On Wed, 5 Sep 2012, Alasdair wrote:
> >
> > > I have narrowed this problem down further.
> > >
> > > Comment out:
> > >
> > >Aircraft/c172p/Systems/instrumentation.xml
> > >
>
On Wed, 2012-09-05 at 15:47 +0200, Anders Gidenstam wrote:
> On Wed, 5 Sep 2012, Alasdair wrote:
>
> > I have narrowed this problem down further.
> >
> > Comment out:
> >
> >Aircraft/c172p/Systems/instrumentation.xml
> >
> > in c172p-set.xml
> >
> > Similarly
> >
> >
On Wed, 5 Sep 2012, Alasdair wrote:
> I have narrowed this problem down further.
>
> Comment out:
>
>Aircraft/c172p/Systems/instrumentation.xml
>
> in c172p-set.xml
>
> Similarly
>
>Aircraft/b1900d/Systems/instrumentation.xml
> -->
> in b1900
I have narrowed this problem down further.
Comment out:
Aircraft/c172p/Systems/instrumentation.xml
in c172p-set.xml
Similarly
Aircraft/b1900d/Systems/instrumentation.xml
-->
in b1900d-set.xml
and in the case of the SenecaII
On Tue, 2012-09-04 at 22:14 +0100, Alasdair wrote:
> On Tue, 2012-09-04 at 21:58 +0100, Alasdair wrote:
> > On Tue, 2012-09-04 at 22:34 +0200, Frederic Bouvier wrote:
> > > > >
> > > > > If you start FG with --log-level=debug --log-class=view
> > > > > you'll be able to see messages like :
> > > >
On Tue, 2012-09-04 at 21:58 +0100, Alasdair wrote:
> On Tue, 2012-09-04 at 22:34 +0200, Frederic Bouvier wrote:
> > > >
> > > > If you start FG with --log-level=debug --log-class=view
> > > > you'll be able to see messages like :
> > > >
> > > > FGEventHandler::handle: RESIZE event 763 x 1338, re
On Tue, 2012-09-04 at 22:34 +0200, Frederic Bouvier wrote:
> > >
> > > If you start FG with --log-level=debug --log-class=view
> > > you'll be able to see messages like :
> > >
> > > FGEventHandler::handle: RESIZE event 763 x 1338, resizable: 1
> > > FGRenderer::resize: new size 1338 x 763
> > >
> >
> > If you start FG with --log-level=debug --log-class=view
> > you'll be able to see messages like :
> >
> > FGEventHandler::handle: RESIZE event 763 x 1338, resizable: 1
> > FGRenderer::resize: new size 1338 x 763
> >
> > What are yours ?
> >
> > Regards,
> > -Fred
> >
> I see FGRenderer
>
> If you start FG with --log-level=debug --log-class=view
> you'll be able to see messages like :
>
> FGEventHandler::handle: RESIZE event 763 x 1338, resizable: 1
> FGRenderer::resize: new size 1338 x 763
>
> What are yours ?
>
> Regards,
> -Fred
>
I see FGRenderer::resize: new size 1904 x
> > > Here you go:
> > > https://dl.dropbox.com/u/15936159/fgfs-rem_rend_buffers_on.png
> > >
> > > You seem to be scenting the fox here, Fred
> > > Wish I knew what the rendering buffers tell you!
> >
> > The corners are rendered in a first pass in textures. These
> > textures
> > are resized wh
> > Here you go:
> > https://dl.dropbox.com/u/15936159/fgfs-rem_rend_buffers_on.png
> >
> > You seem to be scenting the fox here, Fred
> > Wish I knew what the rendering buffers tell you!
>
> The corners are rendered in a first pass in textures. These textures
> are resized when an event from OSG
> Here you go:
> https://dl.dropbox.com/u/15936159/fgfs-rem_rend_buffers_on.png
>
> You seem to be scenting the fox here, Fred
> Wish I knew what the rendering buffers tell you!
The corners are rendered in a first pass in textures. These textures are
resized when an event from OSG tells to, and
On Tue, 2012-09-04 at 18:52 +0200, Frederic Bouvier wrote:
> > On Tue, 2012-09-04 at 18:00 +0200, Frederic Bouvier wrote:
> > > > Can't think how to proceed from here though :-( Sigh!
> > > > As you and others have mentioned, the wxradar connection ought to
> > > > be
> > > > a clue, but I am not b
> On Tue, 2012-09-04 at 18:00 +0200, Frederic Bouvier wrote:
> > > Can't think how to proceed from here though :-( Sigh!
> > > As you and others have mentioned, the wxradar connection ought to
> > > be
> > > a clue, but I am not brainy enough anymore to follow it up,
> > > especially
> > > if invol
On Tue, 2012-09-04 at 18:00 +0200, Frederic Bouvier wrote:
> > Can't think how to proceed from here though :-( Sigh!
> > As you and others have mentioned, the wxradar connection ought to be
> > a clue, but I am not brainy enough anymore to follow it up, especially
> > if involves delving into OSG.
> Can't think how to proceed from here though :-( Sigh!
> As you and others have mentioned, the wxradar connection ought to be
> a clue, but I am not brainy enough anymore to follow it up, especially
> if involves delving into OSG.
If you are able to start Rembrandt, does it change anything ?
Reg
On Tue, 2012-09-04 at 15:40 +0100, Alasdair wrote:
> 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^ -
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
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
On Tue, 2012-09-04 at 12:07 +0100, James Turner wrote:
> On 4 Sep 2012, at 11:43, Alasdair wrote:
>
> > Further research shows that for the b1900d & SenecaII, this problem goes
> > way back to 2.6.0. It has only become apparent (in my case) for the
> > c172p in recent git pulls. I will attempt to
On 4 Sep 2012, at 11:43, Alasdair wrote:
> Further research shows that for the b1900d & SenecaII, this problem goes
> way back to 2.6.0. It has only become apparent (in my case) for the
> c172p in recent git pulls. I will attempt to find exactly when, but I am
> having to learn git as I go :-( Si
On Mon, 2012-09-03 at 21:32 +0100, Alasdair wrote:
> 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, 2
Hi Alasdair,
This tutorial on git bisect has references to Drupal but is otherwise very
clear:
http://webchick.net/node/99
You basically start from a known-good point, a known-bad one and then tell
git bisect if the next checkouts are good (no problem) or bad (show the
problem).
Each test require
On Mon, 03 Sep 2012 21:32:02 +0100, Alasdair wrote in message
<1346704322.26230.28.camel@executrix>:
> I cannot therefore attribute this problem to the Catalyst driver.
..one quick way to find out, is fetch a live usb distro, e.g. Debian
Live, (there's also Ubuntu, Knoppix etc) put it on an usb
On Mon, 2012-09-03 at 22:40 +0200, Frederic Bouvier wrote:
> > I cannot therefore attribute this problem to the Catalyst driver.
> > My git pull/build of 12 Aug did not display this problem. That of 1
> > Sep did. So I reckon it must have been a commit made between these dates.
>
> So you may want
On Mon, 2012-09-03 at 20:22 +0200, Geoff McLane wrote:
> 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 i
> I cannot therefore attribute this problem to the Catalyst driver.
> My git pull/build of 12 Aug did not display this problem. That of 1
> Sep did. So I reckon it must have been a commit made between these dates.
So you may want to "git bisect" to find which commit was the problem
Thanks,
-Fred
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 wrote:
> > On Mon, 2012-09-03 at 01:06
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 Cataly
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 wrote:
> On Mon, 2012-09-03 at 01:06 +0200, ThorstenB wrote:
>> > On Sun, Sep 2, 2012 at 11:31 AM, Alas
On Mon, 2012-09-03 at 01:06 +0200, ThorstenB wrote:
> > On Sun, Sep 2, 2012 at 11:31 AM, Alasdair 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 cor
> On Sun, Sep 2, 2012 at 11:31 AM, Alasdair 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, b
Please open a bug for this, if there is not one already (it sounds similar to
one existing issue), and include all the information below - especially when it
broke, OSG versions, graphics cards and so on.
Cheers,
James
On 2 Sep 2012, at 20:07, Alasdair wrote:
> On Sun, 2012-09-02 at 12:26
On Sun, 2012-09-02 at 12:26 -0600, syd adams wrote:
> Ive had this same issue for months now , on a laptop with ATI Mobility
> Radeon HD 4250.It only happens on some aircraft , but i havent really
> tried to hunt the problem down. Im suspecting a shortage of video
> memory . I also can get full scr
Ive had this same issue for months now , on a laptop with ATI Mobility
Radeon HD 4250.It only happens on some aircraft , but i havent really
tried to hunt the problem down. Im suspecting a shortage of video
memory . I also can get full screen by changing the window size , but
any dialog or text on
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.
36 matches
Mail list logo
