Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update and rename Nintendo Co., Ltd. Pro Controller (old).cfg to Pro …
…Controller (default-off).cfg The individual responsible for uploading the file inadvertently swapped the non-HID autoconfig file with the HID autoconfig file. You can access the non-HID file [here](libretro@3abfcb2) and the HID file [here](libretro@3abfcb2). To address this issue, I: * Removed "(old)" from the non-HID file and added "(default-off)" to the HID file to align with our updated naming convention. * Swapped their autoconfig data. However, he was correct about one detail. He included `input_device = "Pro Controller"` (Bluetooth identifier name), which I mistakenly later changed to `input_device = "Nintendo Co., Ltd. Pro Controller"` (USB identifier name) ([source](libretro@98b1591)). The non-HID driver does not support USB connection for this controller, only Bluetooth. I made this change because I believed the udev controller driver identified the controller using `input_vendor_id` / `input_product_id`, as generated by "Save Controller Profile" in RetroArch, but later discovered that udev relies on `input_device`, which led me to file a bug report. Consequently, I edited this file: * I removed the commented variables `input_product_id` and `input_vendor_id` which fail to disable this controller. * Commented `input_device = Pro Controller` to disable this controller to leave file name space for `Pro Controller.cfg` (HID) since Linux 6.8.0 (Ubuntu 24.04) also identifies this controller as "Pro Controller". I filed this issue just a few days ago: * [GitHub Issue](libretro/RetroArch#16904) Additionally, I removed the comments as a standard procedure. "non-HID" is included in `input_device_display_name`.
- Loading branch information