On another forum, Simon Knott gave me these links:
http://aar400.tc.faa.gov/aar-430/reports/01-44.pdf
http://www.avnet.co.uk/gtaviatn/betashop/categories_category=19023.htm
The first includes a 3side view of a C172. Unfortunately, there are no
crosssections. There is also a lot of data about
Wolfram Kuss writes:
Have you looked at the profile of the wing yet? :-).
I'm trying to keep the tri count down, but it does have sort-of an
airfoil profile (i.e. the top curves up).
All the best,
David
--
David Megginson
[EMAIL PROTECTED]
Windows 98 SE ... stock standard stuff.
Tell me about the display car dyou have, how much memory there?
Must search for the 'book' that came with the machine for the actual
'card'
but i remember something like AGP something. The driver is the Intel
810e Chipset Graphics Driver PV 2.1 (as Alex
... Really, the FDM takes a very small amount
of computation time. Most of the time is spent in the display
routines, IIRC.
That is agreed. But i was making a point about how 'rocking' the ac
when the engine/mags are off (and 0 wind) cause the 'display' to be
re-done - that is a small
I seeing on TV recently that they have only recently added full computer
stabilisation to the Harrier. They had the presenter of the program (a
qualified military pilot, but not on the Harrier) flying a two-seater.
There was a switch to choose hover or normal flight, in hover mode the
throttle
Melchior FRANZ wrote:
Andy Ross wrote:
There's also a complication with the Harrier. You'll need to map a
joystick axis to the /controls/thrust-vector[0] property in order to
work the thrust vectoring.
Works also reasonably well when mapped to the low/high properties of a
I am again trying to compile the CVS version of FlightGear. I *think* I am
following instructions!
I have not had any trouble building the version 0.7.8, but with CVS I get
the following compile error:
Making all in ATC
make[2]: Entering directory `/usr/local/src/FlightGear/src/ATC'
c++
I am again trying to compile the CVS version of FlightGear.
I *think* I am following instructions!
I have not had any trouble building the version 0.7.8, but
with CVS I get the following compile error:
Did you do a build of plib first, followed by Simgear, then FlightGear?
Jon
Boslough, Mark B wrote:
I am again trying to compile the CVS version of FlightGear. I *think*
I am following instructions! I have not had any trouble building the
version 0.7.8, but with CVS I get the following compile error:
Not to be too snooty, but sometimes it's helpful to actually
No. That was going to be my next guess. Thanks, I'll try that!
Mark
I've got a perl script (and I believe Norman also has a script) that
automates that whole process for me, in the corret order, with dependencies.
If you do a checkout of flightgear, you should also do a checkout of Simgear
Since I already had built plib, this time I downloaded and build the CVS
version of Simgear followed by the CVS version of FlightGear. This time I
got further, but still ran into this:
Making all in GUI
make[2]: Entering directory `/usr/local/src/FlightGear/src/GUI'
c++ -DHAVE_CONFIG_H -I. -I.
The downloads page states you need at least plib-1.4.0 to build
flightgear. Right now I'm using plib-1.4.2. What version of plib do
you have installed?
Curt.
Boslough, Mark B writes:
Since I already had built plib, this time I downloaded and build the CVS
version of Simgear followed by the
Jon Berndt writes:
No. That was going to be my next guess. Thanks, I'll try that!
Mark
I've got a perl script (and I believe Norman also has a script) that
automates that whole process for me, in the corret order, with dependencies.
If you do a checkout of flightgear, you should
The latest stable Plib (1.4.2 I believe) should also work (It
does for me). It shouldn't be necessary to keep checking out CVS Plib.
It takes about 2 minutes (maximum) to check out and build on my machine. I
always do it to avoid (and rule out) any build problems. This is one reason
why I no
I went ahead and checked out the CVS plib and it built without
error. Thanks again everybody... hopefully there will be no more
dumb beginner questions from me again for awhile :-)
Mark
-Original Message-
From: BERNDT, JON S. (JON) (JSC-EX) (LM)
[mailto:[EMAIL PROTECTED]]
Sent: Monday,
Christian wrote:
In that case you can have a much simpler solution. Look at PLIBs PUI and
create a new (permanet) PUI window that outputs the text. Should be
quite easy.
Thanks Christian! Pui worked great!
Dawn
___
Flightgear-devel mailing
Geoff McLane writes:
Yeah! Precisely. perfectly. Can I give you the number of my
person-in-charge-of-upgrade of our in-house major system? ... and you
tell them (actually her) - err, I only write an fdm for that in which in
can
run. Get a better capability, or ??? shut up ??? :-)))
There
FWIW, I just bought a GeForce 2 Pro from newegg.com for US$90. It was
the Gainward Ti450 and works quite well.
Jon
On Sunday, January 27, 2002, at 11:52 AM, Elad Yarkoni wrote:
Hi Guys,
I know you hate it... and this topic seems to be
endless on FGFS-Devel group, AND this discussion
Andy wrote
Just need to get the turbine data across the
link (Assuming that YASIM is generating N1, N2, EGT, EPR, oil
pressure, fuel flow, etc)
Sure thing:
/engines/engine[n]/n1
/engines/engine[n]/n2
/engines/engine[n]/epr
/engines/engine[n]/egt-degf
Engine data is a little screwy. running jbsim for the c310 no data comes
across and for yasim-747 the zeroeth values are missing.
Not sure i've got this properties thing all figured out yet.
In opengc.cxx
data-n1_turbine[0] = fgGetDouble(/engines/engine[0]/n1);
Engine data is a little screwy. running jbsim for the c310 no data comes
across and for yasim-747 the zeroeth values are missing.
Not sure i've got this properties thing all figured out yet.
In opengc.cxx
data-n1_turbine[0] = fgGetDouble(/engines/engine[0]/n1);
data-n1_turbine[1]
21 matches
Mail list logo