MSFS Common problem with rotating knobs

[eric_marciano]

Hello experts,

I am not an expert in virtual cockpit animations and I am facing a problem that I believe is very common:
I created an animation for a rotating knob that controls a local variable that varies from 0 to 359 degrees, and like the HEADING or COURSE knob in many cockpits, it can turn endlessly in both directions. Turning clockwise increases the value and when the value reaches 360, it is reset to 0 and can keep increasing. Same for anticlockwise, decreasing.
The XML code in the interior model file looks like this:

<Component ID="MyCompenentID" Node="MyNode">
<Update Frequency="2.0">
(O:IsInit) ! if{ 1 (&gt;O:IsInit) 0 (&gt;L:MyLocalVariable, number) }
</Update>
<UseTemplate Name="ASOBO_GT_Knob_Finite_Code">
<ANIM_NAME>My_Rotating_Knob</ANIM_NAME>
<ANIM_CODE>(L:MyLocalVariable, number) 1 *</ANIM_CODE>
<ANIMTIP_0>OFF</ANIMTIP_0>
<ANIMTIP_1>AUTO</ANIMTIP_1>
<ANIMTIP_2>ON</ANIMTIP_2>
<ANIM_LENGTH>360</ANIM_LENGTH>
<CLOCKWISE_CODE>
(L:MyLocalVariable, number) ++ d 359 &gt; if{ 0 } (&gt;L:MyLocalVariable, number)
</CLOCKWISE_CODE>
<ANTICLOCKWISE_CODE>
(L:MyLocalVariable, number) -- d 0 &lt; if{ 359 } (&gt;L:MyLocalVariable, number)
</ANTICLOCKWISE_CODE>
</UseTemplate>
</Component>

It works well, but... When I turn the knob clockwise using the mouse wheel and reach the value of 359, increasing once more resets it to 0. The value is correct, but the animation is wrong because the knob turns counterclockwise to reflect the value of 0. It is the same the other when I decrease and reach the value of 0, decreasing again sets the value to 359 and the animation is wrong.
The strange thing is that if I use the mouse button of the left/right of the knob to decrease/increase the value, everything works perfectly.
I am sure it is a common problem some of you already had, I am sure there is solution.

Thanks for any help,
Eric

 

[Lagaffe]

Hi,
How many keyframes are used for 0 to 360 ° ? I create in such occasion, 5 keyframes: 0, 90, 180, 270, 360

 

[eric_marciano]

The code I copied here is simplified. In my code I have 36 key frames, which means the knob turns 10° for each increment/decrement. But it doesn't change the problem...

Let's say I use the same technique as you do, with 5 key frames, how would it solve my problem? My understanding is that the problem remains the same: when you increase the value a change from 5 to 0, the knob will turn counter clockwise as if you set it to 0. Am I wrong?

Eric

 

[Anthony31]

Is there a infinite_code template? Because an infinite knob is one that continuously rotates. Finite implies there are limits. The roll back to keyframe zero implies there is a <Lag> parameter in the animation in the template as this is a common issue with lag and animations.

 

[B21-soaring]

As Anthony, I'm guessing the ASOBO_GT_Knob_Finite_Code is propagating an <ANIM_LAG> value other than 0 down through the sub-templates, probably ending up in Asobo_GT_Anim. Maybe try adding <ANIM_LAG>0</ANIM_LAG> as another parameter into the ASOBO_GT_Knob_Finite_Code (no guarantees, it completely depends how that template is written), or find another template.

 

[eric_marciano]

I don't understand, I wrote a reply after Anthony's post and I don't see it now, was it deleted?
Anyway, I was saying that setting ANIM_LAG to 0 solved the problem, and I thank Anthony for his help.

Now I saw that both finite and infinite templates have ANIM_LAG set to 100, but if I set it to 0 in my component, it overrides the value defined in the template and it works

 

[Lagaffe]

if I set it to 0 in my component, it overrides the value defined in the template and it works

Yes, it is the normal functioning of a template:
- propose default values and
- in the instantiation overload the desired values to adapt to its need