Andy Ross wrote:
As far as I can see, there is no generic implementation possible
for turbine startup and shutdown. Everything would have to be
done specifically for each engine type. Maybe the best thing to
do would be to expose some appropriate inputs to the engine
code (running or not, current RPM, station temperatures, etc...)
and implement the details per-engine in Nasal...
I'm wholely open to suggestions.
FWIW: why do people care about this stuff so much? Engine
startup and shutdown is a boring, algorithmic, checklist task.
It's not exactly what I'd call fun, and it certainly won't ever
be implemented at a fidelity level useful for flight training.
What's the deal? :)
There are people in the world that are actually looking at FlightGear
for building training simulators (certified and not certified) and these
people are actually quite interested in the nit-picky details of engine
operation.
I remember hearing a story some time back (and I've forgotten most of
the details) but the gist of it was that the military purchased an
advanced helicopter simulator for one of their helicopters. They ended
up using it primarily as an engine startup/shutdown procedural and as a
result saved millions of dollars in burned out engines on the real
helicopters. Apparently there were some subtle operational points in
the real helicopter that the rookies would miss at first, but they'd end
up destroying engines when they trained in the real thing.
You are just going to have to face up to the facts Andy. You built a
"toy" that was so fun and useful, that people want to use it for real
"work."
Curt.
--
Curtis Olson http://www.flightgear.org/~curt
HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
