Carsten, David
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
It looks interesting -- I'll try to find time to read it in more
detail.
If Carsten manages to get this written with time (and I am sure it will need
time) this will be a great addition to FlightGear and
Sorry for the full quote... just happened.
Michael
--
Michael Basler, Jena, Germany
[EMAIL PROTECTED]
http://www.geocities.com/pmb.geo/
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Michael Basler writes:
There are several checklists available (intended for use with MSFS, but
these are the real ones), including for Cessnas, from
http://www.flightsim.com/login.htm
Besides, they have complete manuals for several aircraft available
(including Cessnas, as I just
David,
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Megginson
Thanks. I took a look, but couldn't find anything except
FS2000/FS2002 checklists. Where are the actual Cessna ones on the
The file names are
manc310.zip, manc185,zip, manc172 and so on, depending
Here's the sprintf problem again in a recent build attempt for
fg_init.cxx. Is there a fix for this for CygWin?
Jon
g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/us
r/local/include -DPKGLIBDIR=\/usr/local/lib/FlightGear\ -c -o fg_init.o
`test -f 'fg_init.cxx' || echo
Martin Spott writes:
make[2]: *** No rule to make target `new_gui.cxx', needed by `new_gui.o'. Stop.
Somethings not rebuilding properly. Make sure you have a fresh CVS
checkout, [...]
I was absolutely shure I did - but I forgot to uncomment a line in my
build-script that updates the
Michael Basler writes:
Thanks. I took a look, but couldn't find anything except
FS2000/FS2002 checklists. Where are the actual Cessna ones on the
The file names are
manc310.zip, manc185,zip, manc172 and so on, depending which you
are looking for. I entered cessna and manual
Jon Berndt writes:
Here's the sprintf problem again in a recent build attempt for
fg_init.cxx. Is there a fix for this for CygWin?
Jon
g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/us
r/local/include -DPKGLIBDIR=\/usr/local/lib/FlightGear\ -c -o fg_init.o
David,
These are short checklist collections for FS2000/2002. You mentioned
that there were actual scanned POH's available somewhere. What I'm
most interested in are the POH performance tables for various
Unfortunately you are right, I should have checked before. I thought they
would
Michael Basler writes:
Unfortunately you are right, I should have checked before. I thought they
would provide manual + checklist if they write manual + checklist :-(
It still might be helpful for what Carsten wants to do, though.
I've noticed POH's and IM's (generic POH's) popping up
Norman Vine wote:
! #ifdef _WIN32
#define snprintf _snprintf
#endif
--- 66,72
! #if defined(_WIN32) !defined(__CYGWIN__)
#define snprintf _snprintf
#endif
To Norman: Good fix.
To Curt (etc.): Shouldn't this go in simgear/compiler.h instead of in every source
file
[EMAIL PROTECTED] writes:
Norman Vine wote:
! #ifdef _WIN32
#define snprintf _snprintf
#endif
--- 66,72
! #if defined(_WIN32) !defined(__CYGWIN__)
#define snprintf _snprintf
#endif
To Norman: Good fix.
To Curt (etc.): Shouldn't this go in
Once upon a time, you were sitting and writing:
Roel Michiels writes:
When you start modelling the B737, here's an excellent site by on of
the Captains I flew with at Sabena. This man is highly proficient
and also a simulation enthousiast. You will find lots of info
concerning the
On Wed, 13 Nov 2002 21:33:56 -0500
Norman Vine [EMAIL PROTECTED] wrote:
I realize that Patrick needed to change the
#ifdef WIN32 to #ifdef __CYGWIN__
but this should not be necessary in that WIN32 should be
being #defined by our configure script and as it is written
this works on both
I have been working a bit over the weekend on the intialization
infrastructure, especially as it relates to providing initial
conditions to the FDM's.
I created a /sim/presets area in the property manager which is where
all the FDM initial conditions can be batched up. Things like:
airport-id
Curtis L. Olson wrote:
BTW, Andy, how hard would it be to accept an initial airspeed for
the YASim models so we can do in-air starts with those?
Not hard at all. The only reason it doesn't is that, heh, I got
really confused about how to figure out the units and precedence
rules. Speed can be
Curtis L. Olson writes:
BTW, Andy, how hard would it be to accept an initial airspeed for the
YASim models so we can do in-air starts with those?
Andy's concern has been the obfuscation around velocities. We have
- calibrated airspeed in knots (forward from the nose of the plane)
- mach
On Mon, 2002-11-18 at 14:17, Andy Ross wrote:
Curtis L. Olson wrote:
BTW, Andy, how hard would it be to accept an initial airspeed for
the YASim models so we can do in-air starts with those?
Not hard at all. The only reason it doesn't is that, heh, I got
really confused about how to
On Mon, 2002-11-18 at 14:41, David Megginson wrote:
Curtis L. Olson writes:
BTW, Andy, how hard would it be to accept an initial airspeed for the
YASim models so we can do in-air starts with those?
Andy's concern has been the obfuscation around velocities. We have
- calibrated
Thanks for the checklist, David. Now it's in the document!!
Carsten
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] Im Auftrag von David
Megginson
Gesendet: Montag, 18. November 2002 03:50
An: [EMAIL PROTECTED]
Betreff: re: [Flightgear-devel] Flying Tutorial
Carsten Höfer writes:
Thanks for the checklist, David. Now it's in the document!!
Great. I'll send the emergency checklists another time, when I feel
like more typing. The weight and balance data and performance tables
are also needed for flight planning.
All the best,
David
--
David
* [EMAIL PROTECTED] (Curtis L. Olson) [2002.11.18 15:47]:
I created a /sim/presets area in the property manager which is where
all the FDM initial conditions can be batched up. Things like:
snip/
runway (i.e. 1R)
snip/
Woohoo! That's been on my wishlist[1] from when I first
22 matches
Mail list logo
