[Bug] Dualsense doesn't appear correctly using bluetooth connection

[RealVishy]

Current Behaviour

When connecting the DualSense controller to Minecraft using Bluetooth , the controller is detected as a "PS5 Controller" instead of a "DualSense Controller." Additionally, a generic controller icon is displayed instead of the specific DualSense controller icon. Furthermore, the button icons shown in the game are the default Xbox button icons, not the corresponding icons for the DualSense controller.

Expected Behaviour

The controller should be recognized and displayed as a "DualSense Controller" rather than a "PS5 Controller." The specific DualSense controller icon should be shown instead of a generic controller icon. The button icons in the game should accurately represent the buttons on the DualSense controller, not the default Xbox button icons.

Screenshots

Reproduction Steps

1. Install game-devices-udev
2. restart computer
3. connect dualsense through bluetooth
4. navigate to controls

Logs

No response

Mod Version

1.4.0+1.20

Controller

Playstation Dualsense Controller. https://www.playstation.com/en-au/accessories/dualsense-wireless-controller/

Bluetooth

• [X] Yes

Operating System

Arch Linux with KDE

ARM

• [ ] Yes

Additional Information

The controller is correctly picked up as a dualsense with the correct icon maps when using a cable.

Just to make sure...

• [X] I have made sure I am using the latest version of Controlify for the latest version of Minecraft.
• [X] I have made sure there are no other issues describing the same problem on the issue tracker.

[Dolfost]

I have the same problem. MacOS ventura v13.4.1, ARM. Sony Dualsense 5 gamepad.

In addition, when it works via cable: If I press R2 or L2 and release it, game thinks that this buttons are held down for some reason and player keeps placing/breaking blocks. This might be because the R2 and L2 are axes on Dualsense 5, not buttons.

[Dolfost]

Almost forgot, button textures are wrong. The Dualsense 5 uses circle, triangle, square, cross for B, Y, X, A buttons.

[isXander]

Send the latest.log file after repeating this issue.

[RealVishy]

Here is the latest.log file for 1.40+1.20 latest.log I also tried it on 1.41+1.20 with the same issue. latest.log

I assume this is what's causing the issue. If controller's can't be identified over bluetooth, it might be worth creating an option to choose controller icons in the settings or to identify the controller manually when using bluetooth. [11:12:40] [Render thread/WARN]: No controller found via USB hardware scan! This prevents identifying controller type.