Axes mapping

[I.JG3_CDRSEABEE]

I was mapping my axes in Blitz and the it was very difficult because the program would sense an axes I wasn't touching. I would have to clear it numerous times to get the axes I wanted to appear in the box.

 

It was like it was over sensitive. This is the only program I have that does this. RoF and BoX do not do this.

 

Has anyone else experienced this? Is there a solution?

 

It seems to work fine after getting the mapping done. Just a pain.

[Sokol1]

The issue is because one or more axis of your controllers (joy/throttle/pedal...) is "spiking" (generating electric noise). Saitek's is "champion" in this issue. An option is disassembly (PITA) pot and clear their resistive trail help for a while. Spray pot case externally with contact cleaner is just placebo.

 

Or if this joystick, etc has software increase their deadzone - not the best solution because reduce controller authority. 

 

Try identify the culprit axis and move their lever/knob for a position that can interfere less.

Try too leave the "sensitivity" slider in Controls GUI (that just refer to "S" response curve) in 1, 0 mean 100(%).

Can try too increase axes deadzone to max, temporarily until mange to assign all axes.

Edited July 16, 2019 by Sokol1

[I.JG3_CDRSEABEE]

On 7/16/2019 at 12:35 PM, Sokol1 said:

The issue is because one or more axis of your controllers (joy/throttle/pedal...) is "spiking" (generating electric noise). Saitek's is "champion" in this issue. An option is disassembly (PITA) pot and clear their resistive trail help for a while. Spray pot case externally with contact cleaner is just placebo.

 

Or if this joystick, etc has software increase their deadzone - not the best solution because reduce controller authority. 

 

Try identify the culprit axis and move their lever/knob for a position that can interfere less.

Try too leave the "sensitivity" slider in Controls GUI (that just refer to "S" response curve) in 1, 0 mean 100(%).

Can try too increase axes deadzone to max, temporarily until mange to assign all axes.

I will try to isolate it. Strange it only happens in CloD though.

[Sokol1]

Thing that in CloD axis detection is set high sensible, other games have a kind of filter, but otherwise sometimes Bo'X', DCS don't pick the axis movement of certain controllers, in DCS is possible select the axis by name in a drop down menu.