Version: 1.4.20.0 (Also checked in SU3 Beta)
Frequency: Consistently
Severity: High
Marketplace package name: 67FL Bald Eagle Airfield- Myakka Head
Bug description:
I have a hangar door animation that is triggered using Behavior code. The animation works in 2020. The door is either fully opened or fully closed depending on several factors:
<Behaviors>
<Include ModelBehaviorFile="Asobo\Generic\Animations.xml"/>
<Component ID="Open">
<UseTemplate Name="ASOBO_GT_Anim">
<ANIM_NAME>Opening</ANIM_NAME>
<!-- Hangar open Dawn-Dusk on Sunday, Tuesday, Wednesday, & Saturday, while not raining.-->
<ANIM_CODE>(E:LOCAL DAY OF WEEK, Number) 1 == (E:LOCAL DAY OF WEEK, Number) 2 == || (E:LOCAL DAY OF WEEK, Number) 5 == || (E:LOCAL DAY OF WEEK, Number) 6 == || (E:TIME OF DAY, Enum) 3 < && (A:AMBIENT PRECIP STATE, Mask) 2 == && if{ 100 } els{ 0 }</ANIM_CODE>
<ANIM_WRAP>1</ANIM_WRAP>
<ANIM_LENGTH>100</ANIM_LENGTH>
</UseTemplate>
</Component>
</Behaviors>
To ensure that it wasn’t an issue with a Simvar, I have temporarily rewritten the code to only allow the door to open if it’s raining. Code that I know works, because I have other SimObjects using it currently without issue in 2024:
<Behaviors>
<Include ModelBehaviorFile="Asobo\Generic\Animations.xml"/>
<Component ID="Open">
<UseTemplate Name="ASOBO_GT_Anim">
<ANIM_NAME>Opening</ANIM_NAME>
<ANIM_CODE>(A:AMBIENT PRECIP STATE, mask) 4 == if{ 100 } els{ 0 }</ANIM_CODE>
<ANIM_WRAP>1</ANIM_WRAP>
<ANIM_LENGTH>100</ANIM_LENGTH>
</UseTemplate>
</Component>
</Behaviors>
Even with this simple code, I still cannot get the hangar door to open or close. When I use the Behaviors tool in the dev toolbar, I can see the current value in the Animations tab. Using Simvar Watcher I can see the precip state change with the slider, however on the Animations tab the value always remains 0/100. I can force this value to 100 and the hangar door does open.
Is there something that needs to be done differently for 2024? Am I missing something, or is this just a sim bug?
I did notice a template structure error in the Logs tab of the Behaviors tool. I’m not sure if that is part of the issue or not…