Joystic Lag - false reading

Joystic Lag - false reading

devo_au

Member #15,282

August 2013

Hey there,

Sometimes al_get_joystick_state gives me
false axis readings. Eg sometimes when I release the analog
the player will continue to travel in the last direction it was heading.
I checked the rest of the loop,

#SelectExpand
  al_get_joystick_state(joy, &joyState);
  axvalX = joyState.stick[0].axis[0];
  axvalY = joyState.stick[0].axis[1];
  
  //TEST X AXIS
  if(axvalX < 0)//left
  {
    keys[LEFT] = true;
    keys[RIGHT] = false;
  }
  else if(axvalX > 0)//right
  {
    keys[LEFT] = false;
    keys[RIGHT] = true;
  }
  else //center
  {
    keys[LEFT] = false;    
    keys[RIGHT] = false;
  }

the issue seems to be coming straight
after al_get_joystick_state.

I'm running v5.0.7 mono
VC 2010 express on win7 32
& Logitech F310 switched to directinput
Cheers

it wasn't me, it was other kids

Edgar Reynaldo

Major Reynaldo

May 2007

Your stick might not be in a totally neutral position. Try using a small epsilon to test for centeredness :

double epsilon = 0.05;

if (axis < -epsilon) {left = true;}
else if (axis > epsilon) {right = true;}
else {center = true;}

Eagle and Allegro 5 binaries | Older Allegro 4 and 5 binaries | Allegro 5 compile guide
King Piccolo will make it so Then I could just flip it with some sweet, sweet matrix math. In either case, I’ll ride this wagon until the wheels fall off. Thanks to those that keep it running

devo_au

Member #15,282

August 2013

Thanks for reply. Normally the stick is 0.00000 center. When bugging the stick is reading 0.435652 when it has physically returned to the center. It works ok most the time, so I haven't worked out what is triggering it, only that I can debug the false read back to al_get_joystick_state(joy, &joyState).

it wasn't me, it was other kids

l j

Member #10,584

January 2009

No joystick is perfect and the issue is likely hardware related but 0.435652 seems a tad high though.

devo_au

Member #15,282

August 2013

Could be right about hardware, it might be a dodgy controller. Can't find another explanation. It works well 99.9% of the time.

it wasn't me, it was other kids