How can I participate somehow in the developping
process of flightgear? Thanks in advance!
--- [EMAIL PROTECTED] wrote:
Send Flightgear-devel mailing list submissions to
flightgear-devel@flightgear.org
To subscribe or unsubscribe via the World Wide Web,
visit
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
or, via email, send a message with subject or body
'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it
is more specific
than Re: Contents of Flightgear-devel digest...
Today's Topics:
1. Re: TaxiDraw-0.3.2 released (Durk Talsma)
2. Re: multiplayer patch for enianess (Mathias
Fr?hlich)
3. Re: Multiplayer Location Transformation
toLat/Lon/Alt
(Mathias Fr?hlich)
4. Re: Real weather fetch stops FG from starting
(Lee Elliott)
5. FlightGear freezes (float point interrupt)
(Ampere K. Hardraade)
6. Re: FlightGear freezes (float point interrupt)
(David Luff)
7. Re: TaxiDraw-0.3.2 released (David Luff)
8. Re: FlightGear freezes (float point interrupt)
(Andy Ross)
9. Question for Solaris-men (Sergio)
10. Re: Question for Solaris-men (Martin Spott)
--
Message: 1
Date: Tue, 16 Aug 2005 20:17:43 +0200
From: Durk Talsma [EMAIL PROTECTED]
Subject: Re: [Flightgear-devel] TaxiDraw-0.3.2
released
To: FlightGear developers discussions
flightgear-devel@flightgear.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1
On Tuesday 16 August 2005 14:49, David Luff wrote:
TaxiDraw-0.3.2 has been released. This release is
primarily to track
changes in the X-Plane data format. TaxiDraw has
also moved to
SourceForge, and can now be found at
http://taxidraw.sf.net. As a result,
the latest code can now be obtained from CVS,
hopefully making it easier
for others to collaborate in further development.
It also has an
autotools-type configure/make system now instead
of the buggy, hand-written
makefile, so those compiling from source will need
to use ./configure; make
(or ./autogen.sh; ./configure; make if using CVS).
That's really great news! I just started working
again on the AI ground
network code, and was wondering what the status was
with respect to the move
to sourceforge/CVS. I started working version 0.3.0
and was wondering how we
should go about merging this with the current
release. With cvs, I guess it's
going to be fairly easy to incrementally add my
changes to the repository.
FWIW, we probably need to think a bit about the
changes to the fileformat
required to support the AI networking code.
Cheers,
Durk
--
Message: 2
Date: Tue, 16 Aug 2005 20:30:22 +0200
From: Mathias Fr?hlich [EMAIL PROTECTED]
Subject: Re: [Flightgear-devel] multiplayer patch
for enianess
To: FlightGear developers discussions
flightgear-devel@flightgear.org
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1
Ok, this is *way* better than what was there before!
Thanks so far!
What I have problems with is that, as long as you
use a struct for the whole
message, the compiler is free to do alignment
decisions different than your
expectations on it.
I posted, at the time of the first attempts to fix
that, a xdr stream
implementation from the c++ journal.
That one would guarantee independence of struct
alignment.
The ip address of the sender is redundant.
I do at the moment not know the actual
implementation of the udp socket we use
here, but there must be a way to get them from the
recv call (at least for
the udp/ip case).
Is that address used to send a reply?
If so, this will not work for everybody behind a nat
gateway which rewrites
the ip headers but cannot know something about
flightgears internals.
Also why do you use fixed length strings?
It seems better to me if there is a length field in
front of the string data
which tells the implementation how much characters
it can expect (within the
limits of the current udp connection of course).
Also that xdr stream would not have the problem with
returning hardware
doubles if floats are returned by declaration (your
comment in timy_xdr.h).
I have access to a DEC alpha. I don't believe that I
can run flightgear on
that machine successfully and I doubt that there is
a single alpha left on
this earth where flightgear will be run on.
So if you just want to be complete, I can help you
with that, but my be we can
ignore the DEC's ...
Objections?
So all together this is good work, but as we are on
it, we might be able to
make it fool proof :)
Greetings
Mathias
On Montag 15 August 2005 10:02, Oliver Schroeder
wrote:
Hi,
I've written a patch that _should_ solve
