I wrote:
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:flightgear-devel-
> [EMAIL PROTECTED] On Behalf Of Vivian Meazza
> Sent: 18 June 2005 11:23
> To: 'FlightGear developers discussions'
> Subject: RE: [Flightgear-devel] New turbo/supercharger code
>
> Andy Ross
>
> > Vivian Meazza wrote:
> > > Engines/engine/boost-pressure-psi-gauge = 46.00167 (correct order of
> > > boost)
> >
> > Can you try it with the CVS code? This may be interacting badly with
> > your local changes, which makes debugging difficult. Nothing in this
> > mechanism should require any of the new code.
> >
> Here's the result of the short experiment conducted using a clean download
> of the YASim directory from this morning cvs-HEAD:
>
> This is the entry in the config file
>
> <control-input axis="/controls/engines/engine[0]/boost-control"
> control="THROTTLE"/>
>
> Here is the setting in the property browser
>
> Controls/engines/engine/boost-control= 1.0
>
> Here is the output in the property browser
>
> Engines/engine/mp-inhg = 145.518585
> Engines/engine/prop-thrust = 4230.001953
> Velocities/airspeed-kt = 45.839
>
> Same outcome. I guess that something somewhere isn't reading the input
> axis.
Ok - problem solved, or rather, cause identified. The solver is failing
silently. This is the output:
YASim solution results:
Iterations: 1
Drag Coefficient: 1000
Lift Ratio: 1
Cruise AoA: 0
Tail Incidence: -0
Approach Elevator: 0
CG: -3.412, 0.000, -0.201
I would deduce that the property:
Controls/engines/engine/boost-control
Does not exist when the solver runs. So now to try to get around that one.
V.
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
