A fix for Full Axis throttle mapping

[AmazngSniperMan]

Hey, Im trying to get this script to work for me and am having some trouble. I have the X52 pro as well, my problem is that in the control panel test area when i run the script and move the throttle the input moves all over the spectrum and can't seem to find how much power im putting in unless i leave it still. In ArmA this is translating into only feeding power at 100% throttle.

Heres my script:

PPJoy3.analog2 = (MapRange(-Joystick3.Z, -1, 1, 0, 1))
debug = joystick3.z

[jestera]

Or more easily if you are on windows 7 go
ctrl pannel
devices and printers
Then right click on your joystick e.g. Cyborg X
Game controller settings
Properties
Deadzones
Find your Z Axis details

You will have 4 markers you can slide around to customise your axis
For ARMA 2 you want to first of all right click and ensure the deadzones are not linked
Then drag all 3 of the left most markers to the far left and right most to the far right.

You can test what this does on the TEST page after applying.

Basically to begin with the slider will go up very quickly with minimal movement until halfway, where it will slow down and cover the remaining axis very slowly.

It isnt perfect there is effectively a small deadzone at the beginning of the throttle to about 5-10% throttle, but it is effective, requires very little mucking around with programs and has absolutely zero risk of downloading the wrong thing and being riddled with trojans.

Also if you play other games you must remember to set it back to normal (clear deadzone).

Something similar can be done on XP however it is slightly more complicated.

[Fruity_Rudy]

When i'm using this on my hotas, i can't take off with chopper unless i'm on 51% of throttle. When i put the throttle up to like 5% , engine of chopper starts, but i can't take off..i have to put the slider on more then the middle. I think thats not the intention of this script right?

[Fruity_Rudy]

I still don't get it

This isn't the way a real chopper works, its not like a jet, there should be no decrease thrust at all. As You stand 0-50% thrust in a chopper does absolutely nothing for You in game without this fix. Being at 1% is the same as being at 49%. The increase thrust should be mapped to the full scope of the throttle 0-100%, not just the top 50-100%

I did exactly what you said wiht ppjoy and pie, i mapped it ingame. When i push the throttle away from me, nothing happens till i reach 51% , then chopper starts taking off

[doveman]

Whilst this is supposedly fixed in the beta by mapping both axis of the throttle to thrust, I just tried this and found it still doesn't work as well as using PPJoy/GlovePIE. With the later, by adjusting the sensitivity to about 60% in ArmaII, in Auto-Hover with the throttle at mid-point it maintains altitude and above/below midpoint I can increase/decrease altitude at variable rates. Mapping the throttle in ArmaII directly, at mid-point and even below the helicopter increases altitude when in auto-hover and I don't have the same precision in controlling altitude. I tried adjusting the sensitivity all the way from 60% down to 0% but it doesn't make any difference, unlike with the PPJoystick where it allows me to fine-tune the collective response to achieve "maintain altitude at mid-point".

[Fruity_Rudy]

How do you adjust the sens for throttle ingame, i mean i use ppjoy and glovepie too, and its superb. but for me it's not really middle pos when i hover. Which sens did you put to 60% ? I'm not at home and i never touched the axis like that..and additionally, i'm stupid

[doveman]

If you click on Controllers at the bottom, you'll see the PPJoystick and then highlight that and click on Customise and you'll see the Sensitivity bars. For me it's the Z axis I needed to adjust but it will be whichever axis you have mapped to Thrust (Analogue).

[Fruity_Rudy]

allright, i try that out when i'm home..I'd like to see what happens if i play with the value, never did that before

[doveman]

Using beta 94700 (or 95099), sensitivity now works with the Hotas X Throttle (Z Axis) directly, but it's still not possible to adjust it so that mid-point maintains altitude and it only seems to change the time it takes for the collective to change in response to throttle adjustments, so I'll continue using PPJoy for now.