I have found the same problems. I think it is related to using gcc 3.2 on recent
cygwin.
gcc 3.2 doesn't look in /usr/local/* by default, so you need to add it manually (set
CXXFLAGS and LDFLAGS appropriately). There must be a simpler and more automated
solution, but my knowledge of the auto
On Saturday, February 15, 2003, at 11:19 pm, Jim Wilson wrote:
The two possible options that come to mind are as follows:
1) Use the current 3D Modeling system.
2) Take code from the opengc project and change it so that it gets data
directly off our property system (property paths
I have found the same problems. I think it is related to using
gcc 3.2 on recent cygwin.
Thanks, Richard, good to know it's not just my fault.
gcc 3.2 doesn't look in /usr/local/* by default, so you need to
add it manually (set CXXFLAGS and LDFLAGS appropriately). There
must be a simpler
Jim Wilson wrote:
Recently I've been looking at potential solutions to doing a glass cockpit
display in flightgear. The 2D panel system just doesn't provide anywhere near
the functionality to do it, so I've pretty much decided that isn't an option.
The two possible options that come to mind are
Michael Basler wrote:
I have found the same problems. I think it is related to using
gcc 3.2 on recent cygwin.
Thanks, Richard, good to know it's not just my fault.
gcc 3.2 doesn't look in /usr/local/* by default, so you need to
add it manually (set CXXFLAGS and LDFLAGS appropriately).
://www.a1.nl/~ehofman/fgfs/download/SimGear_remove_cout-20030217.diff
David, can you apply it to SimGear?
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Erik,
Why should configure automatically add /usr/local/include to the search
path and not (for example) /opt/include?
because Metakit and SimGear are installed there by default (withour any
additional --prefix option) - at least in my case.
Regards, Michael
--
Michael Basler, Jena,
On Mon, 17 Feb 2003 10:24:01 +0100
[EMAIL PROTECTED] (Michael Basler) wrote:
I have found the same problems. I think it is related to using
gcc 3.2 on recent cygwin.
Thanks, Richard, good to know it's not just my fault.
gcc 3.2 doesn't look in /usr/local/* by default, so you need to
Bernie,
There already is a --with-metakit=DIR option to configure. Conversely you
specify CPPFLAGS and LDFLAGS on the command line to configure thus:
Is there a similar option to tell FlightGear where to look for the Simgear
libs, as they hit the same problem? - I still would prefer having
I agree. If a user sucessfully builds and installs a package to it's default location,
it is reasonable to expect that subsequent ./configures would find that package.
Richard
-Original Message-
From: Michael Basler [mailto:[EMAIL PROTECTED]]
Sent: 17 February 2003 10:48 am
To:
I've scanned in the cockpit diagram from the GR3 from the pilots manual,
and managed to hack it around to get this:
http://www.stockill.org/fgfs/fgfs-screen-001.jpg
If anyone wants to make use of it to produce a full 2d panel then I'll be
happy to provide the files in whatever resolution/format
Michael Basler writes:
Bernie,
There already is a --with-metakit=DIR option to configure. Conversely you
specify CPPFLAGS and LDFLAGS on the command line to configure thus:
Is there a similar option to tell FlightGear where to look for the Simgear
libs, as they hit the same problem? -
James Turner [EMAIL PROTECTED] said:
Basically, I think the currently panel method (a tree of elements we
place) is essentially right model (i.e declarative, not just procedural
bits of openGL). We would need quite a few custom elements in this
approach, and NAV (map) displays are a
Erik Hofman [EMAIL PROTECTED] said:
There is a third option:
use glDrawPixels to draw essentially a constantly updating texture.
I have no idea about the performance penalty it involves, but it might
be worht looking into.
Erik
It seems like that'd be the only way of doing gps map
Curt,
Ok, looking in configure.ac, the --with-metakit=/path/to/metakit
option simply adds the specified path to EXTRA_DIRS. We used to add
/usr/local to EXTRA_DIRS automatically, but this was removed because
it was causing problems for gcc-3.x. Question for those with gcc-3.x:
does the
Jim Wilson writes:
Erik Hofman [EMAIL PROTECTED] said:
There is a third option:
use glDrawPixels to draw essentially a constantly updating texture.
I have no idea about the performance penalty it involves, but it might
be worht looking into.
Erik
It seems like that'd be
OK, these tests are using SimGear and FlightGear CVS snapshots from about 29th Jan,
Cygwin (similar date) on W2K, gcc 3.2.
When configuring SimGear:
./configure --with-metakit=/usr/local (or ./configure
--with-metakit=/usr/local/lib) both fail at the MetaKit version check. I should note
Curtis L. Olson wrote:
I seem to recall hearing discussions that glDrawPixels() is
*excessively* slow on most platforms; to the point of making it nearly
unusable for real time graphics.
It also ties the implementation to a particular screen resolution,
which is a non-starter 3D cockpits
We appear to have got a mention in Alan Cox's diary.
Unfortunately he's taken to writing the last batch of entries in Welsh -
obviously the lessons are going well...
http://www.linux.org.uk/diary/ if anyone has the ability to translate.
--
Jon Stockill
[EMAIL PROTECTED]
I noticed that too. Pity that Babelfish doesn't do Welsh.
Could be related to DRI? Possibly?
(Why didn't I take Welsh lessons when I was at University in Swansea?)
Richard
-Original Message-
From: Jon Stockill [mailto:[EMAIL PROTECTED]]
Sent: 17 February 2003 4:21 pm
To: [EMAIL
On Monday, February 17, 2003, at 04:21 pm, Jon Stockill wrote:
http://www.linux.org.uk/diary/ if anyone has the ability to translate.
According to my native welsh friend (who also hacks the kernel, so I
assume the technology is correct to):
'Too many collisions, DRI collides too much when
Jon Stockill [EMAIL PROTECTED] said:
We appear to have got a mention in Alan Cox's diary.
Unfortunately he's taken to writing the last batch of entries in Welsh -
obviously the lessons are going well...
http://www.linux.org.uk/diary/ if anyone has the ability to translate.
InterTran
And the answer is
-- Forwarded message --
Date: Mon, 17 Feb 2003 11:41:01 -0500 (EST)
From: Alan Cox [EMAIL PROTECTED]
To: Jon Stockill [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: FlightGear
thought I'd mail and ask for a translation of the entry concerning
InterTran results:
translation
Too much he espouse. He is being THREE ' heartburn espouse when dw I '
heartburn play 'Flightgear' I go he is being two he one has ' heartburn
espouse before the tw. He is being anyone ' heartburn blemish serious except
we were we police force and ambulance I
According to my native welsh friend (who also hacks the kernel, so I
assume the technology is correct to):
'Too many collisions, DRI collides too much when playing Flightgear,
[...]
This sounds quite reasonable. I got a reply from Alan on 'dri-devel':
My lockup with flightgear on the 9000
Martin Spott writes:
I am (I suppose so) annoying the DRI people already for many months because
FlightGear reliably locks up their X server built from development source
tree. So I assume people start getting really interested in this issue
because they don't want an XFree86-4.3.0 release
As to DRI (Welsh for THREE!) crashing, I don't even need FlightGear to
crash my computer with DRI CVS, it crashes on startup of the X
server. Hmmm, maybe it's time to also install the kernel module from
DRI?
Yep, please pick the sources from:
Jon Stockill wrote:
And the answer is...
Alan Cox wrote:
Flightgear crashes my box with a Radeon 9000
Seems to be the large textures when I buzz a city. Quite annoying
really because its a really neat program. Other stuff like cube
works well
Magnificent. Maybe now someone will look
Andy Ross writes:
Magnificent. Maybe now someone will look at the issue. I reported
this a while back, and Keith Whitwell's response was essentially that
FlightGear was too big and complicated to use as a test case. :(
Keith does make a good point, simple test cases are the most ideal in
Curtis L. Olson writes:
Keith does make a good point, simple test cases are the most ideal in
terms of debugging problems, but the flip side is that you run the
risk of building drivers that only work on the simple test cases.
You need a simple test case that uses lots of polygons and lots
Martin Spott writes:
I am (I suppose so) annoying the DRI people already for many months because
FlightGear reliably locks up their X server built from development source
tree. [...]
Keep bugging them. :-)
Hmm, it already cost me zillions of hours to do this. FlightGear is anything
but a
Hi, i'm a student and trying to learn how to make flight sims. i am in the learning process and i was wondering if anyone of you could point me in the righ direction. i want to start by drawing dials, and horizon indicator. i dont know if flightgear has function calls to automatically do this, but
Once upon a time, you were sitting and writing:
Hi, i'm a student and trying to learn how to make flight sims. i am in the learning
process and i was wondering if anyone of you could point me in the righ direction. i
want to start by drawing dials, and horizon indicator. i dont know if
Elad Yarkoni writes:
Once upon a time, you were sitting and writing:
Hi, i'm a student and trying to learn how to make flight sims. i am in the
learning process and i was wondering if anyone of you could point me in the righ
direction. i want to start by drawing dials, and horizon
Curtis L. Olson wrote:
Actually, drawing 2d panels is pretty straight forward, and their's
lots of examples you can start with and modify. Panels are all done
with .xml config files so you don't need to do any coding or
recompiling to build a panel. And, you can reload the panel on the
fly, so
I mentioned earlier that I had a fun toy I wanted to pawn off on you
guys. Here: http://www.plausible.org/nasl
Some will remember a few months back when the subject of scripting
languages came up that I mentioned that someday I'd love to write my
own language. Existing embeddable languages are
I've been working on an ADI for the jets, based on Dave's C-172 attitude
indicator and have hit a snag. Does the 2D panel code offer the ability to
crop textures that would be shifted out of the bounds of the instrument?
Dave Culp
___
37 matches
Mail list logo
