DraftLight 10 Posted June 14, 2015 Well okay, first of all: I know there are a lot of posts about that topic, BUT 1. there are that many Posts without a posted solution, 2. Most of it is for Arma II not III. OK, now to problem which is really annoying. I got Saitek X52 (non Pro) and for sure i want to use that one for flying in ARMA III Also im using the Pedals of my Logitech G27. It looks like non of the Axis being used completly, just about 25-50%. E.g. if im using the Throttle of the X52 to raise with a Chopper I can only use 25% of the Controller, the rest seems to be like a deadzone (already checked deadzones in controlpanel and Arma) Same for all other Axis like turning left and right on the Z axis and similar Second Problem is when im trying to turn the chopper in Hovermode with the Joystick´s z axis, its going really slow ... (same with the G27 pedals) If im turning with the Keybindings on the Keyboard its working like it should do. Any suggestions? Share this post Link to post Share on other sites
DraftLight 10 Posted June 16, 2015 (edited) Well okay, after having a headache about this, i finally found out ur not supposed to bind the collective lower(analouge) to any axis, but bind both axis to collective raise(analouge) so it uses the full range of ur joystick. But still im having a problem about the slow turning speed which seems to be occuring with all kind of joysticks, even my logitech g27 pedals, the Saitek X52 Joystick z axis and also my xbox360 controller. Its only working correctly with the correct speed with my defauklt key bindings "del" and "end" UPDATE: ok, although nobody here even replied i finally found out there seems to be a problem if im using the Logitech g27 pedals with my Saitek X52 controller. Therefore i had to unbind that one, just simply as that ..... Just wanted to share if someone is dumb enough like me, trying to find out for a week what the problem could be .... SOLVED Edited June 16, 2015 by DraftLight Share this post Link to post Share on other sites
doveman 7 Posted June 17, 2015 Well okay, after having a headache about this, i finally found out ur not supposed to bind the collective lower(analouge) to any axis, but bind both axis to collective raise(analouge) so it uses the full range of ur joystick. Except if you're using the helo AFM, in which case you have bind axis + to raise and axis - to lower. Yes, that does make it rather hard to switch between SFM and AFM! The other problem you had is due to a bug where if you have more than one axis bound to a command, each device only has 50% authority. Hopefully both issues will get fixed sometime. Share this post Link to post Share on other sites
xon2 102 Posted January 20, 2016 I can confirm that issue. My T.16000m was only half as strong/fast as the keyboard. I recently started running a target script to have specific deadzone across the board. Hence arma 3 recognized a new virtual joystick. But i did not delete the original T.16000m keybidings, just added the new ones for the scripted virtual joystick. Once i had unboud all axis and rebound only those for the virtual joystick, everything was working perfectly fine again.And incidentely, if you make a new profile, it automatically binds only the recognized joystick with only one set of keybindings. Share this post Link to post Share on other sites
