So I've got this 1st world problem where I want to use my DS4 as an Xbox 360 gamepad and leave it at that. Simply and to the point I used DS4Windows.
I don't really care for proper DS4 integration or anything for the few games that decide and do that. I don't need the touch pad and share or whatever.
Still, apps like RetroArch seem to rely on the order of activation/acknowledgement of the device by Windows to map it. There are also some games that only accept the "first" xinput controller they see for input (regardless of what you set as the "preferred device" in the Windows settings for "older programs"). So I first connected my DS4, set it up as a 360 pad with DS4 Windows, then connected the Fighting Commander, then finally my flight stick, and that was their order.
Then I for example mapped stuff in this RetroArch system core so that the DS4 turned to 360 via DS4Windows is controller 1 and my Fighting Commander controller 2. And for another core, the opposite because I prefer the Fighting Commander to be the primary instead (ie for Sega Saturn and arcade stuff).
It all worked great, Trials of Mana and Phantasy Star Online 2 accepted the DS4 as the first 360 pad input, RetroArch cores/games worked as intended, etc.
The next day it seems that the controller order changed and then messed up everything, perhaps mostly because DS4Windows starts after logging in Windows so that pad goes through the process of first being a dinput controller and then becoming a 360 xinput gamepad after the fact, so the "last" device, while the others just work as soon as Windows starts via their drivers. Anyway, the result was those two games expected the Fighting Commander for input and my DS4 as 360 pad didn't do anything in them, RetroArch cores had different controllers as gamepad 1 and 2 than I had set, etc.
So, does anyone have a way for these usb devices to have the same order no matter what happens on boot so that my DS4 as 360 is always first? I would think that as long as they're not actually uninstalled Windows should keep them with the same order even when they're unplugged as long as they remain in the device manager (as hidden unplugged devices) and you do reconnect them before playing but I guess that's just not the case.
Or alternatively a few simple steps to use Steam's input thing (I never wrapped my head around this seemingly clunky thing, hence the use of the simple DS4Windows) instead for my DS4 to act as an Xbox 360 pad (and as the only pad games like those above recognize and work off of) so I can just use it as a vanilla dinput controller in RetroArch and hopefully not have the order change every time I boot Windows as all controllers will be connected from the start? Unless that also has a chance to change their order based on how the different USB slots get power and device detection or something which would suck.
I don't really care for proper DS4 integration or anything for the few games that decide and do that. I don't need the touch pad and share or whatever.
Still, apps like RetroArch seem to rely on the order of activation/acknowledgement of the device by Windows to map it. There are also some games that only accept the "first" xinput controller they see for input (regardless of what you set as the "preferred device" in the Windows settings for "older programs"). So I first connected my DS4, set it up as a 360 pad with DS4 Windows, then connected the Fighting Commander, then finally my flight stick, and that was their order.
Then I for example mapped stuff in this RetroArch system core so that the DS4 turned to 360 via DS4Windows is controller 1 and my Fighting Commander controller 2. And for another core, the opposite because I prefer the Fighting Commander to be the primary instead (ie for Sega Saturn and arcade stuff).
It all worked great, Trials of Mana and Phantasy Star Online 2 accepted the DS4 as the first 360 pad input, RetroArch cores/games worked as intended, etc.
The next day it seems that the controller order changed and then messed up everything, perhaps mostly because DS4Windows starts after logging in Windows so that pad goes through the process of first being a dinput controller and then becoming a 360 xinput gamepad after the fact, so the "last" device, while the others just work as soon as Windows starts via their drivers. Anyway, the result was those two games expected the Fighting Commander for input and my DS4 as 360 pad didn't do anything in them, RetroArch cores had different controllers as gamepad 1 and 2 than I had set, etc.
So, does anyone have a way for these usb devices to have the same order no matter what happens on boot so that my DS4 as 360 is always first? I would think that as long as they're not actually uninstalled Windows should keep them with the same order even when they're unplugged as long as they remain in the device manager (as hidden unplugged devices) and you do reconnect them before playing but I guess that's just not the case.
Or alternatively a few simple steps to use Steam's input thing (I never wrapped my head around this seemingly clunky thing, hence the use of the simple DS4Windows) instead for my DS4 to act as an Xbox 360 pad (and as the only pad games like those above recognize and work off of) so I can just use it as a vanilla dinput controller in RetroArch and hopefully not have the order change every time I boot Windows as all controllers will be connected from the start? Unless that also has a chance to change their order based on how the different USB slots get power and device detection or something which would suck.
i missed it
