On September 10, 2004 04:34 pm, Olivier Soussiel wrote:
> Around 85 Mb for the vdo taped flight and about the same (or less) for
> Flight Gear Playback.
That's too big for me to host then.
By the way, how did you made a movie out of Flight Gear playback?
__
> Was this
just $GPGGA, $GPVTG? Were $GPRMC needed also?I use $GPRMC and
$GPGGA but basicly only position, altitude and itstimestamp are required.
The rest can be recomputed easily.> Are your modifications to FGFS
available to the rest of us?Yes but tel me how to proceed. I have very
very
Around 85 Mb for the vdo taped flight and about the same (or less) for
Flight Gear Playback.
Olivier
- Original Message -
From: "Ampere K. Hardraade" <[EMAIL PROTECTED]>
To: "FlightGear developers discussions" <[EMAIL PROTECTED]>
Sent: Friday, September 10, 2004 4:28 AM
Subject: Re: [Flig
On Fri, 10 Sep 2004 14:18:00 -0500
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
>
> *This data will not work with
> earlier versions of X-Plane* (such as 7.00 - 7.30).
I get the impression from this that the file formatting may have changed?
The install notes he points to are old and don't say an
Benno Rieger said:
> I'm searching for this point in "Flightgear source code" where my
> current position in the scenery will be calculatet new , after hit 'v'.
>
> Thanks
> Ben
>
Look at the FGLocation class: /simgear/scene/model/location.?xx This is
accessed by the viewer/fdm/ai/scenery/
*From Robin's apt/nav data site ...
NEW* Sep 07 2004: *New data for X-Plane 7.40 and later* will be
available next weekend (Sep 18 2004), based upon * DAFIF cycle 200409*
(valid from Sep 02 2004 - Sep 29 2004). *This data will not work with
earlier versions of X-Plane* (such as 7.00 - 7.30).
We'd like to do another release of FlightGear/Simgear in the next week
or two. I'm starting to roll together the first round of pre-releases.
Mostly this release should fix problems and discrepancies with the
v0.9.5 release of FlightGear with not a ton of new development.
Regards,
Curt.
--
Cu
On 9/9/04 at 9:00 AM Alex Perry wrote:
>From: David Megginson
>> On Wed, 08 Sep 2004 21:35:30 +0200, Erik Hofman wrote:
>> > I do think so, don't we.
>> > I mean, this is an essential part of airfields, but don't know enough
>> > about this subject to assert that the numbers are always right t
> I've always thought that using stl strings was generally safer than char*,
> but could anyone comment on the below?
>
> string s = "";
> s[2] = 'x';
http://www.roguewave.com/support/docs/ (see the "string" docs)
You might need to do a resize() first.
Jon
David Luff wrote:
> I've always thought that using stl strings was generally safer than char*,
> but could anyone comment on the below?
>
> string s = "";
> s[2] = 'x';
>
> Am I stomping on random memory with the out-of-range character write, or
is
> this protected against because it's an stl stri
I've always thought that using stl strings was generally safer than char*,
but could anyone comment on the below?
string s = "";
s[2] = 'x';
Am I stomping on random memory with the out-of-range character write, or is
this protected against because it's an stl string?
TaxiDraw currently has a mem
11 matches
Mail list logo
