David Megginson writes:
> Andy Ross writes:
>
> > I have limited experience here, but the nosewheel shimmy I noticed in
> > a friend's PA-180 was only a rumble. It didn't seem to effect the
> > orientation or handling of the aircraft.
>
> If it's bad enough, the whole plane shakes (we'
Andy Ross writes:
> I have limited experience here, but the nosewheel shimmy I noticed in
> a friend's PA-180 was only a rumble. It didn't seem to effect the
> orientation or handling of the aircraft.
If it's bad enough, the whole plane shakes (we've had trouble with the
nose strut on C-GPMR
Andy Ross writes:
> Does this really have to be modeled, per se? Until we get support for
> force-feedback rudder pedals and seat cushions, the only thing we can
> reasonably do is play a sound. That can be done already with some
> fancy thresholding (gating with /gear[0]/wow and groundspeed) us
David Megginson wrote:
> I cannot say. One thing we're not modelling yet is nosewheel
> shimmy:
Does this really have to be modeled, per se? Until we get support for
force-feedback rudder pedals and seat cushions, the only thing we can
reasonably do is play a sound. That can be done already
Tony Peden writes:
> > In real life, it's also much harder to do a tail strike than it is
> > with the JSBSim 172 -- it's quite safe to pull all the way back on the
> > yoke to keep the weight off the nosewheel.
>
> Hmm, downwash (or, more precisely, the lack thereof)
I cannot say. One th
On Thu, 2002-10-10 at 11:54, David Megginson wrote:
> Curtis L. Olson writes:
>
> > > Don't say that. You know what'll happen _now_ when you next fly ...
> > > Also, although I've said it before, don't forget to practice a bit,
> > > before flying to an airshow or other event with _many_ spec
> In real life, it's also much harder to do a tail strike than it is
> with the JSBSim 172 -- it's quite safe to pull all the way back on the
> yoke to keep the weight off the nosewheel.
Try playing with your CG in JSBsim; I routinely see aircraft with their
tail tiedown heavily abraded due to exc
Curtis L. Olson writes:
> > Don't say that. You know what'll happen _now_ when you next fly ...
> > Also, although I've said it before, don't forget to practice a bit,
> > before flying to an airshow or other event with _many_ spectators !
>
> Would you like to buy a pair of slightly used C
Alex Perry writes:
> > David (who hasn't bounced for a few weeks now)
>
> Don't say that. You know what'll happen _now_ when you next fly ...
> Also, although I've said it before, don't forget to practice a bit,
> before flying to an airshow or other event with _many_ spectators !
Actuall
Alex Perry writes:
> > David (who hasn't bounced for a few weeks now)
>
> Don't say that. You know what'll happen _now_ when you next fly ...
> Also, although I've said it before, don't forget to practice a bit,
> before flying to an airshow or other event with _many_ spectators !
Would you lik
> David (who hasn't bounced for a few weeks now)
Don't say that. You know what'll happen _now_ when you next fly ...
Also, although I've said it before, don't forget to practice a bit,
before flying to an airshow or other event with _many_ spectators !
__
Jon Stockill writes:
> (No laughing when I bounce the landing!)
Why not? People laugh at me when I do it, so it's quite realistic.
It's even worse nowadays since the smokers have to go outside even
when it's not sunny and warm.
All the best,
David (who hasn't bounced for a few weeks now)
On Thu, 10 Oct 2002, David Luff wrote:
> Once you get this working we all ought to have a communal virtual fly-in at
> David M or Alex's local airports sometime :-)
Now *THAT* would be truly impressive.
(No laughing when I bounce the landing!)
--
Jon Stockill
[EMAIL PROTECTED]
_
> On 10/7/02 at 5:50 AM ace project wrote:
> >/network/pilot[n]/callsign
> >/network/pilot[n]/position/ (lat,alt, etc)
> >/network/pilot[n]/[network-module-name]/ (module
> >specific stuff)
I think that is fine, but ...
* I recommend you explicitly state that the 'n' for the same callsign
is l
On 10/7/02 at 5:50 AM ace project wrote:
>I want to know how you guys want the property list to
>be organised. Do we use something like:
>
>/network/pilot[n]/callsign
>/network/pilot[n]/position/ (lat,alt, etc)
>/network/pilot[n]/[network-module-name]/ (module
>specific stuff)
>
>I will need this
I want to know how you guys want the property list to
be organised. Do we use something like:
/network/pilot[n]/callsign
/network/pilot[n]/position/ (lat,alt, etc)
/network/pilot[n]/[network-module-name]/ (module
specific stuff)
I will need this soon(3 weeks tops), as my little
coding is getting
16 matches
Mail list logo