Gladiator K axes integer overflow?
Posted: Wed Jun 17, 2020 22:17
Hey everyone, I just got my Gladiator K in the mail today and just set it up. It's my first joystick, so I'm a bit of a noob.
What I noticed straight away is that the X and Y axes are "snapping over" when moving the stick all the way to one side. In the Device Configurator, when looking at the Test tab with the axes, I can move both X and Y to 0 or 66535, but if I press it a bit more, it goes from 66535 to 0, or vice versa. Looks like the 16-bit integer is simply overflowing.
I looked through the manual because I would like to reduce the sensitivity of the stick anyway, and I found on page 19 that I can reduce the sensitivity factor using the D.Rate option. Unfortunately, it doesn't seem to change anything. I clicked the "Set" button in the Action tab so shouldn't it be saved on the device?
Thanks for your help, I'm enjoying it very much so far. Hope I can sort this out
What I noticed straight away is that the X and Y axes are "snapping over" when moving the stick all the way to one side. In the Device Configurator, when looking at the Test tab with the axes, I can move both X and Y to 0 or 66535, but if I press it a bit more, it goes from 66535 to 0, or vice versa. Looks like the 16-bit integer is simply overflowing.
I looked through the manual because I would like to reduce the sensitivity of the stick anyway, and I found on page 19 that I can reduce the sensitivity factor using the D.Rate option. Unfortunately, it doesn't seem to change anything. I clicked the "Set" button in the Action tab so shouldn't it be saved on the device?
Thanks for your help, I'm enjoying it very much so far. Hope I can sort this out