Well my talk at Linux.conf.au didn't go all to plan. The talk went okay, but
the projector decided to kill itself making the demos a little difficult. I
got to do a demo for the conference dinner though. A lot of people were
impressed, so we can expect to see a few in fgfs-user's soon. Also
David Findlay wrote:
Well my talk at Linux.conf.au didn't go all to plan. The talk went okay, but
the projector decided to kill itself making the demos a little difficult. I
Bad things happen always at thr wrong time :-(
got to do a demo for the conference dinner though. A lot of people
Since a while I get a line of black pixel garbage below the labels WL and
ALT on the autopilot. Does anybody else see this? (Or is it a feature of
my graphics card? :-) The following patch fixes this for me.
m.
Index: autopilot.xml
John wrote:
I'd like to do a reorg of the directory
structure after the release.
Sounds good to me.
Bye bye,
Wolfram.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
On Sat, 9 Feb 2002 00:57:06 -0600, Jon S. Berndt
[EMAIL PROTECTED] wrote:
WHAT???
Design maneuvering speed is Va and is simply and _only_
Va = Vs * sqrt(g load limit)
You can be sure that an aircraft manufacturer would have a whole lot of
patents if they had a method to recognize all the
The problem with Neural Nets, as I understand it, is that they
are regarded as non-predicatable. The only way to check that
they perform correctly in all circumstances is to check all
circumstances. The logic is effectively non-traceable (or
regarded as such).
I don't know, but there's a
Curtis L. Olson wrote:
The 747-yasim-set.xml file references a non-existant panel. Is there
something better we can use in the mean time? Or just not specify a
panel until we have one we can use?
I've been wondering about that myself. :) I figured it was checked in
this way because
I'm trying to build plib in anticipation of building simgear and
flightgear, but make is failing saying ul.h can't find GL/gl.h or
GL/glu.h. This is a perfectly reasonable complaint since a search of my
harddrive has turned up nothing on either of those two files.
...but, I have already
I've noted some irregularities in the coastline data we are using. Is this
coming from the coastline extractor, or from somewhere else? Thanks,
David
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
