- Original Message -
From: Andy Ross [EMAIL PROTECTED]
To: FlightGear developers discussions [EMAIL PROTECTED]
Sent: Thursday, May 27, 2004 6:20 PM
Subject: Re: [Flightgear-devel] VBO patch
Roman Grigoriev wrote:
Here is my new VBO code but it's so strange that it doesn't work with
Hi Guys
When I started this topic all I was asking
was to set aside say ten of the keys that are
not currently used for A/C specific functions.
By this I ment functions that are specific to that
A/C eg a 747 may have a cargo door while a fighter
may have a tail hook in which case each could use
snip
Alternatively, you could use a WYSIWYG paradigm and just make
all the functions
clickable and make people click over to mode 0 and use the
mouse cursor. The way
I see it a real pilot has to let go of something to twiddle a
dial anyway, we
shouldn't complain if we have to as
Innis Cunningham wrote
Hi Guys
When I started this topic all I was asking
was to set aside say ten of the keys that are
not currently used for A/C specific functions.
By this I ment functions that are specific to that
A/C eg a 747 may have a cargo door while a fighter
may have a tail
Arnt Karlsen wrote:
On Thu, 27 May 2004 21:31:10 +0200, Erik wrote in message
[EMAIL PROTECTED]:
First try searching for an aircraft that has a boost function for it's
engine *and* that has speebrakes.
..AFAIR, this was a kludge to get around a few problems modelling
gear shift controls on
being simulated at once. For instance, if you
wanted to show Aerial Re-fueling, with a 747 tanker, and a UAV?
thanks
sonny
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
I have written some code that at initialization time will snap all
localizers into perfect alignment with their runways. It's my
experience that the DAFIF/FAA data reports runway and localizer headings
to a level of precision that is perfect for making charts, or adjusting
your OBS, etc. But
Curtis L. Olson wrote:
There are probably cases where the localizer isn't really perfectly
aligned with the runway, or intentionally misaligned to avoid obstacles
or terrain.
You are correct -- for a non-precision, LOC-only approach, the localizer can
be as far as 30 deg off the runway heading
The fix is attached, could someone please check it into CVS if it is
appropriate?
I am attempting to build source from 16:00 GMT under Mac OS X.3 with
compiler gcc --version
gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495)
Copyright (C) 2002 Free Software Foundation, Inc.
I am
David Megginson wrote:
Curtis L. Olson wrote:
So I have made this configurable for those that trust the data more
than I do. Just set /sim/navdb/auto-align-localizers to
true/false in the preferences file to turn this feature on or off in
the code.
I'd be more comfortable fixing the
Oops! Forgot 4 important things. Try this one instead:
AIBase.cxx
Description: Binary data
(as follows):
void FGAIBase::bind() {
double (FGAIBase::*pgVS_fps) () const;
void (FGAIBase::*psVS_fps) ( double );
double (FGAIBase::*pga) () const ;
void (FGAIBase::*psa) (
[EMAIL PROTECTED] wrote:
Oops! Forgot 4 important things. Try this one instead:
Sorry for the trouble!
No problem. It turned out to be much simpler than that, but thanks for
the hint anyway. A fix is in CVS now.
Erik
___
Flightgear-devel mailing
Hi,
I have installed plib and simgear and GL/glut.h is found in the configure
but when i configure flight gear i get the following error:
checking GL/glut.h usability... no
checking GL/glut.h presence... no
checking for GL/glut.h... no
checking GLUT/glut.h usability... no
checking GLUT/glut.h
sorry, turns out there is no GL/glut.h.
I apologize for wasting anyones time.
Seamus
On Fri, 28 May 2004, Seamus Thomas Carroll wrote:
Hi,
I have installed plib and simgear and GL/glut.h is found in the configure
but when i configure flight gear i get the following error:
checking
Andy Ross wrote:
Or as a compromise, make the property a threshold value.
Misalignments less than ~5 degrees (or whatever) are likely to be
problems with the input data, while larger variances probably
represent a real-world issue we want to simulate.
That seems like a reasonable compromise.
Just did a SimGear/FlightGear/JSBSim CVS build and see the following debugging
console output left in:
dist = 1.54278
bias = 2
dist = -0.457218
dist = 1.54243
bias = 2
dist = -0.457567
etc ...
Look familiar to anyone?
Dave
--
David Culp
[EMAIL
David Culp wrote:
Just did a SimGear/FlightGear/JSBSim CVS build and see the following debugging
console output left in:
dist = 1.54278
bias = 2
dist = -0.457218
dist = 1.54243
bias = 2
dist = -0.457567
etc ...
Look familiar to anyone?
Whups that would be me.
Curt.
--
Curtis Olson
17 matches
Mail list logo
