Quandary #1:  The button assignment below is calling the following script which works just fine when testing in the script editor:

1 (>K:THROTTLE_REVERSE_THRUST_TOGGLE)\n
(A:GENERAL ENG REVERSE THRUST ENGAGED:1, Number) 0 == if{(SPEAK:REVERSE THRUST ACTIVATED)} els{(SPEAK:REVERSE THRUST DEACTIVATE)}

Because the throttle is normally out my camera view on landing, I wanted to alert that the reverse thrust is active or not.  The script also works fine when using the "Test" button in the Change Button Assignment window. However, when I activate the button (which BTW is located at the bottom of my throttle axis handle on the Velocity One Quadrant) the event works but I do not get the SPEAK to work.  Wondering why not.

Quandary #2:  Because I don't want to accidentally activate the reverse thrust by moving the throttle axis into the "button area" I don't want the script to trigger until after a little bit of time has elapsed, giving me time to move the lever back to throttle idle.  In the setting for "Long Click" right now I have it set to one second.  However the this is not working as the event takes place immediately after engaging the button press.  Wondering about this as well.

As always I appreciate the support you give to us customers.  I  am an AAO advocate whenever the need arises in other places.

 

Regards.

55 minutes ago, n116dh said:

Wondering why not.

#1 Sorry, no idea. What I can tell you is that your script syntax looks incorrect to me. Is that really what the code looks like? It is missing a lot of space characters in crucial places. Also, I would use "(SPLIT:nnnn)" instead of "\n". Way less overhead in processing. Also, make sure to make the SPLIT long enough, so the plane logic has time to react and to engage reverse thrust. I wouldn't expect this to happen instantly, so maybe a (SPLIT:1000) or longer would be in order.

1·(>K:THROTTLE_REVERSE_THRUST_TOGGLE)·(SPLIT:100)·(A:GENERAL·ENG·REVERSE·THRUST·ENGAGED:1,·Number)·0·==·if{·(SPEAK:REVERSE·THRUST·ACTIVATED)·}·els{·(SPEAK:REVERSE·THRUST·DEACTIVATE)·}

#2: Working fine here. Didn't try it with your script though, I just made it send a simple (SPEAK:long)

btw. Scripts can be selected from the normal events treelist. No need to use MAN mode for your script.

 

55 minutes ago, n116dh said:

which works just fine when testing in the script editor:

Works fine for which aircraft and what simulator? If you want me to look at things, please (please) provide detailed instructions about how I can reproduce what you are seeing with as little effort as possible. Simulator and aircraft are essential information, because in my experience, scripts, events etc. rarely work the same on different aircraft - especially in the MSFS 20/24 world.

 

Edited April 29, 20251 yr by Lorby_SI

Greetings, just able to back to this and your suggestions have been affected and work fine.  I must say, sometimes I'm in a quandary sometimes as to how much info to provide for help, as I'm not sure if the problem is easily solvable or not, or if I might be doing TMI.  However, I will at least proved sim and aircraft in the future.  Thx