Crow
8th May 2008, 11:39 AM
Hi, Bob.
I looked at the thread below 'flaps setting in IL2' by thdees who did a good job there.
So I copied the algorithm pretty close for use in SH4 subsim, for the forward telegraph speed.
Here's the script, which works fine:
script
cms.a2 = js2.a3; // js2.a3 is throttle handle
cms.b6 = [cms.a2 > 240]; // engines all stop
cms.b7 = [cms.a2 > 200]; // engines 1/3
cms.b8 = [cms.a2 > 160]; // engines 2/3
cms.b9 = [cms.a2 > 120]; // engines standard
cms.b10 = [cms.a2 > 80]; // engines full
cms.b11 = [cms.a2 > 40]; // engines flank
endScript
With the cms buttons set to output the keystrokes for the engine speeds `,1,2,3,4,5.
The script works perfectly when moving the throttle handle slowly forward or even extremely fast.
But moving the throttle handle ridiculously fast backwards can yield the outputs out of correct order.
Which is no problem because all works perfect unless really yanking, but I'm curious why moving the handle forward extremely fast doesn't mess up the output?
I looked at the thread below 'flaps setting in IL2' by thdees who did a good job there.
So I copied the algorithm pretty close for use in SH4 subsim, for the forward telegraph speed.
Here's the script, which works fine:
script
cms.a2 = js2.a3; // js2.a3 is throttle handle
cms.b6 = [cms.a2 > 240]; // engines all stop
cms.b7 = [cms.a2 > 200]; // engines 1/3
cms.b8 = [cms.a2 > 160]; // engines 2/3
cms.b9 = [cms.a2 > 120]; // engines standard
cms.b10 = [cms.a2 > 80]; // engines full
cms.b11 = [cms.a2 > 40]; // engines flank
endScript
With the cms buttons set to output the keystrokes for the engine speeds `,1,2,3,4,5.
The script works perfectly when moving the throttle handle slowly forward or even extremely fast.
But moving the throttle handle ridiculously fast backwards can yield the outputs out of correct order.
Which is no problem because all works perfect unless really yanking, but I'm curious why moving the handle forward extremely fast doesn't mess up the output?