Jim Wilson writes:
> The problem with the 2D panel mapped to the cockpit had been there
> since Andy added that capability...but now I don't see it anymore.
> I'm sure it was there fairly recently, within the last month
> anyway. Are you seeing it with current code David?
It shows up when y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Has anyone thought of using bugzilla to keep track of bugs and suggestions for
FlightGear? If no one else wants to, I could administer it, since I seem to
have no time to code these days. Thanks,
David
- --
If you give someone a program, you will
Dave,
On a Geforce3 and a GeForce4 Ti4200 I have
observed that FSAA works fine, except when I try to exit FlightGear,
my entire machine locks up. On GeForce2, you can't FSAA at
resolutions over 800x600 I believe ... and I'll take 1600x1200
over 800x600 FSAA any day ...
The Geforce3/4 behavior
Geoff Reidy writes:
> The major problem I have with fgfs is that I seem to hit a race
> condition where all graphics and sound stop for extended periods of time
> (up to about 30 secs), long enough for autopilot (or me!) to lose
> control and the plane will always crash.
> During this time there i
Curtis L. Olson
> Geoff Reidy writes:
> > The major problem I have with fgfs is that I seem to hit a race
> > condition where all graphics and sound stop for extended periods of time
> > (up to about 30 secs),>
> This most likely relates to freeing tile memory (i.e. moving old tiles
> out of the
Norman Vine writes:
> The same thing happens for me with both Cygwin gcc 2.95.2
> and MingW gcc 3.2 both using Doug Lea's malloc routines which
> I believe is what most Linux distributions use
>
> CVS version of Cygwin
>
> Implemeting the thread support seems to make this even worse
> but this i
Norman Vine
>
> CVS version of Cygwin
AACK
CVS version of FGFS
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Curtis L. Olson writes:
> Norman Vine writes:
> > The same thing happens for me with both Cygwin gcc 2.95.2
> > and MingW gcc 3.2 both using Doug Lea's malloc routines which
> > I believe is what most Linux distributions use
>
> It might be worth verifying that my partial tile free-er routine i
Jim Wilson wrote:
> The problem with the 2D panel mapped to the cockpit had been there
> since Andy added that capability...but now I don't see it anymore.
> I'm sure it was there fairly recently, within the last month anyway.
> Are you seeing it with current code David?
It's related to depth buf
Norman Vine writes:
> Curtis L. Olson writes:
>
> > Norman Vine writes:
> > > The same thing happens for me with both Cygwin gcc 2.95.2
> > > and MingW gcc 3.2 both using Doug Lea's malloc routines which
> > > I believe is what most Linux distributions use
> >
> > It might be worth verifying th
Curtis L. Olson
> Norman Vine writes:
> >
> > FWIW - I ended up assuming that my poor little 256 meg machine
> > just wasn't big enough to run FGFS anymore under Windows as it
> > appears to be memory related disk thrashing that is killing me.
>
> Another test would be to disable the random gro
I know this is probably opening a can of worms, but I just thought I'd
throw this out to the list now so people could start thinking about
and/or discussing the issues.
Currently SimGear is a set of libraries, each of which is licensed
under the *L*GPL.
FlightGear is also mostly a set of librari
I don't see a real benefit of changing FGFS from GPL to LGPL ...
* The people who don't like GPL probably aren't much happier about LGPL
* They (or we) can add a shared-memory tunnel in SimGear for properties
* Most proprietary extensions can simply coexist as separate programs
Anything that make
I thought about LGPL for JSBSim, and IIRC Tony and others
were agreeable to that and also had been thinking of that
- Tony, correct me if I am wrong. I think it makes a lot
of sense. If we are still agreeable to that, I think we
can go that route at any time.
Jon
* [EMAIL PROTECTED] (Curtis L. Olson) [2002.10.15 15:24]:
> I know this is probably opening a can of worms, but I just thought I'd
> throw this out to the list now so people could start thinking about
> and/or discussing the issues.
Oh, great. This could turn into the flamewar of the year... :-
Alex Perry wrote:
> I don't see a real benefit of changing FGFS from GPL to LGPL ...
> * The people who don't like GPL probably aren't much happier about LGPL
> * They (or we) can add a shared-memory tunnel in SimGear for properties
> * Most proprietary extensions can simply coexist as separate pr
For what it's worth, I did a high speed taxi down the same runway in
the JSBSim C172. At the same point on the runway, the C172 takes a
hard bounce, goes almost completely nose down vertical, but recovers
without "crashing". I don't see any visual discontinuity, so I assume
this must be a proble
On Tue, Oct 15, 2002 at 03:22:02PM -0500, Curtis L. Olson wrote:
>
> - If we wanted to tweak the licensing terms for the FlightGear
> project, could we? Who has authority to do this. If we can get
> most authors/contributors to agree, is that good enough? Do we need
> approval from 100%
Curtis L. Olson writes:
> I dumped out the ground elevation as I went over the anomoly and
> here's what I get:
> elev = 164.032
> elev = 166.037
Curtis L. Olson writes:
> I know this is probably opening a can of worms, but I just thought I'd
> throw this out to the list now so people could start thinking about
> and/or discussing the issues.
>
> Currently SimGear is a set of libraries, each of which is licensed
> under the *L*GPL.
Norman Vine wrote:
> Curtis L. Olson writes:
>
> > Could the hitlist code be overly aggressive on what it's caching
> > internally?
>
> Maybe - should be easy enough to back out almost all of the
> modifications as I do not believe that the Interface ever changed
> much
Oh yea - there is an i
i get a crash trying to fly the a4-yasim out of toronto's pearson
international airport (CYYZ). this is the backtrace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 23176)]
SGPropertyNode::getDoubleValue (this=0x0) at props.cxx:1117
1117 if (_attr == (RE
On Tue, 15 Oct 2002 23:02:09 +1000
David Findlay <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Has anyone thought of using bugzilla to keep track of bugs and suggestions
> for FlightGear? If no one else wants to, I could administer it, since I seem
> to have no
Alex Romosan writes:
> i get a crash trying to fly the a4-yasim out of toronto's pearson
> international airport (CYYZ). this is the backtrace:
Which runway? What altitude at the time of the crash? Which scenery
distro? I'll see if I can reproduce.
All the best,
David
--
David Meggins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 16 Oct 2002 08:19 am, Bernie Bright wrote this piece of wisdom:
> We already have that facility on sourceforge but its hardly ever used.
Well maybe it needs to be setup, and linked on the press releases and front
page of the website, so peop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 16 Oct 2002 08:19 am, Bernie Bright wrote this piece of wisdom:
> We already have that facility on sourceforge but its hardly ever used.
BTW I think Bugzilla, with a KDE style bug reporting wizard would be more
powerful for tracking these th
David Megginson <[EMAIL PROTECTED]> writes:
> Alex Romosan writes:
>
> > i get a crash trying to fly the a4-yasim out of toronto's pearson
> > international airport (CYYZ). this is the backtrace:
>
> Which runway? What altitude at the time of the crash? Which scenery
> distro? I'll see if
Alex Romosan <[EMAIL PROTECTED]> writes:
> the default runway i guess. fgfs doesn't even run (it crashes during
> initialization). i suspect some problem with the radio frequencies for
> CYYZ. the scenery is the standard one downloaded from flightgear.org
> and everything else is the latest from
Alex Romosan writes:
> the default runway i guess. fgfs doesn't even run (it crashes during
> initialization). i suspect some problem with the radio frequencies for
> CYYZ. the scenery is the standard one downloaded from flightgear.org
> and everything else is the latest from CVS.
Yes, I'm g
At first glance it appears that the radio stack is being created,
init'd and bound before the electrical subsystem. This means that
properties in the electrical system that the radio stack expects, are
not there yet. It seems like an initialization order problem although
I don't understand why i
Curtis L. Olson writes:
> At first glance it appears that the radio stack is being created,
> init'd and bound before the electrical subsystem. This means that
> properties in the electrical system that the radio stack expects, are
> not there yet.
That shouldn't matter, though, as long as
Errr, not exactly, but my fault. Should be fixed now in cvs.
Regards,
Curt.
David Megginson writes:
> Curtis L. Olson writes:
>
> > At first glance it appears that the radio stack is being created,
> > init'd and bound before the electrical subsystem. This means that
> > properties in th
On Tue, 15 Oct 2002 17:37:32 -0400,
David Megginson <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
>
> My opinion is already on the record, so I'll just restate it quickly:
> I prefer Public Domain to LGPL (and LGPL to GPL), both because it
> makes it easier for companies to use the c
Norman Vine writes:
> Oh yea - there is an indexing bug in the FAST TRISTRIP logic that
> somehow never got changed even though the fix was in several of
> my submissions
For what it's worth, separating out individual concepts into separate
patch submissions makes things a lot easier and simple
Arnt Karlsen writes:
> .."public domain" equals "the author drops or donates his copyright
> to the public domain"?
It means that the work is released into the public domain. There is
no donation, because no one owns (or can own) copyright on their
original work, though people can copyrig
I figured David would have said something by now, but Blender was
open-sourced a couple days ago. This is great news for the open-source
community (ie. "us"). Go check it out:
http://www.blender.org/
Feel free to write some tutorials for us modelling newbies. ;-) Thanks
--
Cameron Moore
[
Yes, you can use plugins and scripts to load obj, 3ds,...
Marcio Shimoda
- Original Message -
From: dominic stadden
To: [EMAIL PROTECTED]
Sent: Sunday, October 13, 2002 7:07 AM
Subject: [Flightgear-devel] Help
Hi, is it possible to load non gmax .mdl files into gmax. Sorry this message
FWIW, the turn coordinator ball behaves *very* differently between
JSBSim and YASim and another FDM I am playing with. All supposedly
return accelerations in body axis in ft/sec squared. This means we
can't create a single turn coordinator instrument who's ball behaves
reasonably well for every
James A. Treacy writes:
> You should get as close to 100% of the contributors to agree as you
> can get. Flightgear needs to be prepared to remove any code written by
> someone who disagrees or who couldn't be contacted and appears later
> on.
>
> FWIW, wine did this earlier this year and they go
> Arnt Karlsen writes:
> > .."public domain" equals "the author drops or donates his copyright
> > to the public domain"?
See the article in Linux Journal recently. You legally cannot place
anything into the public domain, you merely get to assert that the
licensing you are assigning to yo
> FWIW, the turn coordinator ball behaves *very* differently between
> JSBSim and YASim and another FDM I am playing with. All supposedly
> return accelerations in body axis in ft/sec squared. This means we
> can't create a single turn coordinator instrument who's ball behaves
> reasonably well
On Tue, Oct 15, 2002 at 11:15:08PM -0500, Curtis L. Olson wrote:
> Question: for a particular source file, if a person contributed a
> minor patch or tweak to compile on a new platform, does that person
> now have a "full" say in the future of that source, or are they giving
> their changes to the
42 matches
Mail list logo
