The problems people have with the xBSD have nothing to do with FGFS.
Once you've got all the dependencies (i.e. GL, PLIB, MK, etc) working,
You might get in trouble with some graphics boards that are not supported by
XFree86/DRI. I know that there is a project to build something that is
FWIW on a SuSE 7.3 system I had to downgrade (install parallel actually)
autoconf. Just pointing out SuSE needed a little tweak too.
I would'nt call it that way. Autoconf on SuSE-7.3 works pretty nice. The
only tweak is that you have to run 'aclocal' with '-I .'. I know this
because I do build
I'd like to define a new airport. How can I do that ? Is there any paper
talking about it ?
There is FlightGear/docs-mini/AptNavFAQ.FlightGear.html with lots of useful
information but I have the impression that you need to regenerate scenery at
this location to include the new airport.
Hello,
what's wrong with using
#include assert.h
...
assert(some_condition);
instead of that Null Pointer assignment?
Regards,
Nicolai
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
David wrote:
Wolfram mentioned that GMAX-exported models don't work with PLIB
anyway.
Yes, you can not load the gmax generated MDLs. You can try to use
Quake models as intermdediary file or maybe with Middleman
http://takeoff.to/landing
you could get an *.x file. I have not had time to try
Alex Perry wrote:
http://www.suse.com/us/products/suse_linux/i386/games.html
nearly the same text as for 7.3:
http://www.suse.com/us/products/suse_linux/73/games.html
CU,
Christian
--
The idea is to die young as late as possible.-- Ashley Montague
Whoever that is/was; (c) by
http://www.suse.com/us/products/suse_linux/i386/games.html
Yep, I've been pushing them a bit to make a build of the new release of
FlightGear :-)
Unfortunately this will not include all the nice stuff that went in in the
meantime (c310 crashes on gear retraction ;-). I'll figure out how
William Earnest writes:
In file included from
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../.
./include/g++-3/iostream.h:31,
This doesn't look good -- somehow, include files from G++ 2.95.2 and
G++ 3.0 seem to be getting mixed up.
All the best,
David
--
David Megginson
Jim Wilson writes:
If I was going to add blinking lights to the model animation code,
how would I do the timing?
This is still on my TODO list, together with LOD and other conditional
hiding and showing. Were you thinking of blinking by swapping
objects, or by changing colour/texture?
Greg Long writes:
My question is primarily this: Other that personal preference, is there
any major need to install Debian over RedHat Linux 7.2 for FlighGear
development? I notice the gcc issue in the FAQ, but I should be cool on
that with 7.2, though I'll check.
I think that we have
Sergio Roth writes:
I'd like to define a new airport. How can I do that ? Is there any paper
talking about it ? Is there any place where we can get coordinates of all
airports around the world ?
The airports are defined in $FG_ROOT/Airports/default.apt.gz, but they
don't appear on the
Alex Perry writes:
Fair enough. I certainly overengineered props.[ch]xx, in anticipation
of all kinds of sophisticated stuff that people never bothered doing.
I've been learning, slowly, from the XP people to build only for today
(all my training previously was to anticipate future
Alex Perry writes:
Can we patch the sgdPointInTriangle back to PointInTriangle
_and_ keep the improvements from Norman in the tree ?
I think we just need to #ifdef for the PLIB version.
All the best,
David
--
David Megginson
[EMAIL PROTECTED]
Michael Selig writes:
I am wondering does the view manager work-in-progress support a simple
tower view at this stage? Having gone from our non-CVS tower view in 0.7.8
to a recent CVS checkout leaves me wishing for more.
Jim Wilson is working on the rewrite. We do plan to support
Michael Selig writes:
That would be nice, but even something simple that puts the viewpoint 200
ft above the runway behind the aircraft would be great to start with. That
view is a help when building and testing the new aircraft models. It also
makes the sim well-primed for R/C use.
Norman Vine wrote:
Erik Hofman writes:
Norman Vine wrote:
I'd better just go back into lurk mode I guess
Preferably not. The code improves the framerate by a factor which you
meantioned earlier, but also makes the framerate quite steady.
So you must have done something right!
The
Jonathan Polley writes:
I have made an attempt to describe the contents of 'preferences.xml.'
Could someone knowledgeable in the properties list and preferences.xml
file let me know if I am understanding things correctly? Also, is there
any information about what each component of
David Megginson wrote:
Michael Selig writes:
I am wondering does the view manager work-in-progress support a simple
tower view at this stage? Having gone from our non-CVS tower view in 0.7.8
to a recent CVS checkout leaves me wishing for more.
Jim Wilson is working on the
Erik Hofman writes:
I'm realy impressed by the effect of the code. The higher I get, the
higher the framerate! This makes me believe we could actually enlarge
the view range when getting at a higher altitude.
Cool glad it works for you
but IMHO what is needed are imposter tiles
imposters
Erik Hofman writes:
I'm realy impressed by the effect of the code. The higher I get, the
higher the framerate! This makes me believe we could actually enlarge
the view range when getting at a higher altitude.
This would be really nice for very high flying (X) aircraft.
Jon
David Megginson writes:
One thing that has impressed me about Andy Ross's code over most of
the rest of FlightGear (including any of my own contributions that I
haven't looked at for a few months) is that I was able to understand
most of his code immediately. Part of that is because he uses
David Megginson writes:
For the record, I don't agree with the XP people on team programming
Hopefully you will eventually come to embrace that concept too. :-)
Cheers
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
On Sun, 17 Mar 2002, David Megginson wrote:
I think that we have many RedHat users working with FlightGear, so
there should be no problem. We'll convert you to Debian some other
time.
distro holy war
At this point I'll just add that Slackware users don't have any problems -
it flightgear is
Curtis L. Olson writes:
I know you are making a point by using extereme wording, but if you
are running through the woods, it doesn't hurt to look up once in a
while.
I preached full interface design in advance through much of the 1990s
-- it seemed like a good idea. I now freely
This is where we disagree -- keeping it in makes the code much harder
for new (and existing) contributors to read and understand, gives
false hits when searching for variables and method calls, etc. etc.
With CVS, it's trivially easy to look at or restore old code later if
we need to; I'm
Just to start, the property tree has nothing to do with Metakit -- we
use Metakit only to hold airport and navaid data.
I will make that change.
path Aircraft/c172/Panels/c172-vfr-panel.xml/ path
This tells FlightGear where it can find the configuration
information for
Some of the other XML files are rather easy to figure out (i.e,. keyboard.
xml), but others are not (i.e., the FDM specific files). Does anyone have
anything written that describes these? The materials.xml file has quite a
nice description at the top.
Can you let us know what is unclear in
I might go ahead and give Debian a shot on the install, seems like the
distro of choice, and I have a separate Redhat box (233mhz, don't think
its S3 Virge supports OpenGL, I'd have to look) but I could use that for
testing Debian seems to be the choice by large, and if it supports
rpm's I might
I forgot to say that Debian must REALLY hide their ISO's - I had to get
these from www.linuxiso.org
Hopefully they boot OKburning ISO #1 right now.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Greg Long
Sent: Sunday, March 17, 2002 8:24 AM
To:
Jonathan Polley writes:
Some of the other XML files are rather easy to figure out
(i.e,. keyboard. xml), but others are not (i.e., the FDM specific
files).
YASim and JSBSim each uses its own XML format, which is different from
the XML format used by the rest of FlightGear. For YASim,
Jon Berndt writes:
Elimination of dead code (as we all know, CVS is really good for
tracking past changes) and better documentation would be really
helpful. We'd like to be better in JSBSim too - we all face this.
Absolutely. While I don't tend to keep #ifdef's around, some of my
code is
Michael Selig [EMAIL PROTECTED] said:
That would be nice, but even something simple that puts the viewpoint 200
ft above the runway behind the aircraft would be great to start with. That
view is a help when building and testing the new aircraft models. It also
makes the sim well-primed
Greg Long writes:
I might go ahead and give Debian a shot on the install, seems like the
distro of choice, and I have a separate Redhat box (233mhz, don't think
its S3 Virge supports OpenGL, I'd have to look) but I could use that for
testing Debian seems to be the choice by large, and
On Sunday, March 17, 2002, at 09:53 AM, Jon Berndt wrote:
Some of the other XML files are rather easy to figure out (i.e,.
keyboard.
xml), but others are not (i.e., the FDM specific files). Does anyone
have
anything written that describes these? The materials.xml file has quite
a
On Sun, 2002-03-17 at 09:22, David Megginson wrote:
Greg Long writes:
I might go ahead and give Debian a shot on the install, seems like the
distro of choice, and I have a separate Redhat box (233mhz, don't think
its S3 Virge supports OpenGL, I'd have to look) but I could use that for
I forgot to say that Debian must REALLY hide their ISO's - I had to get
these from www.linuxiso.org
Hopefully they boot OKburning ISO #1 right now.
That's because nobody pays them for the bandwidth. They'd rather you use
someone else's bandwidth, or borrow a CD from someone else, or buy
If the page being shown does not show the #ifdef, it can be really
confusing. I can't recall any specific examples of this in the code, but I
remember being bitten by this kind of thing a couple of times when perusing
some of the base FlightGear code.
Some of it is simply people being
Erik Hofman [EMAIL PROTECTED] said:
Talking about views.
Currently when looking around in the cockpit you turn around a single
point (if I recall it correctly). Wouldn't it be nessercary to actually
incoorporate the eye distance from the middle of the head into that
action (and limit
At 3/17/02, you wrote:
Michael Selig writes:
I am wondering does the view manager work-in-progress support a simple
tower view at this stage? Having gone from our non-CVS tower view in
0.7.8
to a recent CVS checkout leaves me wishing for more.
Jim Wilson is working on the rewrite.
On Sat, 16 Mar 2002 18:15:41 -0500,
William Earnest [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Hello,
Wound up rearranging some hardware, and am trying to move
FlightGear to a faster machine. Sytem is based on RH-7.1 as was
the previous, but with a
Norman Vine writes:
IMHO the biggest obstacle to reading and developing FGFS code
is the formatting
We really need a mechanical formating means that is acceptable to every
one as the CVS standard even if it is not perfect or even close to what one
would personally use.
When I've looked,
David Megginson writes:
I disagree that this is the biggest obstacle (or even one of the top
10), but then, I use an editor (XEmacs) with syntax highlighting,
brace matching, language-based navigation (jump forward one function),
etc., so those features might be hiding the problem from me.
Curtis L. Olson [EMAIL PROTECTED] said:
If something doesn't make sense, or seems out of place, there's no
harm in asking ... perhaps the author will look at the 'cruft' and say
oh yea, nothing valuable there, we can axe it. But perhaps the code
is there is for valid reasons and it's worth
Curtis L. Olson writes:
I'd be happy if somewone could find a decent code [re]formatter that
gave us enough flexibility to make our own style choices and didn't
have glaring ommission or do really stupid things.
astyle is the only 'free' beautifier I know of that does a reasonable
job on c++
Norman Vine [EMAIL PROTECTED] said:
I realize that this is a 'religous' issue and a 'tough' problem but IMHO
it is a major obstacle to FGFS code evolution
It is a tough problem to solve, but I haven't found it to be much of a problem
reading fgfs code (have seen much worse). Maybe I'm not
Jim Wilson writes:
From where I sit, I'd have to agree more with David. There should be no cruft
left in the code that gets committed. This doesn't mean individual developers
can't keep it around on there local drive, but once something is good enough
to commit it should contain working
Norman Vine writes:
Curtis L. Olson writes:
I'd be happy if somewone could find a decent code [re]formatter that
gave us enough flexibility to make our own style choices and didn't
have glaring ommission or do really stupid things.
astyle is the only 'free' beautifier I know of that does
Melchior FRANZ [EMAIL PROTECTED] said:
* Jim Wilson -- Sunday 17 March 2002 19:09:
Interesting note, the top item on the list, Racer is not GPL or
anything
close to opensource ( see http://www.racer.nl/legal.htm ). It also
uses the
fmod lib for sound...which is imho overkill for a race
Curtis L. Olson writes:
One thing we'd need to think about before we got too far down this
path is the texture RAM requirements of such a scheme.
They should be minimal. For the first tier of imposter tiles, we're
using textures that we already have, and just replacing the tile with
a
Curtis L. Olson [EMAIL PROTECTED] said:
positive... we really go no where when we are busy flaming each other
and there has been really too much of that going on lately.
On that note I propose we dump this thread (known as: ARGG!) now and
continue the discussion under different heading
Jim Wilson writes:
From where I sit, I'd have to agree more with David. There should
be no cruft left in the code that gets committed. This doesn't
mean individual developers can't keep it around on there local
drive, but once something is good enough to commit it should
contain
David Megginson writes:
Curtis L. Olson writes:
One thing we'd need to think about before we got too far down this
path is the texture RAM requirements of such a scheme.
They should be minimal. For the first tier of imposter tiles, we're
using textures that we already have, and just
David Megginson writes:
Perhaps we should stick three
files in every code directory: a README file, explaining what the code
in the directory does, a PLANS file, where we can put ideas for future
interfaces, and an ATTIC file, where we can paste old code we might
need again some day. When
I'd like to experiment flying under San Jose photo scenary. I've already
downloaded the package but I don't know how to start it. Anyone coul'd
help
me ?
If you look at the contents, there is one directory.
Simply put it all in the same directory that currently has a KSJC* file in
it.
* [EMAIL PROTECTED] (Alex Perry) [2002.03.18 12:14]:
Alex Perry writes:
Yeah, but I'm running PLIB from CVS and I've now got a nameclash.
Norman replied:
#if 0
//code that clashes
sgdIsectInfLinePlane()
sgdPointInTriangle()
#endif //0
Err, yeah, sarcasm I can do that
Well that install sucked. No Geforce2 support even - much easier to just
go with RedHat7.2 for now. :)
7.2 should have the gcc update that 7.0 didn't have but I'll check it if I
have any trouble.
On 2002.03.17 00:57 Martin Spott wrote:
FWIW on a SuSE 7.3 system I had to downgrade (install
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 18 Mar 2002 07:42, you wrote:
Well that install sucked. No Geforce2 support even - much easier to just
go with RedHat7.2 for now. :)
It does support it, you've just got to load the driver after install. But
Debian probably isn't the
Greg Long writes:
Well that install sucked. No Geforce2 support even - much easier to just
go with RedHat7.2 for now. :)
7.2 should have the gcc update that 7.0 didn't have but I'll check it if I
have any trouble.
Strange, I had no problem at all with any of my Debian installations
and
You're really better off doing a network install if at all possible.
Just download a couple of floppies and you're ready to go.
On Sunday 17 March 2002 11:32 am, you wrote:
I forgot to say that Debian must REALLY hide their ISO's - I had to get
these from www.linuxiso.org
Hopefully they
On Sunday 17 March 2002 02:12 am, you wrote:
http://www.suse.com/us/products/suse_linux/i386/games.html
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Gaaah! What an ugly old
(Regarding the Debian install) Options are nice during install, no argument
here. And I realized I could install the driver after the fact, I just
decided that with limited time, it wasn't worth investing the time in the
direction of figuring out another distro - absolutely nothing against
On Sunday 17 March 2002 03:57 am, you wrote:
FWIW on a SuSE 7.3 system I had to downgrade (install parallel actually)
autoconf. Just pointing out SuSE needed a little tweak too.
I would'nt call it that way. Autoconf on SuSE-7.3 works pretty nice. The
only tweak is that you have to run
Curtis L. Olson writes:
If you are willing to setup these files and keep them from getting too
far out of date, then this sounds like a reasonable proposal to me.
I don't mind setting up the READMEs. The others will be set up as
needed.
All the best,
David
--
David Megginson
[EMAIL
One of the main goals we would like to work on is Martian
terrain. I'm not
sure how much of the Earth's parameters are hard coded, but I'm imagining
it shouldn't be TOO difficult to produce Mars scenery for the sim. I have
done it a little bit with MS's Flight Sim, and the initial results
Curtis L. Olson writes:
That's one valid knock against Linux in general ... knowing how to
admin one distribution doesn't necessarily help you a bit with other
distributions.
That's a bit of an exaggeration. There are quirks -- Debian uses
/etc/rc?.d while RedHat adds another level, or
On Sun, 17 Mar 2002 07:27:07 -0500,
David Megginson [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Alex Perry writes:
Fair enough. I certainly overengineered props.[ch]xx, in
anticipation of all kinds of sophisticated stuff that people
never bothered doing. I've been
Interesting note, the top item on the list, Racer is not GPL or anything
close to opensource ( see http://www.racer.nl/legal.htm ). It also uses
[...]
Yep, the also ship near to commercial software with their distribution - at
least on CD-ROM. Anyway you will find such sort of software on
David Megginson writes:
Curtis L. Olson writes:
That's one valid knock against Linux in general ... knowing how to
admin one distribution doesn't necessarily help you a bit with other
distributions.
That's a bit of an exaggeration. There are quirks -- Debian uses
/etc/rc?.d while
Interesting note, the top item on the list, Racer is not GPL or anything
close to opensource ( see http://www.racer.nl/legal.htm ).
I totally forgot Are you (Alex) using an Nvidia graphics board ? O.k.,
as I remember you do not. But many pople on this list do. So there seems to
be very
Jon Berndt [EMAIL PROTECTED] writes:
I ran into this problem when looking through FlightGear code in the past.
It's hard to keep track of things like:
#ifdef xxx
200 lines of code
#else
100 lines of code
#endif
If you happen to be using Emacs (available on Windows, the various
On Sun, 17 Mar 2002 14:03:31 -0500,
Norman Vine [EMAIL PROTECTED] wrote in message
001801c1cde6$6f3e2380$a300a8c0@nhv:
hence my suggestion to find a set of settings for one of the
'beautifiers' that the code is run through, this way everyone can work
on the code formatted in their prefered
On Sun, 17 Mar 2002 13:42:32 -0800,
Greg Long [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
7.2 should have the gcc update that 7.0 didn't have but I'll check it
if I have any trouble.
..beware, there are 2 gcc's in RH72:
[arnt@lana arnt]$ rpm -q gcc gcc3
gcc-2.96-98
gcc3-3.0.4-1
On Sunday 17 March 2002 02:12 am, you wrote:
http://www.suse.com/us/products/suse_linux/i386/games.html
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Gaaah! What an ugly
I have completed my instrumentation of preferences.xml and I need someone
who knows that file to give it a sanity check. I do have some of
questions:
What description should I have for:
unitsfeet/units
trimtrue/trim
For entries such as:
has-gs-needle1/has-gs-needle
I had been concerned
that SGPropertyNode::getDoubleValue was showing up at the top of the
profiling output for JSBSim, but I think that that was masking the
object methods it was invoking in other JSBSim code.
Could very well be.
properties, but not much for anything else. The biggest
Jim Wilson [EMAIL PROTECTED] wrote:
Heh don't laugh. At LWCE Borland was giving away Kylix which is basically
delphi ported to linux...and if i'm not mistaken that uses something like
turbo pascal as its language. It's what they call a RAD tool. Or is it a
RAG (rapid atrocity generation)
David Megginson wrote:
The biggest surprise was that inlining methods made things slower, not
faster, in most cases (there were a couple of exceptions). That may
be a quirk of G++'s code generation, but it's probably worth
considering -- I had inlined much of the infrastructure to try to
Nicolai Czempin wrote:
what's wrong with using
#include assert.h
...
assert(some_condition);
instead of that Null Pointer assignment?
What null pointer assignment? Old news.
This got covered, but I'll turn the question around: what does
assert.h do that a crash doesn't? My way
Hi,
FWIW:
while I've been working mostly with the glass
displays, now and then I'll bring up the "steam gauges" panel. I finally see why
the artifical horizon looked funny to me. All the ADI's that I'm aware of have
the bank index marks fixed relative to the panel or instrument frame which
Curtis L. Olson wrote:
One thing we'd need to think about before we got too far down this
path is the texture RAM requirements of such a scheme.
That's a manageable problem. If you think about it, the amount of
impostor texture memory required is exactly that required to draw the
tiles on
80 matches
Mail list logo
