Joystick Programming

[mateandmetal]

Hi

Started joystick programming today.... I have some doubts.. 


1) I have discovered that some buttons of my wired X360 controller are not detected as pressed (the buttons are LT and RT)... sf::Joystick::getButtonCount is returning 10..... Using my generic usb gamepad getButtonCount returns 12 buttons (and they all count as pressed when I press them) ... is this a bug?


2) I´m getting some errors trying to get the joystick moved with the events system. This is my code:

        sf::Event event;
        while (window.pollEvent (event)) {

             // Close window : exit
            if (event.type == sf::Event::Closed)
                window.close();

            // HERE I want to know the joystick number, the axis, and the new position
            if (event.type == sf::Event::JoystickMoved) {

               // error: expected primary expression before ´.´ token
               unsigned int njoy = sf::Event::JoystickMoveEvent.joystickId;

               // trying this way.. error: invalid use of ´struct sf::Event::JoystickMoveEvent´
               unsigned int njoy = event.JoystickMoveEvent.joystickId;
 

what is the correct way of getting the joy number, the axis moved, and the new position (using the event system) ?

win7 x64, codeblocks, sfml 2 updated
thanks

[mateandmetal]

i figured it out:

1) LT and RT are not detected as buttons... They are detected as axis  ... Why?

2) correct code:

         if (event.type == sf::Event::JoystickMoved) {

                unsigned int njoy = event.joystickMove.joystickId; // Joy Number
                sf::Joystick::Axis eje = event.joystickMove.axis;  // Axis moved

                float pos = event.joystickMove.position; // New position
 

But now I have a 3rd question.... Is SFML axis handling code very bug? or Joystick programming is just a pain in the ...  ?

Generic USB gamepad uses diferent axes with analog mode on and off
X360 controller uses the same axes for left stick, right stick, LT and RT button, and digital pad  (the controller works fine with most commercial games)

[thePyro_13]

i figured it out:

1) LT and RT are not detected as buttons... They are detected as axis  ... Why?

All the newer controllers(Xbox 360, so on...) seem to expose them as axis these days. Probably so that they can be used as accelerators in racing(and flight sim) games.

But now I have a 3rd question.... Is SFML axis handling code very bug? or Joystick programming is just a pain in the ...  ?

Have you tried using sf::Joystick rather than SFML events? I find getting the input from the input objects to make far more sense then using the event system.

Generic USB gamepad uses diferent axes with analog mode on and off
X360 controller uses the same axes for left stick, right stick, LT and RT button, and digital pad  (the controller works fine with most commercial games)

The 360 controller should have 4 sets of  axis. One for each normal joystick, one for the POV(d-pad). And one shared between the two triggers.

In SFML:
POVx, POVy are probably the d-pad.
X, Y are probably the left most controller
Z, R are either the right joystick or the triggers.
U, V are whichever one Z, R isn't.

[mateandmetal]

Have you tried using sf::Joystick rather than SFML events?

Thanks thePyro_13... Im using sf::Joystick interface now... I wrote a new app that shows the axis positions on the window... I see everything much clearer now:

In SFML:
POVx, POVy are probably the d-pad.
X, Y are probably the left most controller
Z, R are either the right joystick or the triggers.
U, V are whichever one Z, R isn't.

Generic gamepad with analog ON and X360: yes.... PovX, PovY have the same behavior
X, Y ... left stick (analog ON)
the right stick is not the same .. Generic gamepad is Z, R ... 360 is U, R 

LT and RT on the 360 controller is the Z axis going from -99 to 99 aprox.

Perhaps with the PS3 controller is all different