Vivian Meazza wrote:
> I would deduce that the property:
> Does not exist when the solver runs.
It should still see a zero for undefined properties, although you can
make arbitrary property settings in the approach/cruise definitions up
at the top. Some of the aircraft
Note again, though, that you appear to have a case bug. The property
tree name is "controls", not "Controls".
I would back out your changes to the last version that works and
re-add them one at a time. The change to the property input for the
throttle control will not cause a change in solution results.
Something else must have been modified.
Flightgear-devel mailing list