On Wednesday 10 November 2004 11:08, Antonio Pennino wrote:
please verify the brakes and the dimension and visual
definition of the cockpit at the 800x600 resolution.
Wheel brakes are working as expected. The BRAKES indicator on the panel is
not working.
I think you should remove the ADF
From: Antonio Pennino [EMAIL PROTECTED]
Organization: Nocera Informatica
To: FlightGear developers discussions
[EMAIL PROTECTED]
Date sent: Wed, 10 Nov 2004 13:01:35 +0100
Subject:Re: [Flightgear-devel] Beech 99
Priority
On Wednesday 10 November 2004 13:01, Antonio Pennino wrote:
I think you should remove the ADF radio panel, since there is no
instrument to display the adf bearing. Alternatively add an adf bearing
indicator.
I use the 0.9.6 win32 binary. How i make it?
This question forces me to rethink
Funny you guys should be talking about turboprop models.
I have been playing around today trying to get a allison t56
working using jsbsim's aeromatic.But for what ever reason
the RPM just seems to keep climbing from the time you start
even though I had the max prop rpm set at 1450.The prop
did
Funny you guys should be talking about turboprop models.
I have been playing around today trying to get a allison t56
working using jsbsim's aeromatic.But for what ever reason
the RPM just seems to keep climbing from the time you start
even though I had the max prop rpm set at 1450.The
If you're connecting a prop to a turbine, that won't work. The present
turbine model can't be used as a turboprop. As a result, the best way to
model a turboprop is to use a turbine with a direct thruster, and
adjust the
thrust table to simulate a propeller (see the OV-10).
The issue is
If you're connecting a prop to a turbine, that won't work. The present
turbine model can't be used as a turboprop. As a result, the best way to
model a turboprop is to use a turbine with a direct thruster, and
adjust the
thrust table to simulate a propeller (see the OV-10).
The issue
Dave C. wrote:
Right. The relevant code from FGPropulsion is:
PowerAvailable =
Engines[i]-Calculate(Thrusters[i]-GetPowerRequired());
Thrusters[i]-Calculate(PowerAvailable);
vForces += Thrusters[i]-GetBodyForces(); // sum body frame forces
vMoments +=
On 4/30/04 at 7:02 AM Jon Berndt wrote:
Funny you guys should be talking about turboprop models.
I have been playing around today trying to get a allison t56
working using jsbsim's aeromatic.But for what ever reason
the RPM just seems to keep climbing from the time you start
even though I
Presently, the turbine model ignores PowerRequired and returns
pounds-force.
The Piston and Electric models use PowerRequired and return horsepower.
I think this is fixable - are you working on it? If not, I might take a
quick try at it.
Sure. I was going to first implement the
David Luff wrote:
The turbocharged piston engine is a completely different beast from a
turboprop though, I would imagine the latter has more in common with the
turbine model. OTOH, the Piper Navajo is a GA twin that uses turbocharged
piston engines, that might be a nice one to model.
Lots of GA
On Fri, 30 Apr 2004 13:57:03 +0100
David Luff [EMAIL PROTECTED] wrote:
The turbocharged piston engine is a completely different beast from a
turboprop though, I would imagine the latter has more in common with
the
turbine model. OTOH, the Piper Navajo is a GA twin that uses
turbocharged
piston
David Megginson wrote:
Lots of GA planes have an option turbocharged (or turbonormalized --
I'm not technie enough to remember the distinction)
I think it's certification. A turbonormalized engine has a wastegate
setting of normal atmospheric pressure. It never develops more power
than the
Curtis L. Olson wrote:
Anyone want to take a crack at a new FDM model for the Beech 99
as well? You could probably start with the data for the UIUC
model and go from there.
The Beech 99 is a turboprop, which means that YASim is going to
need new code to support it. I'd be happy to write it
Andy Ross wrote:
The Beech 99 is a turboprop, which means that YASim is going to
need new code to support it. I'd be happy to write it if someone
decides they want to go that way.
Doing so would open the way to a whole bunch of other interesting
turboprops, including the Beech KingAir (from
15 matches
Mail list logo
