• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS ModelBehaviorDefs parameters with the Process attribute: evaluate at load-time or run-time?

tml

tml

Messages
89
Country
finland
I had assumed that when a parameter declaration has the Process attribute, that means that the parameter value (the text inside the element) is a RPN expression, typically containing references to other parameters like #FOO#, to evaluate, to get the parameter's value. As in this example in the SDK documentation:
XML: 
<MIN_SPEED_TAKEOFF_LIFT Process="Float">#MIN_SPEED_TAKEOFF_HYDRAULICS# 0.45 *</MIN_SPEED_TAKEOFF_LIFT>

However, in the ASOBO_ENGINE_Throttle_SubTemplate template in Asobo/Common/Subtemplates/Engine_Subtemplates.xml, I now notice this:
Code: 
<DRAG_MIN_VALUE Process="Int">(A:THROTTLE LOWER LIMIT, position 16k)</DRAG_MIN_VALUE>

which clearly can not be evaluated while a model XML is being loaded, but is intended to be evaluated at run-time while the aircraft is flying. Is this just a mistake, and the simulator gracefully ignores the Process attribute if it can't be evaluated at load-time?
 
You must log in or register to reply here.
Back
Top