Controller button input version 5.22

no-reply@allegro.cc (TripleG) — Mon, 06 Mar 2017 01:07:28 +0000

The input response for

if (events.type == ALLEGRO_EVENT_JOYSTICK_BUTTON_DOWN)
{
printf("Button was pressed\n");
}
else if (events.type == ALLEGRO_EVENT_JOYSTICK_BUTTON_UP)
{
printf("Button was released\n");
}

is really bad. Sometimes it even skips that the button was released. It improved when I used al_wait_for_event(event_queue, &events);

but there are still skips when the buttons are pressed when I press the buttons too fast. Even when I press them at slow intervals it sometimes skips Button was released. I am using ALLEGRO_5.22 and have it installed using Microsoft visual studio 2015. Keyboard responses are immediate and analog response are immediate with controllers. It is just the buttons that are the issue

no-reply@allegro.cc (SilverTES) — Fri, 10 Mar 2017 18:16:20 +0000

I have the same problem , but I don't found a solution.
Meantime, I use SFML window module with Allegro, sf::Joystick the response is better.

no-reply@allegro.cc (Eric Johnson) — Fri, 10 Mar 2017 20:33:51 +0000

Like I mentioned in your other topic, I haven't noticed any issues with the joystick API. Here is the example I threw together again:

#SelectExpand
  1#include 
  2
  3#include 
  4
  5using std::cout;
  6
  7int main(void) {
  8
if (!al_init()) {

  cout << "Error: failed to initialize Allegro\n";
  
  return -1;
}

if (!al_install_joystick()) {

  cout << "Error: failed to install joystick\n";
  
  return -1;
}

ALLEGRO_TIMER *timer;
ALLEGRO_EVENT_QUEUE *event_queue;

if (!(timer = al_create_timer(1.0 / 60.0))) {

  cout << "Error: failed to create timer\n";
  
  return -1;
}

if (!(event_queue = al_create_event_queue())) {

  cout << "Error: failed to create event_queue\n";
  
  return -1;
}

al_register_event_source(event_queue, al_get_joystick_event_source());  
al_register_event_source(event_queue, al_get_timer_event_source(timer));

al_start_timer(timer);

cout << "Notice: press joystick buttons now (program will shutdown in 20 seconds)\n\n";

while (true) {

  ALLEGRO_EVENT event;

  al_wait_for_event(event_queue, &event);
  
  if (event.type == ALLEGRO_EVENT_TIMER) {
    
    static unsigned int ticks = 0;
  
    ++ticks;
  
    if (ticks > 60 * 20) {
  
      break;
    }
  }
  
  if (event.type == ALLEGRO_EVENT_JOYSTICK_BUTTON_DOWN) {
  
    cout << "Button pressed\n";
  }
  else if (event.type == ALLEGRO_EVENT_JOYSTICK_BUTTON_UP) {
  
    cout << "Button released\n";
  }
}

al_destroy_timer(timer);
al_destroy_event_queue(event_queue);

cout << "\nGood bye!\n";

return 0;
 81}

The above works for me without issue. I encourage others to test it out and see how it works for them.

no-reply@allegro.cc (Neil Roy) — Sat, 18 Mar 2017 08:08:43 +0000

I had similar issues with an older version of Allegro 5, I forget which exactly, 5.1 maybe? My main problem I had was with the digital joystick input when I used my Microsoft controller, like the XBox style controllers or whatever. Analog seemed okay, but I had issues with the digital joystick inputs. I worked on it for a very long time before finally removing support for Joysticks from my game (Deluxe Pacman 2).

My problems were, if you were going one direction, and changed directions, it would often wouldn't pick it up at all unless you centered the stick first (or let go of it) then push the new direction. For digital this was a pain as that is the main input my game uses. Analog worked okay as I remember. I may have to check my notes again. I worked long and hard on this until I eventually just commented out all the joystick code.

Sounds like the same issues are still there.