Try the following patch to c172.xml, which makes the takeoff-rpm
modification I talked about*. Hopefully things will be more to your
liking; the aircraft maxes out at 2100 RPM while stopped, then the
speed increases to something more like cruise as the airspeed grows.
If you look carefully, you'll actually see the RPM drop very slightly
before it starts increasing. The physical reason for this is that the
blades are "unstalling". As the flow attaches to them, they
experience a sharp increase in induced drag. I was pretty pleased to
notice this little tidbit; it kinda validates the model in an obtuse
way. That being said, I have *no* idea if this effect is noticeable
in a real aircraft. Alex?
This is sufficient to keep the wings level in cruise at 3000 ft, 2200
RPM; the value will have to change as we make changes to the model.
Note that a stock Cessna 172 does not have an aileron-trim wheel
inside the cockpit; to set the trim, you actually bend a sheet of
metal by hand when the plane is on the ground.
lot, since otherwise a property that is never set or tied by
FlightGear itself will always be kept as a string and converted on
each access. That's why fgGetBool and friends could take up a lot of
processor time sometimes.
These add a NEW elevator trim marker
along side the elevator position gauge
also adds missing cemterpoint tick marks
FYI
With this you can see what the AutoPilot is doing
when in one of the 'altitude modes'
Andy's virtual-panel support. This will give a first taste of flying
with a 3D cockpit, but there are many caveats:
1. Clicking on the instruments doesn't work (waiting for a fix from
Andy).
2. The instruments rotate with the 3D cockpit but they don't tilt with
it (also waiting for a fix from Andy).
3. The orientation is incorrect when the view is not straight-forwards
and the plane is not flying level (waiting for a fix from me, but I
don't understand matrix math well enough).
4. The 3D interior is fairly ugly right now.
I just checked in YASim changes that allow for more cleaner export of
control output to the property tree (and flaps now extend slowly now,
to boot). But this breaks the XML syntax in an incompatible way, so
you'll need to update your planes in order to run the code in CVS.
