Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

938

nullDC won't recognize my controller for PuruPuru and it seems that the old Scarlet.Crush I had downloaded isn't working for myDS4 controller. Did a bit of sarching and found the continuation of the Scarlet.Crush SCPToolkit from nefarius on GitHub but his last update was 6 years ago.

Basically, what do I need to do to make my DS4 be recognized by the XBox 360 Accessories Status so I can use my DS4 in nullDC on Win7?

edit: so I found Jays2Kings original DS4Windows which is now out of development since Windows 7 is officially dead. It can be found on various "old version" software sites as well as the official GitHub. I haven't tested it out. https://github.com/Jays2Kings/DS4Windows/releases https://ds4windows.en.lo4d.com/windows

It has since been forked and updated by another developer. This version is for Windows 10 and does not work on previous versions, while the previous version worked on Windows XP, 7, 8, and 8.1, but would only work on Windows 10 with an unstable workaround. https://ryochan7.github.io/ds4windows-site/

And there is an update version of x360ce now as well. https://github.com/x360ce/x360ce/releases https://www.x360ce.com/

edit: So it turns out that this has been extremely helpful for me simply by chance. While testing out thes other programs, which both worked (I used the last stable 1.4.52 of Jays2Kings DS4Windows and version 3 64-bit of x360ce) I found out that there are some unexpected behavior from the more fully featured DS4Windows.

By chance I simply decided to test the programs using Castle Crashers since I was looking through PC games to try it on and I remembered that there was a corruption issue with the Steam emulator for my pirated version the last time I tried to play.

Well, for DS4Windows Castle Crashers see the controller as both player 1 and player 2, which prevents starting the game sinnce pressing the 'A' button will confirm character selection for player 1 but also make player 2 join the game (then the keyboard will behave similarly for player 3 after that - I do want to test this behavior more).

However, it works perfectly with x360ce, which unfortunately doesn't support the touchpad, obviously since it wasn't designed specifically for PS4 DS4 controllers and instead for generic gamepads.

So it is good to have both of these tools, depending on the game being used.

I also have a full version of XPadder 5.7, but the limitation of this program is that it does not support full analogue movement on the joysticks or trigger buttons, which I found out while attempting to p[lay Jet Grind Radio for Dreamcast through nullDC emulator. However, XPadder will for great with a PS4 DS4 for older PC games which were designed for keyboard controls rather than older gamepads which had far few inputs, such as Descent.

So don't rely on one single program and keep them all around. I still need to look into getting the PS4 DS4 working with the original Scarlet.Crush programs, so I guess next up is finding the last stable build of the SCPToolkit and going from there.

nullDC won't recognize my controller for PuruPuru and it seems that the old Scarlet.Crush I had downloaded isn't working for myDS4 controller. Did a bit of sarching and found the continuation of the Scarlet.Crush SCPToolkit from nefarius on GitHub but his last update was 6 years ago. Basically, what do I need to do to make my DS4 be recognized by the XBox 360 Accessories Status so I can use my DS4 in nullDC on Win7? edit: so I found Jays2Kings original DS4Windows which is now out of development since Windows 7 is officially dead. It can be found on various "old version" software sites as well as the official GitHub. I haven't tested it out. https://github.com/Jays2Kings/DS4Windows/releases https://ds4windows.en.lo4d.com/windows It has since been forked and updated by another developer. This version is for Windows 10 and does not work on previous versions, while the previous version worked on Windows XP, 7, 8, and 8.1, but would only work on Windows 10 with an unstable workaround. https://ryochan7.github.io/ds4windows-site/ And there is an update version of x360ce now as well. https://github.com/x360ce/x360ce/releases https://www.x360ce.com/ edit: So it turns out that this has been extremely helpful for me simply by chance. While testing out thes other programs, which both worked (I used the last stable 1.4.52 of Jays2Kings DS4Windows and version 3 64-bit of x360ce) I found out that there are some unexpected behavior from the more fully featured DS4Windows. By chance I simply decided to test the programs using Castle Crashers since I was looking through PC games to try it on and I remembered that there was a corruption issue with the Steam emulator for my pirated version the last time I tried to play. Well, for DS4Windows Castle Crashers see the controller as both player 1 and player 2, which prevents starting the game sinnce pressing the 'A' button will confirm character selection for player 1 but also make player 2 join the game (then the keyboard will behave similarly for player 3 after that - I do want to test this behavior more). However, it works perfectly with x360ce, which unfortunately doesn't support the touchpad, obviously since it wasn't designed specifically for PS4 DS4 controllers and instead for generic gamepads. So it is good to have both of these tools, depending on the game being used. I also have a full version of XPadder 5.7, but the limitation of this program is that it does not support full analogue movement on the joysticks or trigger buttons, which I found out while attempting to p[lay Jet Grind Radio for Dreamcast through nullDC emulator. However, XPadder will for great with a PS4 DS4 for older PC games which were designed for keyboard controls rather than older gamepads which had far few inputs, such as Descent. So don't rely on one single program and keep them all around. I still need to look into getting the PS4 DS4 working with the original Scarlet.Crush programs, so I guess next up is finding the last stable build of the SCPToolkit and going from there.

(post is archived)