Do not upgrade to Windows 10 (yet) if you are using DualShock 4
- Thread starter Knurek
- Start date
I have a problem with DS4 Win, simply I can't see the button to replace batch file.
I'm using InputMapper now because DS4Win with some games (Megaman) doesn't work at all, but now in Megaman 3 I'm having some problems to select proper transformation (I simply can't select it and each time I need to randomly push buttons hoping the right transformation will trigger).
So, why I can't see the new button in DS4 Win? I have the latest version available to download from the official site, I also tried to run the updater but it found nothing. Win 10, here, of course.
Nabs
Member
Try disconnecting your controller and checking the Controllers Tab. A pic of what it looks like from jediyoshi.
Just remember to shut down programs like Steam or Mumble before trying it. Good luck.
I tried that yesterday for like thirty minutes, asking also Frost for help, but that button never appears for me
EDIT: The button appeared, now, but Megaman won't work at all, while it works with InputMapper.
Zomba13
Member
Same. I'm not upgrading until I can use the DS4 like I do now, Plugged in via USB, acting as the only controller connected, pretending to be a 360 controller but still letting me use the touchpad as a mouse.
Meteor_of_War
Member
I am able to do all that now with the latest version of DS4Windows on Windows 10.
Sad to hear some are still having issues.
Dsyndrome
Member
I stopped using the .bat at startup method with Inputmapper since I did not want to always connect my controller right at startup. Since I have to kill explorer anyway if I'm reconnecting, just doing an explorer kill .bat works most of the time, and almost always the second time. Wish that some icons didn't disappear from the bottom right section when I did the .bat, but I can live with it.
jediyoshi
Member
you run into those issues with those games anyway on any other windows. this is just a small step on top of the extra step you'd be taking anyway
eso76
Member
Tried yesterday.
Apparently pairing works just fine with ds4 windows and I can use the touchpad to move the mouse arrow around.
Also, inputs are registered correctly under ds4 windows, and windows recognised a "wireless controller".
Still doesnt work in Mame (the only thing I tried). No input registered
Apparently pairing works just fine with ds4 windows and I can use the touchpad to move the mouse arrow around.
Also, inputs are registered correctly under ds4 windows, and windows recognised a "wireless controller".
Still doesnt work in Mame (the only thing I tried). No input registered
Teletraan1
Banned
The killing explorer trick never worked for me. I killed everything running that might cause issue but it never works. It only works when I stop Network list services but that kills my SMB shares on the network. I think I am moving to an XB1 controller or a Steam controller but I have some concerns with the latter due to playing a lot of emulators.
Mauricio_Magus
Banned
Can't get my DS4 to work wireless, it does work wired but I get the 2 player problem.
Dsyndrome
Member
Windows Update 10532 apparently fixes the exclusivity issues. From the InputMapper forums:
https://inputmapper.com/forum/4/614?start=180#top
Unless you're an insider, you'll have to wait until the update's released to the general public. Glad to see it's been fixed.
Edit: I should've looked a few posts ahead of mine. I'd ask what he did differently from others, but he's banned. Others haven't had the issue anymore on InputMapper, anyway.
https://inputmapper.com/forum/4/614?start=180#top
Unless you're an insider, you'll have to wait until the update's released to the general public. Glad to see it's been fixed.
Edit: I should've looked a few posts ahead of mine. I'd ask what he did differently from others, but he's banned. Others haven't had the issue anymore on InputMapper, anyway.
Do you have any idea how long the wait time is, typically? Have had issues with my 8.1 installation slowly breaking over the past few months, and this has kept me from moving up.
Confirmed here too. Looks like we're all in the clear!
FinalxxSin
Banned
I don't use a gaming controller on PC that often, but thanks for the heads up.
SeeNoWeevil
Member
The update isn't out for the non Insider build, right?
What does stopping the network list service actually break?
What does stopping the network list service actually break?
onken
Member
Start menu searching and most importantly Windows Updates. Looking forward to that update but the stopping explorer.exe process temporarily is not too much of a pain.
e- and maybe a mod could update the title?
The Shadow
Member
It's really not. I've been using my Xbox One controller more, but the current work-arounds for DS4 aren't bad at all.
Code:
@echo off
taskkill /IM explorer.exe /f
echo Press any key after connecting your controller.
pause
start explorer.exe1. Cut and paste all that (not the "Code:" part, but everything after) into a text file on your desktop.
2. Replace the ".txt" with ".bat". Icon should change into a window with gears in it.
3. Unplug controller. Wait about 2-3 seconds.
3. Start DS4Windows or InputMapper.
4. Right click on the .bat file you created, select "Run as Administrator".
5. Connect your controller. DS4Windows or InputMapper should say it's running in Exclusive mode.
6. Click on the window that says "Press any key...".
7. Play.
Seems more complicated reading all that, but it's really not. I'm just being verbose so people can use their DS4s in W10.
Hero Prinny
Member
More people need to confirm this, only reason i havent switched to win10 yet
The Shadow
Member
Unless you can provide more details, it's really not. There's still issues with some games. Not all games, some. So if you're not experiencing issues, you've probably just been lucky.
*shrug* What do you want me to say? I no longer get an error when loading up DS4Windows. It goes immediately into Exclusive mode without workarounds of any kind. I tested both Dark Souls 1 and 2 on it and they work perfectly.
jediyoshi
Member
Could you explain? How could this only be partially resolved? What are the games that had issue post Windows 10 but were fixed as part of the update?
The Shadow
Member
Well, what you just said in this post, actually. Specifics. Details.
I'll have to go back to DS4Windows I guess. InputMapper hasn't updated so the .bat file is needed still.
It's a really long story but here goes:
You plug in a DS4 and it installs older DirectInput drivers. Newer games generally use Xinput. Some developers generously allow the use of both DirectInput and Xinput controllers in their games, so that you can use newer Xinput controllers or DirectInput controllers.
When you install a program like DS4Windows, it "wraps" the DirectInput drivers to be Xinput commands. This is useful for games that only work with Xinput controllers. The issue with this is that the system now thinks that there is a DirectInput and Xinput controller plugged into the system at the same time. This isn't an issue most of the time because most games (smartly) allow you to assign one controller or another and not assume you're using both at the same time.
A "fix" for this was to hide the DirectInput driver from windows so that it's only reading the Xinput wraper. In order for this fix to work, DS4Windows and other wrappers must have exclusive control of the controller driver (exclusive mode). Windows 10 broke this fix because it didn't allow these wrappers exclusive control, therefore games could see both DirectInput and Xinput versions of the DS4 controller even if you elected to hide DirectInput.
So Windows 10 didn't really "break" the DS4 or the wrappers. It basically broke the fix that some games needed to use the DS4 properly. Keep in mind, it's not all games, just a specific list of games that don't work properly with both DirectInput and Xinput active.
I don't know the specific games but I know Dark Souls is one of them. I honestly haven't had any trouble since upgrading Windows 10, but that just means I haven't played any of the games that had this issue.
Grinchy
Banned
Thanks for explaining that. I had seen this fix earlier in the thread but I didn't really know how to use it and never tried.
Hopefully I can go back to playing emulators soon with this (or at least the ones that needed the Hide DS4 option)
jediyoshi
Member
That was absolutely not the question I asked. Check the thread, I've already been responding since the beginning. I'm saying the issue is holistic, either a game natively supports the DS4 and double inputs become a problem through xinput and so it's "broken" until exclusive mode is worked through or it worked exactly as it did before Windows 10 by not supporting the DS4. What is this new subset of games now that are broken post Windows 10 that aren't also affected by a wrapper's ability to go exclusive? At best that just sounds like an issue irrelevant to the version of Windows running.
Brad Grenz
Member
The exclusive mode problem was resolved in Insider Build 10532. Don't know if the fix has been disseminated to other W10 users yet, though.
boredandlazy
Member
So eventually everything should work fine without the need for batch files etc.?
Brad Grenz
Member
Yes, that would be my expectation.
jediyoshi
Member
Only in so far that you don't need to do that extra step. The part in which you have to do something like quit Steam if you didn't already have DS4Windows running while in exclusive mode still has to be worked around as always.
onken
Member
Are you the insider program per chance?
If I am, it's news to me.
The Shadow
Member
Oops. I'm sorry. Didn't realize I was responding to the thread expert. Thought I was just helping someone and didn't mean to step on any toes.
SeeNoWeevil
Member
Has the update that fixes this been pushed out in the non Insider build yet? The latest cumulative update refuses to install on my box.
Thank goodness for this thread. I've been pushing that postpone button on the upgrade to Win10 for about a month now, but today while I was away it decided to upgrade automatically.
After the upgrade it took me a while to research and realize I needed the newest DS4Windows update, and needed to push that "connect DS4 exclusively (experimental)" button, and needed to only plug in the controller while that console window was open before hitting enter. This seems to have made things work. Thanks for all the hard work on this app and info in this thread.
Awful first impression of Win10 though, that initial boot up at 800x600 & 30 minute install of 25+ updates, this trouble, and everything I've heard from podcasts about Win10 is making me uncertain about this upgrade.
After the upgrade it took me a while to research and realize I needed the newest DS4Windows update, and needed to push that "connect DS4 exclusively (experimental)" button, and needed to only plug in the controller while that console window was open before hitting enter. This seems to have made things work. Thanks for all the hard work on this app and info in this thread.
Awful first impression of Win10 though, that initial boot up at 800x600 & 30 minute install of 25+ updates, this trouble, and everything I've heard from podcasts about Win10 is making me uncertain about this upgrade.
Leatherface
Member
I've been using DS4 just fine via Bluetooth and USB on windows 10 with DS4windows. I did absolutely nothing special to make this work.
Damn maybe I should try wireless. I should have mentioned I was trying this wired which I assumed was simpler, but maybe not.
Similar threads
- Poll