I don't get that, you can pretty much find all the same packages you do for Linux distros in OSX. Why would you say they're amateurs? You get all the pre-built Linux utilities in there.
Atleast it's not powershell.
-
Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.
Windows 10 Anniversary Update breaks Dual Shock 4 drivers.
- Thread starter Havel
- Start date
Atleast it's not powershell.
Iirc they are gping to remove gpedit.msc for pro. And prevent unsigned drovers. Not sure if its now with this anniv. update or in the future, but yay!...
Panajev2001a
GAF's Pleasant Genius
I am sad powershell did. It get the love and spread it deserved. Personally I prefer the idea and debuggability of an object oriented languages based design than essentially string manipulations and commands concatenation that we have now. Bash is hardly easy to debug
.Then again my powershell practically experience is limited so I have not seen darker corner cases beyond the lack of third party packages and tools compared to bash/zsh today...
I think the major problem is (like with the Upgrade last year) Microsoft goes and "checks" for the latest update of things and then either overwrites to a default state (causing a conflict) or installs the software which conflicts with something else.
Microsoft should just stop going back to the "default state" when you update/upgrade your OS. Especially if it isn't a new install. I could understand checking for the latest drivers for the hardware and things, but looking for the latest drivers for things not plugged in currently and/or optional like controllers?
GwyndolinCinder
Member
Did it break DS3 too? Mine seems to have gone...
SeeNoWeevil
Member
The same thing happened on the retail release of Win 10.
I 'gave in' and bought an XB1 controller.
I 'gave in' and bought an XB1 controller.
TBiddy
Member
They are. Internally. The build numbers aren't arbitrary. The version numbers relate to the date. I'm sorry you didn't know that, but that falls solely on you.
There are no serious developers that rely solely on Microsofts (or anyone elses) internal build numbers, when they determine whether or not they need to fix their shit. If you were a developer, you'd run tests. That's one of the reasons, Insider Versions/Betas are released. It's for developers to test if everything is running as expected.
It doesn't need to. It's not meant to be used by anyone outside of MS, and especially not by developers, basing their "should we fix it or not" decisions, based on that.
dragonelite
Member
The reason companies have developers preview, unless it does not happens in the preview.
Night Terror
Member
How long did it take for this to be fixed last time?
Now I can't use my DS3 and IDK how I'll play some of the games I own. Killer Instinct being one of them. FFS Microsoft QQ
Now I can't use my DS3 and IDK how I'll play some of the games I own. Killer Instinct being one of them. FFS Microsoft QQ
Bits N Pieces
Member
Im still chuckling to myself when I read back the first page again
Krappadizzle
Member
Drivers were all community driven. Not surprised in the least that the update broke it. It'll be fixed in a few weeks anyways. It's par the course until Sony decides to officially support DS4 on Windows and put some resources behind it. I don't understand the outrage here.
MightyHedgehog
Member
Not that I like the DS4 very much when I can choose other gamepads for PC, but it kind of amazes me that Sony hasn't yet decided to officially support their product with an official driver already. It would only help sell them as well as boost popularity of their gamepad design among PC players.
Ricky Ricardo
Member
Im still chuckling to myself when I read back the first page again
I'm very interested in seeing Nynt9's next thoughtful thought-piece on ways we can hold Microsoft more accountable.
Hibiki Kurosawa
Member
Tim was onto something!
Bits N Pieces
Member
The Omega Man
Member
I think Witcher 3 has native support which is different
The real crime here is playing KI on a DualShock 3
Night Terror
Member
Shhht. It's alright, my child. KEK.
On a serious note: Remember guys, you can roll back to the previous non-Anniversary build via the Update and Security setting window.
If you guys want to avoid to install this build (1607), you can use the following tool to "hide" it:
https://support.microsoft.com/en-us/kb/3073930
EDIT: Actually you guys might want to put this on the first post.
PapaJustify
Member
Nah, of course you are using command line. But not Terminal. Use iTerm2 instead. Just to give one example.
Ah indeed. Now that you say it, I remember the prompts were the DS4 buttons and not the XBOX's ones.
Gotta check it again tonight.
Teletraan1
Banned
For sure, I wasn't trying to imply that exclusive mode was something inherent to xinput. It is a hack workaround that hides the non xinput version of the controller to avoid double inputs and has had its functionality broken multiple times since W10 has released. My main point was that there is nothing the software wrapper folks can do about it. It is all on MS to either fix or leave broken.
BlazinSkatinAxel
Member
There isn't anything to fix. The controller isn't a xinput controller. If Sony releases a xinput version via drivers or controller, it would work.
sir_dany12
Member
Is this the thread where we hate microsoft and talk about their evil plan?
It's an additional option beside the other threads, yes.
Jin
Member
Same here. Tried uninstalling, reboot, and reinstall wireless adapter, changing USB port, resyncing, etc. My elite controller would turn on, the light would stabilize showing it's synced, then turn off after 2 seconds. Between this and the driver earlier this year that causes beeping and freezing I really don't understand why it's so hard to get a controller working. The 360 was plug and play and no issue for many years.
Dsyndrome
Member
Workaround from the Inputmapper dev if you don't want to switch to SCPServer:
https://inputmapper.com/20-windows-10-1607-au-exclusive-mode-fix
Here's a video he did showing how to do it:
https://inputmapper.com/20-windows-10-1607-au-exclusive-mode-fix
FleetingFlowAir
Member
Can confirm, this workaround worked for me and Dark Souls III is now playable again. The Bluetooth HID Device step may vary though if you're using the DS4 wired.
Ha, stupid on my part. Yeah, iTerm2 ftw on OSX.
Head.spawn
Junior Member
So they have PC Remote Play, but they still haven't released modern drivers?
I don't understand why people are making more of a fuss about MS in this instance and not being on Sony's case to supply drivers, it has been three years... which i can only imagine would be a trivial task for a software company like that. Gamers shouldn't be relying on other gamers to create third party work around to use their product.
Teletraan1
Banned
Probably something to do with how ingrained the XBOX controller is into xinput thanks to how they introduced xinput with the 360 controller and depreciated direct input to the point where basic features like rumble wouldn't work because of reasons on the 360 controller if developers used directinput. It wouldn't be like the button prompts are magically going to be playstation prompts just because they made a xinput driver. I might be wrong but most xinput devices share the same button nomenclature as the 360 controller. I doubt sony would want to officially endorse a confusing product such as that and having to rely on the mod community on a game by game basis to change button prompts lol.
spazimoose
Member
Its really hard to give Microsoft any benefit of the doubt when they keep doing stuff like this. Gaming outside of UWP is clearly not their priority if not their outright enemy. If Microsoft was really putting all PC gaming first then they wouldn't let stuff like this happen.
I really do hope I'm wrong. Microsoft is clearly inconveniencing a lot of people here. Maybe it really is development/testing oversight but it's honesly just a little to convenient. Never trust any company to have your best interest at heart, that's just naive.
I really do hope I'm wrong. Microsoft is clearly inconveniencing a lot of people here. Maybe it really is development/testing oversight but it's honesly just a little to convenient. Never trust any company to have your best interest at heart, that's just naive.
Just tested the latest SCP and X-input wrapping for my wired DS4 is working correctly after the Windows 10 Anniversary Update.
Teletraan1
Banned
You are seriously posting this on a gaming forum. We might get there someday and I sincerely hope we do but Linux gaming support is hit and miss right now. Probably less than 10% of my Steam Library offers native Linux versions and absolutely 0% of those games are AAA games. Games and how they perform are really the only thing keeping a lot of people on windows. But as you say since they don't trust microsoft they should probably abandon 90% of PC gaming. Makes sense to have such strong binary principals.
Head.spawn
Junior Member
Good points ask around, though I think of Sony went with official drivers though, developers would be more inclined to give us the option to select our own default button prompts.
Panajev2001a
GAF's Pleasant Genius
Oh yeah... I was assuming iTerm2 + oh-my-zsh + agnoster + got integration and all .json/.js/.sh/etc... scripts and files set to open in Visual Studio Code by default. Good use of the open / open -a command as well as its counterpart cdto on Finder as a must too
.
Teletraan1
Banned
It would be nice but I don't expect it. Some games that detected that you had a direct input PS pad plugged in have switched to those prompts. The Witcher 3 did this for sure, FFXIV on PC let me show PS prompts independent of what controller was plugged in. It would take a huge effort to steer developers into allowing both types of button prompts and frankly I doubt the amount of people who bootleg use a DS4 on windows warrants such a change. It would be nice if this was fixed for the handful of people who prefer this over the 360 pad layout even though the hardliners in this thread keep insisting there is nothing to fix. If it becomes much more of a problem I think I will just buy the next revision of the Steam Controller which even uses the "proper" xbox style button prompts.
Tortahegeszto
Member
I haven't tried the DS4 with just scp server but so far:
With DS4Windows:
-Rise of the Tomb Raider still works
-Doom doesn't recognise the controller at all
-Witcher 3 recognises every button press twice
If I just connect the controller without ds4windows Witcher 3 works well and even has PS button prompts, but I can't use the controller via bluetooth.
The Dualshock 3 with scp server never needed exclusive mode, so it's works as well before. However it feels extremely small after using DS4 for quite a while.
With DS4Windows:
-Rise of the Tomb Raider still works
-Doom doesn't recognise the controller at all
-Witcher 3 recognises every button press twice
If I just connect the controller without ds4windows Witcher 3 works well and even has PS button prompts, but I can't use the controller via bluetooth.
The Dualshock 3 with scp server never needed exclusive mode, so it's works as well before. However it feels extremely small after using DS4 for quite a while.
You are off by 7 years. It's been 10 years since the six axis was released and 9 Since the Dualshock 3 was released. There's still no sign of any kind of official support from Sony.
Diablohead
Member
There's still issues with the xbox controller drivers in windows 10 that cause performance issues when disconnected until you fully reboot the pc.
Microsoft can't even fix their own controller issues after what feels like 5 months of the big being present.
Microsoft can't even fix their own controller issues after what feels like 5 months of the big being present.
NotDigital
Neo Member
I was getting the exact same thing earlier so I connected my controller via usb so that I could play Rocket League. When I finished playing I disconnected the cable, turned the controller off and powered it back up again and it's staying connected while wireless now. Might want to give that a shot if you haven't already.
