On 09/05/2012 07:50 AM, Michael wrote:
> No, FlightProSim and whatever they're called.
>
> I still think we need another license for sceneries etc. Anything but code
> should be possible to license similar to GPL, but not allowing any
> commmercial use.
Disallowing commercial use means Linux dis
> I still think we need another license for sceneries etc. ... not allowing any
> commmercial use.
Why? Freedom Zero matters just as much for things other than code.
-- Chris
--
Live Security Virtual Conference
Exclusiv
No, FlightProSim and whatever they're called.
I still think we need another license for sceneries etc. Anything but code
should be possible to license similar to GPL, but not allowing any commmercial
use.
Only change/add this to gpl, rename it flightgear scenery license or whatever.
Dual licens
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
Nikolay Tychina wrote:
> FreeBSD was relatively recent 9-STABLE, yesterday I upgraded it to
> 9.1-PRERELEASE #0 r240025.
Which port of FLTK is installed, 1.3 or 2 ?
I've recently built the flightgear port successfully on 9.something,
therefore I'd rather expect some remains of an old FLTK or Ruby
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
> Hi!
>
> > Which version of FreeBSD ? Do you have BATCH enabled in make.conf ?
> > Are
> > you sure your port dependencies are up to date ? Do you have any
> > other
> > custom rules defined in make.conf ?
> >
> > Cheers,
> > Martin.
>
> FreeBSD was relatively recent 9-STABLE, yesterday
Hi!
> Which version of FreeBSD ? Do you have BATCH enabled in make.conf ? Are
> you sure your port dependencies are up to date ? Do you have any other
> custom rules defined in make.conf ?
>
> Cheers,
> Martin.
FreeBSD was relatively recent 9-STABLE, yesterday I upgraded it to
9.1-PRERELE
> > 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
Nikolay Tychina wrote:
> I'm trying to build a port of FlightGear 2.6.0 on FreeBSD, and it
> fails with the same error every time. What can possibly cause it?
Has the problem already been solved ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
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
24 matches
Mail list logo
