We should now really think about making a plib branch for
the data -- just named PLIB (no pointless date!). The old
and unused plib branch (PRE_OSG_PLIB_20061029) could be
removed. It doesn't contain anything useful. I guess it's
safe to assume that no more plib based release will be made
(except
* Stuart Buchanan -- Friday 18 January 2008:
Of course, if we're not planning to make any further plib releases,
then there is no need for a PLIB data branch :) .
A plan is (only) a plan. We should keep the possibility to
release a version 1.1 with the most annoying bugs of 1.0 fixed.
Aircraft
Hi all,
I think there is a bug when using the native protocol to link two instances of
FlightGear via network or when recording and playing back flights using
fgfs --native=file,out,20,fgfs.out
and
fgfs --native,file,in,20,fgfs.out --fdm=external
The external FlightGear crashes and after
--- Melchior FRANZ wrote:
We should now really think about making a plib branch for
the data -- just named PLIB (no pointless date!). The old
and unused plib branch (PRE_OSG_PLIB_20061029) could be
removed. It doesn't contain anything useful. I guess it's
safe to assume that no more plib
On Fri, 18 Jan 2008 15:38:47 +0100
Melchior FRANZ wrote:
* Chris Metzler -- Tuesday 08 January 2008:
fgfs --aircraft=ufo is enough to give me the same
} Nasal runtime error: props.setDoubleValue() with non-number
} at /home/cmetzler/Projects/FlightGear-0.9/data//Nasal/props.nas,
hi all,
i've started to run fg through valgrind. i found this to be a nice option for
getting an overview over the code in flightgear.
i plan to prepare some patches to fix various issues reported by valgrind.
this is the first in (i hope) a series of several patches yet to follow. i
couldn't
On 01/18/2008 09:05 AM, till busch wrote:
i've started to run fg through valgrind. i found this to be a nice option for
getting an overview over the code in flightgear.
1) This is important, valuable, and overdue.
2) It's going to be a lot of work. That's because
2a) Although it is easy
* Chris Metzler -- Tuesday 08 January 2008:
fgfs --aircraft=ufo is enough to give me the same
} Nasal runtime error: props.setDoubleValue() with non-number
} at /home/cmetzler/Projects/FlightGear-0.9/data//Nasal/props.nas, line 26
Can't reproduce that here, neither with fg/plib nor fg/osg.
On Friday 18 January 2008 16:49, Chris Metzler wrote:
On Fri, 18 Jan 2008 15:38:47 +0100
Melchior FRANZ wrote:
* Chris Metzler -- Tuesday 08 January 2008:
fgfs --aircraft=ufo is enough to give me the same
} Nasal runtime error: props.setDoubleValue() with non-number
} at
Hi FlightGear developers.
It looks like there are some portability issues in the current code... I
got this report on the Debian packages. I could patch the missing ifdefs
I guess (though it'd be nice if you fixed them for a future release),
but could you comment on the 64-bit issue?
Steve
Ove Kaaven wrote:
It looks like there are some portability issues in the current
code...
On three platforms which don't have the CPU power (or GPU support!) to
actually, y'know, run the software. :)
Steve Langasek wrote:
So this assumes the kernel will never expose more than 48bits of
Hi all,
is anyone successfully building and running fgfs under MacOS X using configure?
It compiles and runs the splash screen and setups but then crashes applying a
texture (don't know which).
I'd just like to make sure it's actually a compilation problem and not some
missing texture file.
12 matches
Mail list logo
