You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to ulao and also my personal testing on my 4-Play on the latest firmware, RetroArch only supports the Bliss-Box detection API on Windows and not Linux.
Notable quote from ulao: "Just for the info, what they said was that in lib USB they couldn't do control transfers like they could with win USB"
I have also tested alternate autoconfig profiles provided by hunterk on Discord that were updated to support the 3.x firmwares, and I have also tried commenting out the device names in all the profiles. What ends up happening is my controller is recognized as an Atari controller, but I can still manually map the buttons. I believe this is because the Atari profile alphanumerically comes first, although I may be wrong there.
I am using Arch Linux with the udev controller driver.
The text was updated successfully, but these errors were encountered:
According to ulao and also my personal testing on my 4-Play on the latest firmware, RetroArch only supports the Bliss-Box detection API on Windows and not Linux.
Notable quote from ulao: "Just for the info, what they said was that in lib USB they couldn't do control transfers like they could with win USB"
I have also tested alternate autoconfig profiles provided by hunterk on Discord that were updated to support the 3.x firmwares, and I have also tried commenting out the device names in all the profiles. What ends up happening is my controller is recognized as an Atari controller, but I can still manually map the buttons. I believe this is because the Atari profile alphanumerically comes first, although I may be wrong there.
I am using Arch Linux with the udev controller driver.
The text was updated successfully, but these errors were encountered: