Jim Wilson wrote:
Erik Hofman <[EMAIL PROTECTED]> said:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/fokker100
In directory baron:/tmp/cvs-serv5280/Aircraft/fokker100
Log Message:
Directory /var/cvs/FlightGear-0.9/data/Aircraft/fokker100 added to the
repository
Hi Erik,
Think we're still mis
Frederic Bouvier writes:
> The texture should be marked -kb in CVS. It is corrupted under windows
> and makes FG segfault on loading it.
As in
cvs admin -kb 737-01.rgb
? If so, then it should be OK now.
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.c
Frederic Bouvier writes:
> The texture should be marked -kb in CVS. It is corrupted under windows
> and makes FG segfault on loading it.
>
> Where is that cvswrapper that enforce the use of -kb for any rgb file ?
It's on my todo list ... 2 out of town funerals and a trip to Norway
for business ha
David Megginson writes:
> >
> That depends on where and when. I think that most pilots in the
> eastern U.S. (you're there, aren't you, Norm?) would have been happy
> even for 3 SM for much of this spring and summer, and L.A., of course,
> has its smog. Somewhere like Arizona, on the other hand,
Norman Vine writes:
> > Six statue miles is the generally-accepted cutoff for good VFR.
> > Terminal area forecasts (TAF's) don't bother with anything over that,
> > and just report P6SM (plus six statue miles).
>
> Nice to know but does that have any bearing on anything other then
> what i
David Megginson writes:
>
> Curtis L. Olson writes:
>
> > Make default visibility exactly 10 miles.
>
> Six statue miles is the generally-accepted cutoff for good VFR.
> Terminal area forecasts (TAF's) don't bother with anything over that,
> and just report P6SM (plus six statue miles).
Nice t
Jon S Berndt wrote:
On 1 Jul 2003 17:20:40 GMT
Martin Spott <[EMAIL PROTECTED]> wrote:
I'm happy to see those in CVS, I yet have to verify if this breaks
build on other platforms
It's quite straight forward so I don't expect any problems.
>> BTW, we have to give notice to Jon about these changes
On 1 Jul 2003 17:20:40 GMT
Martin Spott <[EMAIL PROTECTED]> wrote:
I'm happy to see those in CVS, I yet have to verify if this breaks build on
other platforms. BTW, we have to give notice to Jon about these changes,
otherwise he'll revert them on the next JSBSim update.
Would anyone commit the fix
On Wednesday 18 June 2003 04:32, Martin Spott wrote:
> Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> > $ fgfs --lon=-122.40 --lat=37.79 --heading=320 --altitude=500
> > --aircraft=ufo
>
> Thanks, this shows the buildings as expected. Now I understand the matter:
> The HUD coordinates display degree
Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> $ fgfs --lon=-122.40 --lat=37.79 --heading=320 --altitude=500 --aircraft=ufo
Thanks, this shows the buildings as expected. Now I understand the matter:
The HUD coordinates display degree and minute (the latter with decimals) -
not degrees with decimals
Curtis L. Olson wrote:
I notice the optical illusion subtlely in flightgear as it is. Please
change this back to the way it was. We shouldn't make the sun/moon
artificially larger at the horizon. If you do anything, squash it a
little vertically, but that's it.
It also shows up in photographs,
Erik Hofman writes:
> Christian Mayer wrote:
>
> > The reason why the moon looks bigger is an sort of optical illusion.
> > Because you've got reference points on the horizon like trees and
> > building your eyes tell you the moon is quite big. And when the moon is
> > high above you you don't
Norman Vine wrote:
Ah yes..., optical illusion are convincing
http://science.nasa.gov/headlines/y2002/24jun_moonillusion.htm
or else they wouldn't be called 'illusions' now would they :-)
I've already read this part. But I don't really care if the effect is an
illusion or not, if it is there in r
Christian Mayer wrote:
Any pilot flying on the back (fighter pilots do that occasionally as
well air acrobats) will be like looking bended over through his legs.
I didn't mention any pants ...
So do you take care of that? Does the effect get smaller when the pilot
begins to roll?
That would be e
Erik Hofman writes:
>
> Norman Vine wrote:
>
> > As Christian stated we < I > implemented this years ago, and after much
> > discussion and research, we *collectively* agreed that this was the
> > *wrong* thing todo.
> >
>
> It is commonly accepted that the size looks increased by a factor of
Norman Vine <[EMAIL PROTECTED]> said:
> Erik Hofman writes:
> >
> > Christian Mayer wrote:
> >
> > > The reason why the moon looks bigger is an sort of optical illusion.
> > > Because you've got reference points on the horizon like trees and
> > > building your eyes tell you the moon is quite big.
Erik Hofman schrieb:
Norman Vine wrote:
As Christian stated we < I > implemented this years ago, and after much
discussion and research, we *collectively* agreed that this was the
*wrong* thing todo.
Try searching the archives
It is commonly accepted that the size looks increased by a factor of
Norman Vine wrote:
As Christian stated we < I > implemented this years ago, and after much
discussion and research, we *collectively* agreed that this was the
*wrong* thing todo.
Try searching the archives
I did. But there wasn't any mention that this effect still exist when at
sea or at high alt
Erik Hofman writes:
>
> Christian Mayer wrote:
>
> > The reason why the moon looks bigger is an sort of optical illusion.
> > Because you've got reference points on the horizon like trees and
> > building your eyes tell you the moon is quite big. And when the moon is
> > high above you you don't ha
Christian Mayer wrote:
The reason why the moon looks bigger is an sort of optical illusion.
Because you've got reference points on the horizon like trees and
building your eyes tell you the moon is quite big. And when the moon is
high above you you don't have that kind of re reference.
So as o
David Megginson writes:
> That's too easy. Try --random-wind instead.
I don't see this one listed in --options --verbose ...
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org
Minnesota http:/
David Megginson <[EMAIL PROTECTED]> wrote:
> Martin Spott writes:
> > Do you intend to supply a default 'quite windy' scheme for convenience of
> > those who simply would like to try a sort of "second level in the
> > game" ?
> That's too easy. Try --random-wind instead.
I already do so ;-)
Martin Spott writes:
> Do you intend to supply a default 'quite windy' scheme for convenience of
> those who simply would like to try a sort of "second level in the
> game" ?
That's too easy. Try --random-wind instead.
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://ww
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
> Martin Spott writes:
>> The current state still does not make much sense to me,
> Originally we had 5 unique crop textures and 5 corresponding material
> property entries.
> On April 25, those 5 material property entries were pointed at 3
> nearly i
Martin Spott writes:
> David Megginson <[EMAIL PROTECTED]> wrote:
> > Martin Spott writes:
>
> > > This is why I simply don't understand why they had to go. Would anyone be so
> > > kind to give me an unbiased explanation ? Did Erik fail to follow
> > > differentiation in the available land cov
David Megginson <[EMAIL PROTECTED]> wrote:
> Martin Spott writes:
> > This is why I simply don't understand why they had to go. Would anyone be so
> > kind to give me an unbiased explanation ? Did Erik fail to follow
> > differentiation in the available land cover data or has anything else been
Martin Spott writes:
> Hmmm, I've been following the texture changes for quite some time and to my
> knowledge these textures have been the most sophisticated ones for this sort
> of land coverage that FlightGear has ever seen.
>
> This is why I simply don't understand why they had to go. Wo
Curtis L. Olson wrote:
Erik, can we back this out for the release? Let's put it back in
immediately afterwards so we have time to sort out the consequences
(if any.)
Done.
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear
Jim Wilson writes:
> Sigh... can't we just leave this the way it was for now and tell people that
> we recommend a 3 axis stick??? :-/ If not we need time to check the joystick
> configs (and I don't have time to do the two I have today). I'd much rather
> see this patch added right after releas
David Megginson writes:
>
> There are standards for registering navaids with the FAA -- I saw them
> recently online, but I don't remember where.
I believe NGS has responsibility for airport mapping standards
several links from
http://www.ngs.noaa.gov/AERO/aero.html
Norman
By the way, is all the data consistent ? Everyone uses WGS-84, right ?
As far as I know, when an ILS is installed, they have an aircraft fly the
approach with the needles centered, and at the same time, they use optical
means to measure the path of the aircraft from the theoretical impact
point, t
Curtis L. Olson writes:
> I don't know if either DAFIF or FAA could be considered
> "authoritative".
I'd consider FAA authoritative for U.S. airports, and DAFIF for other
countries, again, until proven otherwise.
> I'm guessing that when an ILS is installed, someone goes out and
> stands at
David Megginson writes:
> We have to decide on the authority of each data point individually.
> Anything that we get from the DAFIF or FAA data should stand as-is,
> for example. For Robin Peel's data, we should fix things only when
> there is a known problem.
The problem is that in my spot check
Curtis L. Olson writes:
> The problem is that I have two data sets both providing "exact"
> locations for the localizer and both disagreeing significantly on the
> position and orientation. :-(
We have to decide on the authority of each data point individually.
Anything that we get from the DA
David Megginson writes:
> Curtis L. Olson writes:
>
> > - Added a redundant (left/right) vacuum pump.
>
> Is this optional? Many (most?) low-end singles have only a single
> vacuum pump, though the newest Cessna 172R/S has two.
I suppose these things should eventually move into some sort of
pe
David Megginson writes:
> Curtis L. Olson writes:
>
> > Modified Files:
> >default.ils.gz
> > Log Message:
> > Align all the approaches I could automatically match up to runways.
>
> Where we have exact data on the lat/lon of the localizer and GS, we
> should use it, and fix our airport
David Megginson writes:
> For the record, a CAT I ILS approach will bring you down to a decision
> height of 200 ft AGL. If you cannot see the runway or approach lights
> well enough to transition to visual at that point, you have to start a
> missed approach.
>
> CAT II and III ILS approaches ca
Erik Hofman writes:
> Do you think this is a good idea?
> Wouldn't it be better to sepecify this in the command line?
I think there needs to be more infrastructure built up around this,
but for now it causes fewer problems.
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Proj
Frederic Bouvier wrote:
Erik Hofman wrote:
BTW. This is a good step in the direction of XML defined options.
Except for options that need to call a function, all can be implemented
to add options to FlightGear without the need to program any code!
Yes, but usually, options refer to code. How use
Erik Hofman wrote:
> Frederic Bouvier wrote:
>
> > option has_param typeproperty b_param s_param
func
> > where:
> > option : name of the option
> > has_param : option is --name=value if true or --name if false
> > type : OPTION_BOOL - property is a boolean
> > OPT
Frederic Bouvier wrote:
option has_param typeproperty b_param s_param func
where:
option : name of the option
has_param : option is --name=value if true or --name if false
type : OPTION_BOOL - property is a boolean
OPTION_STRING - property is a string
OPT
Frederic Bouvier wrote:
I should have put that in a comment in the file at the first place.
Eric, can you add it for future reference.
BTW, the old way of testing options is ifdef'ed out and can be removed
now (look for NEW_OPTION_PARSING). Can you do it yourself our do you
want a patch ?
Okay, th
Martin Spott wrote:
Modified Files:
options.xml
Log Message:
Updated options from Erik Hofman
In some cases it would be _very_ useful for those who try to manage the
manual if there was a diff attached to the CVS 'loginfo' messages ;-)
I've added the command line options for MultiPlayer suppor
On Thursday 13 March 2003 7:13 am, Martin Spott wrote:
> [EMAIL PROTECTED] wrote:
> > Date: Wed Mar 12 16:07:34 EST 2003
> > Author: cvsroot
> >
> > Update of /home/cvsroot/FlightGear/FlightGear/Aircraft/f16/Panels
> > In directory dash:/tmp/cvs-serv31668/f16/Panels
> >
> > Modified Files:
> >
Martin Spott wrote:
Erik Hofman <[EMAIL PROTECTED]> wrote:
Martin Spott wrote:
I think, something went wrong here:
It looks like it, put the following file in FlightGear/Aircraft/f16/Panels:
http://www.a1.nl/~ehofman/fgfs/download/ded.xml
This one does the trick for the panel. I still see th
Erik Hofman <[EMAIL PROTECTED]> wrote:
> Martin Spott wrote:
>> I think, something went wrong here:
> It looks like it, put the following file in FlightGear/Aircraft/f16/Panels:
> http://www.a1.nl/~ehofman/fgfs/download/ded.xml
This one does the trick for the panel. I still see the glider from o
Martin Spott wrote:
I think, something went wrong here:
It looks like it, put the following file in FlightGear/Aircraft/f16/Panels:
http://www.a1.nl/~ehofman/fgfs/download/ded.xml
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flig
[EMAIL PROTECTED] writes:
> On 7 Mar 2003 at 8:42, Curtis L. Olson wrote:
>
> > Update of /var/cvs/FlightGear-0.9/FlightGear/src/ATC
> > In directory seneca:/tmp/cvs-serv18953
> >
> > Modified Files:
> > AIMgr.cxx AIMgr.hxx
> > Log Message:
> > Eeek! Emergency fix of a couple "case" problem
On Wed, 5 Mar 2003 17:19:30 -0600
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
http://www.flightgear.org/images/crop-variety.jpg
Wow. Now that looks like the areas surrounding Mpls.
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mai
Jon Stockill writes:
> On Wed, 5 Mar 2003, Gene Buckle wrote:
>
> > > [EMAIL PROTECTED] wrote:
> > >
> > > > New hi-res irregular crop texture.
> > >
> > > For eye-candy fetischitsts (is this an english word?)
> > > http://www.a1.nl/~ehofman/fgfs/download/irrcrop.jpg
> >
> > Damn, that's cool.
>
On Wed, 5 Mar 2003, Gene Buckle wrote:
> > [EMAIL PROTECTED] wrote:
> >
> > > New hi-res irregular crop texture.
> >
> > For eye-candy fetischitsts (is this an english word?)
> > http://www.a1.nl/~ehofman/fgfs/download/irrcrop.jpg
>
> Damn, that's cool.
yeah, VERY nice
--
Jon Stockill
[EMAIL PR
> [EMAIL PROTECTED] wrote:
>
> > New hi-res irregular crop texture.
>
> For eye-candy fetischitsts (is this an english word?)
> http://www.a1.nl/~ehofman/fgfs/download/irrcrop.jpg
Damn, that's cool.
g.
___
Flightgear-devel mailing list
[EMAIL PROTECT
* [EMAIL PROTECTED] (Erik Hofman) [2003.03.05 14:39]:
> [EMAIL PROTECTED] wrote:
>
> >New hi-res irregular crop texture.
>
> For eye-candy fetischitsts (is this an english word?)
> http://www.a1.nl/~ehofman/fgfs/download/irrcrop.jpg
Weight On Wheels
--
Cameron Moore
/(bb|[^b]{2})/
Martin Spott writes:
> "Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
>
> > Modified Files:
> > native_ctrls.cxx native_ctrls.hxx native_fdm.cxx
> > native_fdm.hxx
> > Log Message:
> > Add a net_byte_order flag so that the calling code can specify if network
> > byte order conversion is de
Martin Spott <[EMAIL PROTECTED]> wrote:
> foehn: 23:04:08 ~# cat /tmp/FIFO > /dev/rmt/0ln &
> foehn: 23:04:30 ~# rsh sirius tar cvfp - /usr/freeware > /tmp/FIFO
Just for completeness, of course you could also do this one, if you can't
persuade your FDM to write to STDOUT:
foehn: 0:55:19 ~# cat /
Martin Spott <[EMAIL PROTECTED]> wrote:
> # rsh cat FIFO > /dev/tape &
> # tar cvfp - /home FIFO
I've fiddled a bit and now I believe I know how I did it. Curt was true, you
probably can't run the FIFO over NFS. But there's another solution - I
believe it is the one I used for backups.
'foehn' i
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
> Martin Spott writes:
>> FIFO's via NFS:
>>
>> # rsh cat FIFO > /dev/tape &
>> # tar cvfp - /home FIFO
>>
>>
>> Synchronization works quite well,
> Really? What platform was this? Supposedly the Unix Programming FAQ
> says this won't work, but i
Martin Spott writes:
> You should try to export the filesystem containing the FIFO via NFS and
> mount it onto a remote machine running the FDM (or vice versa, maybe reading
> from the mounted fs is faster). I've done remote backups quite often using
> FIFO's via NFS:
>
> # rsh cat FIFO > /dev/ta
Martin Spott <[EMAIL PROTECTED]> wrote:
> # tar cvfp - /home FIFO
Ooops, swap these - should be:
# tar cvfp - FIFO /home
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
__
John Check <[EMAIL PROTECTED]> wrote:
> On Tuesday 25 February 2003 2:22 pm, Martin Spott wrote:
>> [EMAIL PROTECTED] wrote:
>> > Modified Files:
>> >f16.xml
>> > Log Message:
>> > improved f-16 from Erik Hofman
>>
>> Oh, _very_ nice, but eerm, did anyone manage to get the beast off
>> t
Curtis L. Olson wrote:
John Check writes:
On Tuesday 25 February 2003 2:22 pm, Martin Spott wrote:
[EMAIL PROTECTED] wrote:
Modified Files:
f16.xml
Log Message:
improved f-16 from Erik Hofman
Oh, _very_ nice, but eerm, did anyone manage to get the beast off
the runway without cras
On Tuesday 25 February 2003 3:40 pm, Curtis L. Olson wrote:
> John Check writes:
> > On Tuesday 25 February 2003 2:22 pm, Martin Spott wrote:
> > > [EMAIL PROTECTED] wrote:
> > > > Modified Files:
> > > > f16.xml
> > > > Log Message:
> > > > improved f-16 from Erik Hofman
> > >
> > > Oh, _v
John Check writes:
> On Tuesday 25 February 2003 2:22 pm, Martin Spott wrote:
> > [EMAIL PROTECTED] wrote:
> > > Modified Files:
> > > f16.xml
> > > Log Message:
> > > improved f-16 from Erik Hofman
> >
> > Oh, _very_ nice, but eerm, did anyone manage to get the beast off
> > the runway wi
On Tuesday 25 February 2003 2:22 pm, Martin Spott wrote:
> [EMAIL PROTECTED] wrote:
> > Modified Files:
> > f16.xml
> > Log Message:
> > improved f-16 from Erik Hofman
>
> Oh, _very_ nice, but eerm, did anyone manage to get the beast off
> the runway without crashing _before_ take-off ?
Carsten,
> Does this mean, the document is also part of cvs?
Luckily, indeed. Plus, it certainly will become part of the next official
release (if you don't object, of course).
> Can anyone give me a hand on how to continue writing using cvs?
> Where do I have to send or put new chapters?
Instr
Does this mean, the document is also part of cvs?
Can anyone give me a hand on how to continue writing using cvs?
Where do I have to send or put new chapters?
Thanks,
Carsten
Michael Basler schrieb:
>
> > Log Message:
> > Add Carsten Hoefer's excellent flight tutorial to help
> system
>
> Tha
David Luff writes:
> This is fantastic and works beautifully! Unfortunately the default startup
> at the moment leaves the magneto switch stuck in the starter position, and
> the only way to get it back so the above can work properly if required is
> to hit the space bar as before.
Can you f
David Luff writes:
> On 1/2/03 at 11:52 AM Curtis L. Olson wrote:
>
> >Another feature request would be to create a volume and on/off switch
> >property and honor them. Volume could go from 0.0 - 1.0 scaled
>
> BTW, can you hear the audio ATIS OK on your Linux box? There have been a
> few probl
On 1/2/03 at 11:52 AM Curtis L. Olson wrote:
>Another feature request would be to create a volume and on/off switch
>property and honor them. Volume could go from 0.0 - 1.0 scaled
BTW, can you hear the audio ATIS OK on your Linux box? There have been a
few problems reported with it over Christm
On 1/2/03 at 11:52 AM Curtis L. Olson wrote:
>David,
>
>Another feature request would be to create a volume and on/off switch
>property and honor them. Volume could go from 0.0 - 1.0 scaled
>appropriately, and on/off is pretty self explanitory. It would also
>be nice to have a "servicable" prope
David Luff writes:
> On 12/30/02 at 7:47 PM [EMAIL PROTECTED] wrote:
>
> >Date: Mon Dec 30 14:47:23 EST 2002
> >Author: cvsroot
> >
> >Update of /home/cvsroot/FlightGear/FlightGear
> >In directory bitless:/tmp/cvs-serv15423
> >
> >Modified Files:
> > preferences.xml
> >Log Message:
> >Changed
Norman Vine wrote:
>
> Michael Basler writes:
> >
> > > Christian Mayer wrote:
> >
> > > This gives ma an idea:
> > >
> > > Render only the @ to a picture and include this picture instead of the
> > > real @ sign in the address. I think this should fool enough
> > > address-harvesters.
> >
> > So
Norman,
> [mailto:[EMAIL PROTECTED]]On Behalf Of Norman Vine
> Sent: Tuesday, December 17, 2002 8:09 PM
> To: [EMAIL PROTECTED]
> Why not just use ' at ' instead of '@'
>
> note spaces surrounding 'at'
>
Something similar already occured to me but I've dismissed it as being
to ugly. If those n
Michael Basler writes:
>
> > Christian Mayer wrote:
>
> > This gives ma an idea:
> >
> > Render only the @ to a picture and include this picture instead of the
> > real @ sign in the address. I think this should fool enough
> > address-harvesters.
>
> Sounds like a cool idea as I'll only have t
Christian,
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christian
> Mayer
> This gives ma an idea:
>
> Render only the @ to a picture and include this picture instead of the
> real @ sign in the address. I think this should fool enough
> address-harvesters.
Sounds like a co
Michael Basler wrote:
>
> I tried this. It was still recognizable after conversion in the HTML. I
> simply searched for my address (Ctrl-GF in IE) and it was found :-( I tried
> several font changes etc. which all did not hide the address.
>
> A clever sign for/aft the @ being invisible but maski
Curt,
> Could you fake something as an equation:
>
> $ curt\@flightgear.org $
>
> latex2html would convert this to a graphic automatically ... although
> in equation mode you have to worry about things getting interpreted as
> equations and variables ...
Yes, latex2html does, but tex4ht which I
Michael Basler writes:
> Chrisitan,
>
> > Well, I think even addresses like
> >
> > something @ something.com
> >
> > aren't save against spammers.
>
> I guessed it.
>
> > So far the best recepie is to convert the address to little pixel
> > graphics and to include the images on the page.
>
>
Christian,
> Including images in LaTeX is no problem - that just leaves us with the
> problem how we are generating the images...
Exactly. Although the HTML converter might become a bit slow with 100+ pix.
Perhaps no serious problem.
> I'm sure that one of the Unix gurus knows a fast way to do t
On Tue, 17 Dec 2002, Michael Basler wrote:
> Chrisitan,
>
> > Well, I think even addresses like
> >
> > something @ something.com
> >
> > aren't save against spammers.
>
> I guessed it.
Sadly most will already have been harvested. I know that within a day of
the link to the slackware packages b
Michael Basler wrote:
>
> Chrisitan,
>
> > Well, I think even addresses like
> >
> > something @ something.com
> >
> > aren't save against spammers.
>
> I guessed it.
>
> > So far the best recepie is to convert the address to little pixel
> > graphics and to include the images on the page.
>
Chrisitan,
> Well, I think even addresses like
>
> something @ something.com
>
> aren't save against spammers.
I guessed it.
> So far the best recepie is to convert the address to little pixel
> graphics and to include the images on the page.
...which 100 or so graphics you are going to creat
Tony Peden wrote:
>>I think I've found what causes the instabillity in the F-16 model. It
>>looks like the axis systems and me don't get along quite well. Somehow
>>it always turns out to be different than what I've thought.
>
>
> Well, hmm. Which system are you getting hung up on.
Probably
On Sun, 2002-09-22 at 10:07, Erik Hofman wrote:
> [EMAIL PROTECTED] wrote:
> > Date: Sun Sep 22 11:21:02 EDT 2002
> > Author: cvsroot
> >
> > Update of /home/cvsroot/FlightGear/FlightGear/Aircraft/f16
> > In directory bitless:/tmp/cvs-serv6423/Aircraft/f16
> >
> > Added Files:
> > f16.xml
>
> On Thu, 2002-09-19 at 06:52, Alex Perry wrote:
> > The last ten degrees _are_ mostly drag, but that's what you need
> > (a) to get a steep final in rugged terrain
> > (b) for fast descents in emergency management
> > (c) for a relatively quick flare for short fields
> (d) to keep %N1 up (for fas
On Thu, 2002-09-19 at 06:52, Alex Perry wrote:
> > Does the R have a 40 deg flap detent?
>
> My understanding is that the 40 deg flap setting (over the whole family)
> is actually related to max gross weight. If you want the 40 deg then you
> will be limited to 2300 lb; if you make do with 30 d
Alex Perry writes:
> The last ten degrees _are_ mostly drag, but that's what you need
> (a) to get a steep final in rugged terrain
> (b) for fast descents in emergency management
> (c) for a relatively quick flare for short fields
Speaking of quick flares, I'm finally getting the hang of *ra
> I don't really object to that -- except that I wonder how many folks
> will be able to really tell the difference. Surely, even in the real
> thing, the differences are fairly subtle. I'm also not so sure that we
> have the fidelity that making that distinction implies.
I recommend the split,
> Does the R have a 40 deg flap detent?
My understanding is that the 40 deg flap setting (over the whole family)
is actually related to max gross weight. If you want the 40 deg then you
will be limited to 2300 lb; if you make do with 30 deg ... you can have more.
However, as the interior gets
On Thu, 2002-09-19 at 06:34, Tony Peden wrote:
> On Thu, 2002-09-19 at 06:19, David Megginson wrote:
> > Tony Peden writes:
> >
> > > Does the R have a 40 deg flap detent?
> >
> > No. The 172R and 172P allow up to 30deg flaps, but the 172M (mid
> > 1970s) goes to 40deg -- it feels like draggin
On Thu, 2002-09-19 at 06:19, David Megginson wrote:
> Tony Peden writes:
>
> > Does the R have a 40 deg flap detent?
>
> No. The 172R and 172P allow up to 30deg flaps, but the 172M (mid
> 1970s) goes to 40deg -- it feels like dragging a parachute.
That's typical. You get to a point with flap
Tony Peden writes:
> Does the R have a 40 deg flap detent?
No. The 172R and 172P allow up to 30deg flaps, but the 172M (mid
1970s) goes to 40deg -- it feels like dragging a parachute.
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
__
On Thu, 2002-09-19 at 05:27, David Megginson wrote:
> Tony Peden writes:
>
> > > My suggestion is that c172.xml (and --aircraft=c172) would disappear
> > > altogether, and we'd have c172p.xml and c172r.xml instead.
> >
> > I don't really object to that -- except that I wonder how many folks
Tony Peden writes:
> > My suggestion is that c172.xml (and --aircraft=c172) would disappear
> > altogether, and we'd have c172p.xml and c172r.xml instead.
>
> I don't really object to that -- except that I wonder how many folks
> will be able to really tell the difference. Surely, even in
On Thu, 2002-09-19 at 04:26, David Megginson wrote:
> Tony Peden writes:
>
> > The 48 in number checks with my copy of the POH (from which many
> > other numbers have been derived, so we should probably stick with
> > that)
>
> You've talked before about forking, and that might not be a bad i
Tony Peden writes:
> The 48 in number checks with my copy of the POH (from which many
> other numbers have been derived, so we should probably stick with
> that)
You've talked before about forking, and that might not be a bad idea.
Right now, we're more-or-less targetting a 172R, but the 48 n
On Wed, 2002-09-18 at 17:48, Jon Berndt wrote:
> > Is there some reasoning behind setting the steering gains according to
> > the brake selection? This makes no sense to me. It looks to me like
> > their needs to be a separate steering selection (or just specify the
> > gain in the config file).
> Is there some reasoning behind setting the steering gains according to
> the brake selection? This makes no sense to me. It looks to me like
> their needs to be a separate steering selection (or just specify the
> gain in the config file).
Agreed. I beg your indulgence - let me have a look at
On Wed, 2002-09-18 at 06:29, David Megginson wrote:
> Tony Peden writes:
>
> > I didn't look at everything, but the nose wheel was in NONE and the
> > mains CASTERED as far back as I looked (which went back to the beginning
> > of time for the configurable gear). I can't explain the CASTERED
Jon S Berndt writes:
> I may be guilty, here. Note that this file needs to be
> gone through again with a fine tooth comb and validated.
> Just when I think I can't become more overwhelmed than I
> already am ...
Wife pregnant with triplets again?
(Don't laugh, my wife has a friend who had tw
401 - 500 of 559 matches
Mail list logo
