Gamepad buttons are always bound to multiple functions

[second2050]

Issue

Gamepad buttons always execute to functions: one function I defined and one function that I haven't defined but that is always the same for a given button.
This happens with both a DualShock 4 v2 and a Steam Controller (used via SC Controller, emulating an Xbox 360 Controller).

This does not happen if a button is unbound.

Example

• A / Cross button: Defined as +jump but also always executes +attack2
• B / Circle button: Defined as +reload but also always executes +attack
• LB / L1: Defined as invprev but also always executes +duck
• RS / R3: Defined as +use but also always executes pause

Things I have tried

• using unbindall to remove all bindings and then rebind all the buttons I need
• executing xash3d with the -sdl_joy_old_api flag, which makes it not recognize controllers anymore

Platform information

OS: Arch Linux (Kernel 6.3.0-x64v3-xanmod1-1)
Xash3D version: Xash3D FWGS 49/0.20 (linux-i386 build 2947) compiled from master (4817623)

Logs and attachments

engine.log
xgamepad.cfg.txt Gamepad Bindings

[a1batross]

Better set joystick 0 in this config.

It seems that joystick support in original client.dll is conflicting with our in-engine support. You have to disable one of them.

I will figure out how to support both later.

[second2050]

According to the console joystick 0 is already set and executing joystick 0 doesn't seem to change anything.
Setting joystick 1 makes the left stick also control the camera though.

[CkauNui]

[RU] Такая же проблема, всё ещё нет исправленного client.dll?

[OlegAckbar]

I can confirm this issue. For me, A and B buttons are also acting as primary and secondary attacks, even though I've not set them so.

xash3d_gamepad.webm

[OlegAckbar]

hlsdk-portable libraries are fixing the issue

[a1batross]

Yeah, hlsdk-portable client wouldn't have this issue because it's aware of our custom input interface.