MapInputEventToClientEvent + button:0

I am registering all of those using SimConnect_MapInputEventToClientEvent_EX1

joystick:4:Button:0
joystick:4:Button:1
joystick:4:Button:2
joystick:4:Button:3
joystick:4:Button:4
joystick:4:Button:5
joystick:4:Button:6
joystick:4:Button:7
joystick:4:Button:8
joystick:4:Button:9

On by Xbox Controller specifically, when I press the X button (joystick:4:Button:0), all the other events are firing as well. It seems related to it having index 0.

Any way to prevent that?

Hello @runshotgun

I am not able to replicate this issue so far, Button:0 event is only received when pressing ‘A’ as expected

Here’s the code snippet I used :
JoystickInput.cpp (3.1 KB)

Do you have the same problem when all other controllers/joysticks are unplugged?

Regards,
Sylvain

1 Like

This is coming back from the dead, but the issue still exists in 2024.
An example project (P42 Demo Project) exhibiting the issue has been sent to @PrivateContent

Hello @runshotgun

I was able to replicate the issue.
This seem to occur when mapping buttons beyond a certain range.
For a XBox controller, all events starting from button 32 and beyond will trigger a generic SimConnect exception on MapInputEventToClientEvent, but will somehow be mapped on the same event as button 0.

This will be investigated further.

Regards,
Sylvain

3 Likes