Version: *1.7.16
Frequency: Consistently
Severity: *Low
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)
Marketplace package name: if applicable
Context: What package? When editing or mounted from Community? In main menu or in flight? etc…
Similar MSFS 2020 issue: insert url here if applicable
Bug description:
There is missing information on the use of XML Dynamic parameters with @var suffix.
example:
<DynamicParameters>
<OIL_CAP_ANIM_ID>'OIL_CAP@Exterior'</OIL_CAP_ANIM_ID>
<ENGINE_ID>1</ENGINE_ID>
</DynamicParameters>
The Oil cap animation name is a variable that defaults in this case to OIL_CAP and then there is an @Engine. I assume this is an Alias of the Exterior model simattachment for the exterior given in the attachedObjects.cfg file.
The DA62 sample has a couple oil dipsticks - one in each engine. Engine_L and Engine_R simattachment alias.
The attached_objects.cfg for the oil dipstick has that added
behavior_parameter.0="OIL_CAP_ANIM_ID,'ENGINE_CAPS_OIL_1@Engine_L'"
behavior_parameter.1="ENGINE_ID,1"
This is so the [OIL_CAP_ANIM_ID] XML dynamic parameter gets assigned with a value of
‘ENGINE_CAPS_OIL_1@Engine_L’.
I guess the key here is that:
- the ’ or @Engine (EDIT: my error - change from apos); makes this a string literal.
- the @ sign is NOT a macro but a delimiter to separate out the animation name value with the alias of the model that the animation name is held.
They only explanation I can find in the DOCs is
Please add more description to any and all combinations of XML dynamic parameters.
Am I correct in my above explanation? Are there more permutations to how XML dynamics params can be set up?
Repro steps:
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content