Does anyone have scripts for the latest version of the Ejets? The ones on .to don't seem to be working any longer. Specifically, the ones for increase and decrease the altitude.

This is the script (from .to that use to work). I have found no modification to make it work

L:FSS_EXX_FGC_ROT_POS_ALT,·Number)·0.028·+·(>L:FSS_EXX_FGC_ROT_POS_ALT,·Number)

Not even sure what the 0.028 is for. They used it in all rotary knob scripts. The altitude version "works" but it does not land on either 1000s or 100s consistently.

Edited Monday at 08:25 PM1 day by Crabby

Which one of the EJets? When was that latest version released? And for what simulator?

I haven't looked at them in a long time, but I do own them. I could look into this tomorrow night.

Edited Monday at 08:28 PM1 day by Lorby_SI

If you want to check it out yourself, activate MSFS developer mode, open "Tools->Behaviors", then click back into the sim, hover the mouse over the knob/button/lever that you are interested in and press "Ctrl - G". This will bring up the behavior code - take a look at the "MouseRect" part, that will show you the code that is executed when you are using the mouse - that is what you want to replicate in AAO. Usually, just using part of the code is enough.

1 hour ago, Crabby said:

(L:FSS_EXX_FGC_ROT_POS_ALT,·Number)·0.028·+·(>L:FSS_EXX_FGC_ROT_POS_ALT,·Number)

That is still working for me. It increases the altitude by 1000 feet. Please note that your script is missing a bracket at the beginning.

And this would be the hundreds:

(L:FSS_EXX_FGC_ROT_POS_ALT,·Number)·0.0028·+·(>L:FSS_EXX_FGC_ROT_POS_ALT,·Number)

1 hour ago, Lorby_SI said:

That is still working for me. It increases the altitude by 1000 feet. Please note that your script is missing a bracket at the beginning.

And this would be the hundreds:

(L:FSS_EXX_FGC_ROT_POS_ALT,·Number)·0.0028·+·(>L:FSS_EXX_FGC_ROT_POS_ALT,·Number)

I am not seeing any difference in the two scripts (one for 100 and one for 1000)

2 hours ago, Lorby_SI said:

Which one of the EJets? When was that latest version released? And for what simulator?

I haven't looked at them in a long time, but I do own them. I could look into this tomorrow night.

Latest release and I am on AAO 4.60 b09

10 minutes ago, Crabby said:

I am not seeing any difference in the two scripts (one for 100 and one for 1000)

0.028 and 0.0028

Oh yes. The dreaded extra zero. Old eyes. I still cannot get this to work creating changes in even 100's or 1000's. Not my script work. I got it from .to, but definitely not working "correctly" on my side.

This is what I have for increase ALT: (L:FSS_EXX_FGC_ROT_POS_ALT,·Number)·0.028·+·(>L:FSS_EXX_FGC_ROT_POS_ALT,·Number)

It "works" but it will add some one hundred increments too. So it will go from let's say 0 to 1000 to 2000 then 2700 then 3700 then 15900 all the way to 39900 then 40000 etc.

For speed: (L:FSS_EXX_FGC_ROT_POS_SPD,·Number)·0.028·+·(>L:FSS_EXX_FGC_ROT_POS_SPD,·Number). Does not move the speed at all. In either the "+" or "-" version of the script.

Ok. Went into developer mode and I learned an important lesson: I wish I was as smart as you guys.

Here is what I currently have for a speed knob script:

(L:FSS_EXX_FGC_ROT_POS_SPD,·Number)·0.028·+·(>L:FSS_EXX_FGC_ROT_POS_SPD,·Number)

I have set this to my HC Bravo as a dual input with the right knob spinning to the right, button 12 and the assigned combo to button 16 (the IAS notch). I set the decrease script the same way except button 13 on the right hand knob. Speed does not move in either case. I have verified that this combo works with other scripts on other planes so it is not hardware.

I also tried binding directly in the sim and I could not get that to work either.

I took pictures of the mousereact from developer mode and my settings, but I guess the forum does not allow image upload.

Edited 15 hours ago15 hr by Crabby

3 hours ago, Crabby said:

It "works" but it will add some one hundred increments too. So it will go from let's say 0 to 1000 to 2000 then 2700 then 3700 then 15900 all the way to 39900 then 40000 etc.

That happens because the "0.028" isn't exactly right. The correct scripts would look like this:
(L:FSS_EXX_FGC_ROT_POS_ALT,·Number)·1·36·/·+·(>L:FSS_EXX_FGC_ROT_POS_ALT,·Number)
(L:FSS_EXX_FGC_ROT_POS_ALT,·Number)·1·360·/·+·(>L:FSS_EXX_FGC_ROT_POS_ALT,·Number)

2 hours ago, Crabby said:

I could not get that to work

From my perspective, this aircrafts controls system is broken. None of the InputEvents work (which they should) nor are their bindings working. The developer went to great lengths implementing them - but they are all non-functional. I was able to get one of them working partially (I was able to reduce the AP speed...), but that was it.

I'd say that the E-Jets are officially unusable with AAO. It is up to the aircraft developer to at least implement his IEs properly - that is the way that this stuff should be implemented. Fooling around with the animation LVars from the outside is a bad choice.

Edited 10 hours ago10 hr by Lorby_SI

5 hours ago, Lorby_SI said:

From my perspective, this aircrafts controls system is broken. None of the InputEvents work (which they should) nor are their bindings working. The developer went to great lengths implementing them - but they are all non-functional. I was able to get one of them working partially (I was able to reduce the AP speed...), but that was it.

I'd say that the E-Jets are officially unusable with AAO. It is up to the aircraft developer to at least implement his IEs properly - that is the way that this stuff should be implemented. Fooling around with the animation LVars from the outside is a bad choice.

Yea. Being able to reduce the AP speed only was exactly what I saw. Nothing has worked for increasing.