This pulls the spd button

(>IE:INSTRUMENT_FCU_SPD_PULL)

The problem is that it stays pulled and does not go back to the "neutral" position.  I have tried a number of things but to no avail.  Any ideas? 

It seems that when using the mouse, the pull happens on the down click and the release to neutral on the mouse release.  If that helps. 

Edited December 27, 20241 yr by Crabby

1 hour ago, Crabby said:

This pulls the spd button

(>IE:INSTRUMENT_FCU_SPD_PULL)

The problem is that it stays pulled and does not go back to the "neutral" position.  I have tried a number of things but to no avail.  Any ideas? 

It seems that when using the mouse, the pull happens on the down click and the release to neutral on the mouse release.  If that helps. 

The value is missing. The value that you send to an IE is very important.

Without knowing the required value(s) I'm just guessing - for starters I would assign

1 (>IE:INSTRUMENT_FCU_SPD_PULL)
to the Key down

and 

0 (>IE:INSTRUMENT_FCU_SPD_PULL)
to the Key up.

Something like that.

 

Edited December 27, 20241 yr by Lorby_SI

1 hour ago, Crabby said:

This pulls the spd button

(>IE:INSTRUMENT_FCU_SPD_PULL)

The problem is that it stays pulled and does not go back to the "neutral" position.  I have tried a number of things but to no avail.  Any ideas? 

It seems that when using the mouse, the pull happens on the down click and the release to neutral on the mouse release.  If that helps. 

Forget what I wrote above. Looking at the behavior code, there is no way to reset this knob. They have bound the mouse button press and release to an O: variable, which are specific to the actual component object - they cannot be accessed from the outside.

That being said, this is just a visual issue, not a functional one. The animation isn't reset, but that's all that happens from what I can tell. You can even still turn the knob.

Edited December 27, 20241 yr by Lorby_SI

I was thinking it was something like that.  I played with all the numbers like you first suggested, guess I should have said that.  

Now I am trying to figure out the increase and decrease for the actual speed, altitude and heading and v/s numbers.  I wish developers would stop getting cute with their coding.  Makes everything a pain in the word not allowed.  

1 hour ago, Crabby said:

I was thinking it was something like that.  I played with all the numbers like you first suggested, guess I should have said that.  

Now I am trying to figure out the increase and decrease for the actual speed, altitude and heading and v/s numbers.  I wish developers would stop getting cute with their coding.  Makes everything a pain in the word not allowed.  

When there is an IE, it can often also be accessed as a BVar. Those might be more convenient. The BVar has the same name with a "do-word" at the end. You can see them in the behavior code too, using Ctrl-G

1 (>B:INSTRUMENT_FCU_SPD_Knob_Inc)
1 (>B:INSTRUMENT_FCU_SPD_Knob_Dec)

1 (>B:INSTRUMENT_FCU_HDG_Knob_Inc)
1 (>B:INSTRUMENT_FCU_HDG_Knob_Dec)

1 (>B:INSTRUMENT_FCU_ALT_Knob_Inc)
1 (>B:INSTRUMENT_FCU_ALT_Knob_Dec)

1 (>B:INSTRUMENT_FCU_VS_Knob_Inc)
1 (>B:INSTRUMENT_FCU_VS_Knob_Dec)

You can enter them manually on the Button assignment dialogs too, by switching the green slider to MAN

 

Edited December 27, 20241 yr by Lorby_SI