|
From: Ron J. <wi...@je...> - 2012-10-29 02:56:30
|
On Sunday 28 October 2012 19:10:57 Jon S. Berndt wrote: > > I think for now I will push a fix to the property names in FGFDMExec. > > As it sits right now the defaults can't be set from a script or the > > command line since the properties they depend on don't exist. Also, I'm > > going to make sure everything that's read gets set. > > > > Ron > > It's possible that the property names are supposed to be as they are. I'm > not sure why that would be, though. > > Jon It looks like this is the last patch James applied to his tree. He called it "Adding simplex support to scripts." He may have intended to use the trim/guess/ properties in functions to set the trim/solver properties. I'm kind of iffy about always creating a whole bunch of solver properties. But pre-creating them is the only way to enable specifying a value in a script or on the command line. So, as long as we seem to need them, we should make them the live properties and not depend on a scripted layer to set a second set of properties? I also think the creation should be moved out of FGFDMExec, and the default values should be set with the property getters in src/initialization/FGSimplexTrim, but I will leave the organization for now. The change I pushed today enables the script 737_cruise_steady_turn_simplex.xml to function. It seems to lock whatever the current flight conditions are, so as written we get a 2500 fpm descent. Setting engine throttles to .75 and decreasing the delay for trim to run to 1 second works much better. Ron |