The way I ended up getting it to work was to use four virtual DirectInput devices instead of Xinput, and turn off autoconfiguration. If RetroArch simply had a way of only using Xinput devices, everything would work perfectly for me and everyone else with DS4 troubles. I tested this with both the latest stable release of RetroArch and one of the very recent nightlies (I think from Sept 29). But even if I used a different DS4 driver, I would still have this problem because my system also has at minimum four DirectInput devices that I use for compatibility reasons with other older games and emulators. The DS4 gamepad always has both an Xinput and DirectInput device that corresponds to it (I am using DS4Windows) which screws everything up. This means that there’s no way for me to get it to consistently pick the Xinput gamepads I have connected for slots 1-4. Even when I set “Input driver” to “null” and “Joypad driver” to “xinput”, it still lists DirectInput gamepads along with Xinput gamepads in the Input settings and will automatically choose them regardless of whether autoconfiguration is turned on. The problem in RetroArch is that there’s no way to set it to only use Xinput devices. Mixed in with my various devices are several DirectInput gamepads that I do not want RetroArch to use, including one that corresponds to my DS4 gamepad and occasionally some that correspond to WiiMotes. I was having trouble getting two or more Xinput devices working, one of which was a DualShock 4, and the other three were wireless Xbox 360 gamepads. I had the same problem with RetroArch and I was able to get it working. I would be happy to upload a log if someone could explain how to generate one! Is there a way to manually bind a controller to a port permanently?Īny suggestions would be great! Sorry if this is too wordy, just trying to be as descriptive as possible. I have a suspicion that RetroArch is picking up both the DINPUT & the XINPUT from the wrapper and registering each as a device? I thought maybe my BT keyboard was being registered as a gamepad, but it didn’t make a difference when I took it out of the loop. I have tried a variety of configurations and settings. I have been through these forums and haven’t found anyone with a similar issue. If i manually change user 1 index to XINPUT USER 1 than both controllers work as they should.Īlternatively, if I don’t configure a second controller, the 1 controller will work as expected without issue. If i go into input settings, my device 1 has been identified as WIRELESS CONTROLLER and device 2 is registered as it should (xinput user 2). When I start BSNES Mercury or Nestopia core and load content, controller 1 doesn’t work, I power on controller 2 and it is identified and works as controller 1. Max Users - 4Menu Toggle… - NoneRemap Binds Enable - ONAutoconfig Enable - OFFDisplay Autoconfig Descriptor Labels - OFFDisplay Core input Descriptor Labels - ONHide Unbound Core Input Descriptors - ONBind Mode - RetroPadUser 1 Device Type - RetroPadUser 1 Analog to Digital Type - NoneUser 1 Device Index - Xinput Controller (User 1)User 2 Device Type - RetroPadUser 2 Device Index - Xinput Controller (User 2) Input driver - nullJoypad driver - xinput I am having an issue connecting a second BT DS4 controller, hope you can help!?Ģ Dualshock 4 controllers ( connected via BT)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |