Andy Ross writes:
> Curtis L. Olson wrote:
> > David, (Andy?)
> >
> > It appears that in the latest cvs, we have lost the ability to control
> > the engines independently.
>
> This one is mine. The recent Nasal stuff contains a rework of the
> engine handling to allow for arbitrary numbers of engines, and avoid
> the "why are there 10 engines on the skyhawk?" issue.
The engine selection code seems to work ok based on examining the
property tree.
It seems like the stepMagnetos() and startEngine() routines must be at
fault. But I agree, from an initial reading, I don't see any obvious
faults.
I see this also with --aircraft=c310 which I believe is a jsbsim
aircraft.
> > Previously you could type <Shift-1> <Shift-2> <Shift-3> ... etc. to
> > select an engine. Then '{' and '}' would select the magnetos.
> > Finally, "space bar" would kick in the starter motor for as long as it
> > was depressed.
>
> Let me take a look. I presume you're seeing this with the DC-3? The
> code (selectEngine(), stepMagnetos() and startEngine() in
> controls.nas) looks more or less correct at first reading. I'm pretty
> sure I remember testing this with a multiengine aircraft...
Ok, thanks for looking into this, hopefully it is something simple.
Curt.
--
Curtis Olson HumanFIRST Program FlightGear Project
Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org
Minnesota http://www.flightgear.org/~curt http://www.flightgear.org
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
