Joystick 2 Object - XBox360 reads as Joypad 2?

[FinalSpecimen]

The XBox360 controller I'm plugging in only is responding when I map it as "Joypad 2." When I use a Logitech F310, it only reads as "Joypad 1." I'm not defining any more than one player in my game, and the XBOX Joypad's light reads Player 1. Shouldn't all joypads in this scenario respond to "Joypad 1" by default?

Additionally, I find that when I unplug a controller and plug it back in, it *sometimes* lags the app. Other times, it's fine. Any way to account for all these variables?

[J3sseM]

I'm trying to figure out the same. You can swap the controller through Windows "Gamepad" software.
However I can't expect players to do this. Would be awesome if we could set all controllers to respond to "joypad 1".

Any ideas? :>

[PBarwick]

You could map all joypads to one global value and use that instead.

For example:

- Always
= Set global value to 0

- If pad1 up is pressed
= set global value to 1

- If pad2 up is pressed
= set global value to 1

...etc, finally:

- if global value equal to 1
= move up 1 pixel

[J3sseM]

It would make no sense to have duplicate code like that.

Anyways, we could however use a value instead of a player, and have only a few lines to determine which player is active. That wouldn't take but a few lines and should work in theory, thanks for the idea!

[PBarwick]

Yeah there's more sophisticated ways to do it, I was just trying to write it down in the most simple way possible to get the idea across.

I'd encourage capturing the full range of values from the thumb sticks for example.

Though I'm not quite sure what you mean instead Jesse?

[J3sseM]

I mean we could have only a few lines of code, say
"any button is pressed on pad2" = set player to "2".
"any button is pressed on pad3" = set player to "3".
etc.

Then "specific button is pressed on pad "player value here"".

This is basically what you suggested but reversed and would only take a few extra lines instead of possibly hundreds of lines.

EDIT: Actually there is "Get last active joystic" command, so we can do this with single line.

[PBarwick]

Nice, that's a very neat method!

[FinalSpecimen]

The "get last active joystick" command is exactly what I was looking for. Saves so much time coding LOL!

Is there a need at that point to even define players (in my case it's just a single player game) or will the event just be self-referential?

Additionally, for anyone looking for a lot of GREAT info on the joypad 2 object, this video from Snail On is a great in-depth exploration of the extension: https://www.youtube.com/watch?v=lZZt0nMgzFQ