I assume that the problem should be analyzed when the rules are active, right?
If so, the issue then becomes related to DualSense inputs incorrectly mapped in Metal Gear Solid V: The Phantom Pain (287700).
I am leaving open the issue for the time being and simultaneously mentioning it in Metal Gear Solid V: The Phantom Pain (287700); you will find the related logs there.
Please let me know what you think.
SOLVED:
SDL_JOYSTICK_DEVICE=/dev/input/js0 %command%
proton 9.0-2x1 2024-09SDL_JOYSTICK_DEVICE=/dev/input/js0x1 2024-09SDL_JOYSTICK_HIDAPI_PS5x1 2024-09
I need help dealing with DualSense (connected via bluetooth) behaving differently with different games.
All tests were done on openSUSE Leap 15.6 with this setup:
pfxWhen NOT using
88-steam-input.rules:287700) ✅(game shows XBox buttons layout, but that's OK for me)
1659040) ❌With
88-steam-input.rules(+sudo udevadm control --reload && sudo udevadm trigger):287700) ❌R2(orRT, Right Trigger as Xbox names it) is recognized as always constantly pressed(game shows me XBox buttons layout, but that's OK for me)
1659040) ✅(with
88-steam-input.rules)Thanks