![]() ![]() Alternatively, you may be able to delete the entire "OEControllerLogitechDualAction" dictionary from the ist inside the OpenEmu application bundle which should allow you to use all devices at once, but then you will have to remap controls. It will take some time to figure out a way to cleanly differentiate these devices and still be able to automap controls for them, so for now the workaround is to either use only F310/F710 devices together or Rumblepad 2/Dual Action devices together. This makes the devices differ enough to throw off our input automap system which ends up not working with both a F310/F710 and Rumblepad 2/Dual Action plugged in.Īs you can see with the profile screenshots below, the cookie elements for the buttons do not match up: Buttons and controls are fully programmable and can even mimic keyboard and mouse commands. ![]() ![]() With the newer F310/F710 models, they removed a HID collection grouping from the profile so that all of the cookie elements for the buttons are off by one. Change the standard commands or adapt F310 for play with an unsupported title, using Logitech profiler software. So, despite all of these devices reporting as "Logitech Dual Action" when set to DirectInput mode and having matching vendor/product ID's, they do not all have the exact HID profiles. Thank you for the original detailed report! It took time to acquire these devices (Logitech F310 and Logitech Dual Action) to test with, but thanks to having set up donations we can finally check out issues with gamepads if we need to. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |