From: ghmalau <gh...@gm...> - 2010-09-29 12:31:47
|
Le mercredi 29 septembre 2010 13:56:39, Jon S. Berndt a écrit : > Gerard, > > Did you know that there is an "propulsion/active_engine" property? You can > set the active engine, and then set these properties - which will act on > the current engine specified in the "active_engine" property: > > propulsion/starter_cmd > propulsion/cutoff_cmd > > The engines are numbered from 0 to n, in the order that they appear in the > configuration file. > > Jon > Hi Jon, Yes i know, The configuration jsbsim used with FG , does not work , i could not identify the cause. However when i am using the similar feature within FG , which i guess, trigger jsbsim , it does work. That feature is done by an embedded Nasal script ( there is not any exposed property about it ), which is probably useful with YASim. Thus that process is hidden. The jsbsim FDM which work stand alone, with the property you refer to, don't with FG. To me, any stand alone FDM jsbsim should work FG. which is not the case. You may look at that "ugly"FG input done to start the engines ( extracted from the Nord-2502). We could have the same elegant process, with only jsbsim, working stand alone, and working with FG, which should use the jsbsim property, and trigger FG ( why not) when used. Thanks Cheers gérard |