-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wonder if we could use some of this stuff. http://www.openatc.org
David
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE85fsZx58m2d272NoRAspWAJ0fySpRWprmXDadVXK/hxaTzj285gCgnlcd
* Keith Wiley -- Saturday 18 May 2002 00:26:
Should I just scrap my entire flightgear directory, throw it away, and
start over from scratch?
As a last resort, maybe. But you still didn't investigate the bug that
you originally reported: remember do ble?
Hi,
Another approach to cliud modelling could be found here:
http://nis-lab.is.s.u-tokyo.ac.jp/~nis/abs_cgi.html#pg01
Looking at the images it has about the same looks, but seems to be
cheaper in CPU/GPU performance:
http://nis-lab.is.s.u-tokyo.ac.jp/~nis/img/cmlcloud1s.jpg
As a last resort, maybe. But you still didn't investigate the bug that
you originally reported: remember do ble?
/usr/local/src/FlightGear/src/Main/fg_init.cxx:628: undefined reference to
`FGNullFDM::FGNullFDM(do ble)'
Have you ever looked into fg_init.cxx, line 628? (Things have
When you cvs update FlightGear, do you also cvs update SimGear ?
Cheers,
-Fred
- Original Message -
From: Keith Wiley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, May 18, 2002 7:28 PM
Subject: Re: [Flightgear-devel] Re: I simply don't know what I'm doing wrong
As a last
When you cvs update FlightGear, do you also cvs update SimGear ?
Ugh! Usually I start with plib, move to SimGear, then move to
FlightGear. But when FlightGear starts causing trouble for me, I suppose
I just revert to trying to cvs update FlightGear. I guess that won't work
though. That
Do you retry now with plib, SimGear and FlightGear in sync.
What are your actual error messages ?
-Fred
- Original Message -
From: Keith Wiley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, May 18, 2002 8:00 PM
Subject: Re: [Flightgear-devel] Re: I simply don't know what I'm
Do you retry now with plib, SimGear and FlightGear in sync.
What are your actual error messages ?
Further on that topic, I've got a script redoing that I need about
once every couple of months. It does CVS with explicit -APd
against the six trees, builds simgear from clean with reinstall,
Another idea: you might have old versions of SimGear, plib or other libraries
installed somewhere. This should find exactly one copy of libsgsky:
$ find /usr -name 'libsg*' -exec grep -l getSpan_m {} \;
/usr/local/lib/libsgsky.a
If it finds none or more than one, there's a problem with the
The telnet interface produce wrong line ending when I run both FlightGear
and the telnet client on Win2k. I've just sent a patch to Curt that produce
line ending based on the platform where fgfs is running ( something between
#ifdef and #endif ).
For the moment, this patch only address the issue
Frederic Bouvier wrote:
The telnet interface produce wrong line ending when I run both FlightGear
and the telnet client on Win2k. I've just sent a patch to Curt that produce
line ending based on the platform where fgfs is running ( something between
#ifdef and #endif ).
For the moment,
I (Julian Foad) wrote:
Idea: the receiver should accept any of these four line endings:
Sorry, I misunderstood. I was thinking of a peer-to-peer type connection.
- Julian
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Frederic Bouvier wrote:
Perhaps I didn't made me clear. The problem is when FlightGear send text to
the telnet client. Each line begins where the previous ends because Win2k
telnet client needs a cariage return (\r) with the line feed (\n).
OK. The Telnet protocol (RFC854) requires that line
Frederic Bouvier wrote:
The telnet interface produce wrong line ending when I run both FlightGear
and the telnet client on Win2k. I've just sent a patch to Curt that produce
line ending based on the platform where fgfs is running ( something between
#ifdef and #endif ).
For the moment,
14 matches
Mail list logo
