#Xbox 360 mode creates a secondary device entry, resulting in no response in games

1 messages · Page 1 of 1 (latest)

glad totem
#

If DSX has an active profile that makes use of Xbox 360 emulation mode running, then the controller is shut down, and then its turned back on (seconds, minutes or hours after, as long as DSX is still running in the background) DSX will create a secondary gamepad entry (as far as I can tell, will explain further below), which results in the PS button not opening the Xbox Game Bar overlay, and certain games not detecting the controller at all.
To check what was going on, I used the DuckStation PlayStation 1 emulator's controller settings since it updates it's controller entries in real time (it makes use of SDL). Once the gamepad is turned on, it will create the following entry:

SDL-0: DualSense Wireless Controller

Which is correct, because HidHide didn't kick in yet. After it does, that entry dissapears and changes to:

SDL-0: Xbox 360 controller

That's how it worked as always, but then that entry dissapears and changes the SDL-0 entry to SDL-1, suggesting a different controller (for a second player) was plugged in. Windows also plays the device connection sound effect when that happens. This results in the PS button not opening the Xbox Game Bar overlay, and some games not detecting the controller at all.

A momentary fix for this issue is switching emulation modes from Xbox to DS4 or DualSense, and then setting it back to Xbox. The PS1 emulator mentioned above will report SDL-0: Xbox again, Game Bar will open as usual and games will recognize the controller as always.

DSX v3, Windows 11 23H2

cedar hedge
#

Will investigate this

glad totem
#

Glad to report as of 3.0.2 this no longer happens

cedar hedge
glad totem
#

As of 3.0.4, this behavior is back but in a different way. After a couple of seconds or minutes of connecting the controller with DSX open with Xbox 360 mode enabled, a virtual device disconnection will happen. It seems DSX doesn't create a second controller entry anymore, as in having two virtual controllers, but rather switches to a secondary controller entry removing the first virtual device created, as far as I can tell, will give more details below.

Games/software that can switch controllers dynamically on the fly don't seem to be affected (DuckStation, Steam, etc.), but some games (for example Like a Dragon: Infinite Wealth) don't like this at all, they don't detect the controller anymore even after a restart. A fix for this issue, again, is to switch profiles/emulation modes and then choose Xbox 360 mode again.

As I mentioned before, software that can dynamically switch between controllers on the fly are not affected, for example DuckStation will report SDL-0: Xbox 360 Controller as usual, but oddly enough, checking the Steam client's controller settings, usually the virtual controller name is "Mando Xbox 360" (my Steam installation is set to Spanish), but after the virtual device disconnection happens (can be heard through a Windows device connection notification sound effect), it changes to "Control Xbox 360". Switching to a profile that uses native mode/PlayStation controller emulation modes, and then going back to one with Xbox 360 mode, it will go back to "Mando Xbox 360" as usual.

Whenever it is set to "Control Xbox 360" on Steam, some games like the one mentioned before will not detect the controller at all, and also the Guide button will not open the Xbox Game Bar overlay. Just to clarify, Steam Input is completely disabled, i'm using its controller config panel just to check the behavior of the virtual gamepad.

#

This whole process repeats every time the controller is connected once, after doing the profile switch method everything will work as usual until it is turned off or DSX is restarted.

#

As far as I can tell, other emulation modes don't seem to be affected

#

Just found this right now, after shutting down my physical controller, it seems DSX didn't shut down the actual virtual gamepad, Steam kept reporting an Xbox 360 controller was plugged in (reported as "Mando Xbox 360"). DSX didn't show any connected gamepads. Hooking up my controller again and then shutting it off seems to have fixed it

cedar hedge
#

This should now be addressed in v3.0.5

#

Let me know how it is on your end!