Do not upgrade to Windows 10 (yet) if you are using DualShock 4
- Thread starter Knurek
- Start date
jediyoshi
Member
Can confirm here, Hide DS4 working normally now in Windows 10. Just had to restart after stopping the service.
Hmm. I hope someone can find a perma solution sometime that won't affect anything. For now, this is better than nothing anyway.
The Shadow
Member
Basically, this will only affect games that for some reason try to read input from both xinput and directxinput at the same time, necessitating the "Hide DS4" option, which hides the DS4 directxinput. If a game properly allows you to select one or the other, or only works with xinput, then there's no problem.
For instance, I've been replaying the older Tomb Raider games and haven't had a problem with Windows 10 and DS4Windows.
One other "fix" is simply not using DS4Windows, and just configuring your controller in the game. It's time consuming, but will work that way as well. I did this for GRID 2 at one point. That's only if a game allows directxinput though, which some games don't.
Eventually I will run into a game that'll be jacked, it's just a matter of time.
Don't bother with x360ce someone came up with a much better solution.
https://www.reddit.com/r/pcgaming/comments/3f1bso/getting_windows_10_and_the_ds4_controller_to_work/
That post details the SCP method that means you never need ds4windows or input mapper again and it works automatically for all games not just ones you use the x360ce for.
https://www.reddit.com/r/pcgaming/comments/3f1bso/getting_windows_10_and_the_ds4_controller_to_work/
That post details the SCP method that means you never need ds4windows or input mapper again and it works automatically for all games not just ones you use the x360ce for.
jediyoshi
Member
Hooray for less functionality? Why would we want to deliberately cut DS4Windows out of the equation?
I can't see this getting me to drop InputMapper. Love the sheer amount of customization too much. Better than DS4Windows, better than everything else. At least for my purposes. I use SCP server for the DS3 and it's honestly not very good compared to both InputMapper and DS4 windows.
So you don't need to cripple your windows to get it to work?
I think I've found a temporary solution for some games, at least for me. I was having issues with Trails in the Sky, and did some messing around. It also appears to only work over bluetooth for some reason in some games, not wired.
Unplug your controller and make sure it is disconnected from bluetooth.. Go to your Devices and Printers, right click all Wireless controllers that show up, remove device on all of them.
Now plug the controller in with DS4windows running. This will install a 360 and Wireless controller under Devices and Printers, but for whatever reason it will install the 360 as the priority controller (use DS4 Windows, settings, control panel). All the games it was screwed up for, it was Wireless Controller, 360 in order. It works when I have it in the 360, Wireless order. Unplug the controller, hold Share plus PS symbole to pair back it to the bluetooth, and DS4 Windows will see it.
I've only tested this with Trails and Ori and the Blind Forest so far. Works for them. Doesn't work for Dark Souls 2 Scholar but I've always found that game doesn't like having more than one controller on the system so not unexpected (I have a Dolphin Bar, and it would not work with any controllers if I had it plugged in). If I plug in the controller, it does the double inputs in Ori, but if I run it in bluetooth, it was fine. Which is for me personally, I don't play wired very much.
One thing I did notice is plugging it in while running wirelessly sometimes adds a third Wireless Controller into the mix, and then everything is fucked, and has to be started over. So make sure you turn off the controller before plugging it in to charge (use DS4 Windows to software, or hit Options + PS button for a quick turn off).
Unplug your controller and make sure it is disconnected from bluetooth.. Go to your Devices and Printers, right click all Wireless controllers that show up, remove device on all of them.
Now plug the controller in with DS4windows running. This will install a 360 and Wireless controller under Devices and Printers, but for whatever reason it will install the 360 as the priority controller (use DS4 Windows, settings, control panel). All the games it was screwed up for, it was Wireless Controller, 360 in order. It works when I have it in the 360, Wireless order. Unplug the controller, hold Share plus PS symbole to pair back it to the bluetooth, and DS4 Windows will see it.
I've only tested this with Trails and Ori and the Blind Forest so far. Works for them. Doesn't work for Dark Souls 2 Scholar but I've always found that game doesn't like having more than one controller on the system so not unexpected (I have a Dolphin Bar, and it would not work with any controllers if I had it plugged in). If I plug in the controller, it does the double inputs in Ori, but if I run it in bluetooth, it was fine. Which is for me personally, I don't play wired very much.
One thing I did notice is plugging it in while running wirelessly sometimes adds a third Wireless Controller into the mix, and then everything is fucked, and has to be started over. So make sure you turn off the controller before plugging it in to charge (use DS4 Windows to software, or hit Options + PS button for a quick turn off).
jediyoshi
Member
I'll take 'crippling' a completely unused Windows feature set on my end to crippling the actual utility of the controller. Simply using the DS4 normally & DS4Windows + DS4 normally already covers so many use cases, it's bizarre you'd throw away what makes the controller unique purely for the extreme minority of games.
Tal Shiar Agent
Banned
So if I am only playing games that only support Xinput like Fallout 3/New Vegas and Skyrim I don't have to do anything right now, yes?
Felix Lighter
Member
That should be the case, yes. Only the games that require the Hide DS4 option to be enabled will have issues.
I had to use the work around for using the DS4 with bluetooth for Rocket League. x360ce is a cumbersome solution compared to the completely perfect, effortless situation I came from on Windows 8.1 but it does the trick for now. Hopefully, the workarounds and additional information coming around will expose a more elegant fix.
SeeNoWeevil
Member
So disabling the Network List service means InputMapper functions exactly as it did in previous versions?
Rocket League has native DS4 support.
Felix Lighter
Member
It does when wired but not over bluetooth.
Nabs
Member
While it's annoying to deal with, it's not as bad as I thought it would be. You just have to have Network List Service disabled on Startup. Turn on your DS4 and it'll hide the Wireless Controller with no issue. Then you can go ahead and enable Network List Service, start it, then set it to disable so it wont start up next time. You can freely turn off/on your DS4 as you'd like with no conflict.
For me this screws with a lot of apps like Netflix. They think I'm offline. Internet and programs work though, just OS apps.
I don't use a ton of apps though so probably will do this for now.
Nabs
Member
You're free to enable the service once you turn on your controller on once.
I know, I mean after doing so they are still screwed up. The start menu search works again, but all the apps like Netflix still think I'm offline.
Nabs
Member
Gotcha. That sucks.
onken
Member
I can't be bothered to reboot and test but I suspect disabling Network List service has broken Windows update:
"There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070422)"
"There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070422)"
Custom mappings doesn't have anything to do with it. It's just that games will think you have two controllers (1 Xinput, 1 Dinput) at the same time and respond to both because you can't hide the DS4 from the system anymore without doing one of the fixes.
ok thanks for clarifying. i have not come across any games yet with this issue, but i guess its gona crop up at some point..
TheFNEffecT
Member
Works fine over bluetooth for me, even has the PS4 button prompts.
Xbox One controller is the one that went crazy for me.
Upgraded to Windows 10.
the DS4 connects to my computer through DS4Windows no problem. I can start a game and it seems to be registering inputs through DS4W. However, while Start (Options) seems to be working, games (I've tried DOA5LR and Dark Souls) don't register the face buttons.
Yatagarasu does recognize face buttons, but it seems like the button configuration is a bit screwed up there, too.
What do I do?
EDIT: Devil May Cry 4 SE seems to be working flawlessly. Not sure what this means.
the DS4 connects to my computer through DS4Windows no problem. I can start a game and it seems to be registering inputs through DS4W. However, while Start (Options) seems to be working, games (I've tried DOA5LR and Dark Souls) don't register the face buttons.
Yatagarasu does recognize face buttons, but it seems like the button configuration is a bit screwed up there, too.
What do I do?
EDIT: Devil May Cry 4 SE seems to be working flawlessly. Not sure what this means.
synce
Member
Has anyone been able to use the DS3 on Win10 without having to start scpserver.exe every time? If I close the program the controller just shuts off :/
Here's a screen when I first turn on the DS3 via bluetooth: http://i.imgur.com/Gx7HcWO.png
Here's a screen when I first turn on the DS3 via bluetooth: http://i.imgur.com/Gx7HcWO.png
ok i have ds4windows working perfectly now under windows 10 Pro, using exclusive mode so no more double inputs. just sharing what i found over at the devs forums here
http://forums.pcsx2.net/Thread-DS4Windows-J2K?page=56
Full credit and thanks to Vanquo and Vallaqan forum members at above link who figured this out
+rep
Orignally posted by Vanquo
So you basically create a batch file which runs on system boot and disables the Network List Service and runs ds4windows first, and then it re-enables the Network list service, so once its done cortana and search and start menu all work 100% normal. ive tested this several times and it works perfectly.
Once desktop has loaded just wait a short while you will see the batch file window pop-up and minimised while it runs, just let it do its thing.
They key it seems to granting ds4windows exclusive mode is to hit the DS4 PS button as soon as the desktop appears, so login and then on the next screen hit the PS button on the pad. ds4windows will load and ive set mine to minimise on start. You should see a win10 alert saying default controller 1 connected. simples
Note in my batch file ive also added
@ECHO OFF to the top and /min after the first line after start. This runs the batch file minimised, so for those interested here is my batch file below
DS4WindowsFIX.bat
settings in ds4windows app all ive changed is to set the app minimised on launch and hide controller checked. you can test this in fact yourself, if its worked correctly you can check and uncheck hide controller and it will just beep and no error. without the fix above it says cannot gain exclusive mode, turn off uplay, steam etc etc.
hope this helps! maybe other can try and confirm as well
http://forums.pcsx2.net/Thread-DS4Windows-J2K?page=56
Full credit and thanks to Vanquo and Vallaqan forum members at above link who figured this out
+repOrignally posted by Vanquo
So you basically create a batch file which runs on system boot and disables the Network List Service and runs ds4windows first, and then it re-enables the Network list service, so once its done cortana and search and start menu all work 100% normal. ive tested this several times and it works perfectly.
Once desktop has loaded just wait a short while you will see the batch file window pop-up and minimised while it runs, just let it do its thing.
They key it seems to granting ds4windows exclusive mode is to hit the DS4 PS button as soon as the desktop appears, so login and then on the next screen hit the PS button on the pad. ds4windows will load and ive set mine to minimise on start. You should see a win10 alert saying default controller 1 connected. simples
Note in my batch file ive also added
@ECHO OFF to the top and /min after the first line after start. This runs the batch file minimised, so for those interested here is my batch file below
DS4WindowsFIX.bat
settings in ds4windows app all ive changed is to set the app minimised on launch and hide controller checked. you can test this in fact yourself, if its worked correctly you can check and uncheck hide controller and it will just beep and no error. without the fix above it says cannot gain exclusive mode, turn off uplay, steam etc etc.
hope this helps! maybe other can try and confirm as well
Felix Lighter
Member
Thanks! That is an elegant enough solution for me and it appears to work without issue so far.
FFXIII doesn't use standard XInput libraries (because Square Enix), so it won't work with x360.
It does work fine with DS4Windows/InputMapper.
Can you confirm that you really need to press the PS Home button manually for the fix to work? I can't see anything in the batch file that would require doing so...
Nabs
Member
I waited a few minutes before turning on my controller and everything seems perfect.
I'm using the DS4 via BT.
Felix Lighter
Member
There is an issue with a very specific feature. The Hide DS4 Controller option doesn't work if the Network List Service is running before the application starts. There is a work around above that works for me. The feature is necessary for a handful of games that recognize the DS4 as a DirectInput controller. Basically, it sees the spoofed XInput controller and the DirectInput controller at the same time and every input is doubled in these games if the Hide DS4 Controller option is not enabled. Most games that are Xinput only are uneffected.
This is something i have added and works for me everytime. If i dont press the PS button then ds4windows doesnt tie up the controller and i get the 'cant aquire exclusive mode' error. So it may work different for others once they test it, but the method ive outlined works everytime. Im sure a complete solution will be found soon for those who dont want to run batch files, tho its pretty easy to setup..
So, is this required for wired setup or just for BT pairing?
Im running BT not tested wired, but id assume ds4windows would detect a wired pad on startup? Will try and test later.
Even wired the Hide/Exclusive mode doesn't work without the fix on W10.
Pejo
Member
I picked up Dying Light last night and started playing through, and found the jumping/grabbing ledges to be super super difficult, sometimes my character wouldn't jump, sometimes he wouldn't grab the ledge, and also noticed that when I was talking to someone, it kept switching between Square and X prompts, then I realized I was getting the double mapping effect going on.
I'll have to look at some of the fixes in this thread when I get home, but at least for me, it looks like I can by pass it by turning off the "hide controller" option since I'm using it wired. I really hope a more permanent fix is found eventually, I really love using a DS4 on my PC.
I'll have to look at some of the fixes in this thread when I get home, but at least for me, it looks like I can by pass it by turning off the "hide controller" option since I'm using it wired. I really hope a more permanent fix is found eventually, I really love using a DS4 on my PC.
If a game has Dualshock button prompts, it's highly likely it doesn't need DS4Windows running to, you know, support Dualshock.
I'm using Win 8.1 pro and the SCP Server / Zadig solution at the moment...
Never used DS4Windows etc., I'm fully confident with what I get with SCP Server...
Haven't upgraded to W10 yet, because of this thread...
Does the above mean I can safely upgrade to W10 and everything should work like now in regards to DS4 and windows..?
Or should I uninstall all of scp and zadig first (because I need the newer zadig version mentioned in the link) before upgrading??
It works. I'm having no issues with a wired DS4 with the .bat fix. Tested with Dark Souls 2.
Similar threads
- Poll