Netherscourge
Banned
Apparently the update also broke this thread...
MS made changes that did not allow exclusive mode when Win 10 first released
waiting on MS to fix whatever they broke
Also Microsoft didn't break compatibility, the controllers will work perfectly well with dinput applications. What they won't do is work correctly with xinput applications right now, which the controllers do not support to start with.
Hell, they still work with xinput applications. It's very specifically about the subset of xinput applications that also natively support the DS4. If you want to currently run an xinput wrapper to use the DS4 with some Win10 Store game even, you can.
I'm not Rex Novis, I don't speak for him.
Again I ask, if the problem doesn't affect you, why the fuck are you here? To get into flame wars on a topic that you have no beef in?
Seriously, why are you here?
People that are saying this thread is about Sony support for Windows DS4 Drivers decided that the thread should be about that. Read the fucking OP, nothing was said about Sony not providing drivers. We know Sony doesn't provide drivers, this is how we get past that.
Blaming Sony for not providing drivers for their own controllers would do a lot more towards getting the problem fixed than blaming Microsoft for a third party hackaround using deprecated code no longer working on their new OS.
Why are people being condescending dickbags in here? .
Well, this goes even further down the rabbit hole of what technical problem each individual framework was made for... and I'm probably going to brutalize the explanation by simplifing it... but here we go!
The reason Windows defaults to DInput is because DInput was developed to be as wide reaching as possible to allow a Hardware Developer to make a Racing Wheel with the same type of driver as a Joystick, with the same type of driver as a controller, with the same type of driver... ect, ect you get the point. Anyhow, to do this, the framework is made flexible, but not nessesarily easy to use. This also means that DInput has to support essentially unlimited numbers of buttons and triggersand deals with the raw input data (eg, Button 32 has a current value of 0.56... but what is Button 32? Where is it located on a controller?)actually, there is a limit but its insanely large
By comparison, XInput is a narrow set of specs that deals with a specific type of controller, the Xbox 360 controller and all of its joystick variations (Guitar, Wheel, Dance Pad, ect). Because of this, the framework is easy to use because it is narrow in focus, and because of the popularity of the Xbox 360 controller, it became the standard used by every single Controller Hardware Developer on Windows
And to answer your original question finally, the reason why Windows defaults it to a DInput driver is because it is the more vertisaile. You can guarentee that it will map to DInput in every case, whereas you can only map it to XInput if it fits a specific criteria. Hence why it defaults to DInputActually, it really defaults to what replaced DInput which is RawInput, which XInput is a subclassification of... but that just makes the explanation more complex
Now for your Linux question, DInput, XInputare all Microsoft APIs for how to handle controllers on Windows. Since Linux is a completely different operating system with a completely different set of APIs and complexities, it has its own standard for how a Controller works with Linux APIsand Raw Input
Pretty much, the only way you are going to find a DInput device in 2016, is if you either specifically go out looking for one, or if you get an old controller, or if the Hardware Developer doesn't create a driver for their controllers.
MS superfans do come off as incredible dickbags with no ability to think critically or willingness to engage in conversation. It is almost as if they don't want anyone to talk about these things.
Self righteousness combined with a serious overestimation of their understanding of the world is a noxious mix.
* * *
As to the topic, we have a message from the actual dev of the program saying AnniWin10 will break it and it is MS' fault and there is nothing he can do except hope they change things. That in a nutshell is the power ms wields as the defacto desktop is monopoly. They do something and people have zero recourse. It is the same level of power google wields in search.
Xbox One Wireless controller doesn't work for me as well after the update. Turns off after a second. Great job MS.
Could sony take microsoft to court over this?
Could sony take microsoft to court over this?
They will set all new precedents in flack giving.Could sony take microsoft to court over this?
Could sony take microsoft to court over this?
There is a workaround to this, confirmed (by me) to work for Dark Souls III, Dragon's Dogma and GTA V. This has only been tested wired because I don't have a BT chip in my rig, but it should work wireless by choosing the correct device.
First you need to quit anything that could grab the device before DS4Windows, like Steam. On my rig it's only Steam, but I've heard that some other things may have to be closed as well.
Then, before starting DS4Windows, open the Device Manager. Note that if you have your DualShock connected, there will be one entry under "Human Interface Devices" called "HID-compliant game controller".
Once you start DS4Windows, this entry will be duplicated, you will now have two "HID-compliant game controller"-devices. Disable one of them by right-clicking and choosing from the menu. On my rig it's always the top one that should be disabled, but I don't know how Device Manager orders its devices so it might be the bottom one for you.
If you disable the incorrect entry, the controller will disappear from DS4Windows, so just re-enable it and disable the other one.
Tim Sweeney was telling the truth! Apologise right now, GAF.
With their software capacity, I can imagine PC drivers is on the low priority end of their backlog.Is there any official explanation as to why Sony hasn't released drivers?
Bad advice. This is a solid improvement to W10. You get a native Ubuntu installation for starters which gives you a bash terminal.I wouldn't recommend anyone rush to get this update.
Just a reminder: Lack of exclusive mode support *breaks* Dark Souls 1 and 2 with DualShock4.
Is there any official explanation as to why Sony hasn't released drivers?
It's called an OS update. Of course stuff is going to break.
Sounds to me like this dev is missing a trick. If this was the case, then every controller wouldn't work, not just the DS4. There isn't officially restricted libraries. If third parties can do it, so can this guy.As to the topic, we have a message from the actual dev of the program saying AnniWin10 will break it and it is MS' fault and there is nothing he can do except hope they change things. That in a nutshell is the power ms wields as the defacto desktop is monopoly. They do something and people have zero recourse. It is the same level of power google wields in search.
With their software capacity, I can imagine PC drivers is on the low priority end of their backlog.
Bad advice. This is a solid improvement to W10. You get a native Ubuntu installation for starters which gives you a bash terminal.
To be honest, I think it would the opposite reaction. A reaction of, "oh shit, what have we broke here?". I doubt playing certain games with a DS4 with hacked together community drivers is part of their OS regression pack .Yeah, I can imagine some MS PM is heartbroken that the update mistakenly hurt controllers sold by the competition .
This is an exciting aspect of W10, hopefully it is well integrated with the rest of the environment and catches on. Poor poor Powershell the object oriented approach we deserve.
Sony hasn't built any third party drivers for it. The solution to get the DS4 working on Windows was knife and forked together, and is about as far from "official" as it gets. Sony has no horses in this race.
To be honest, I think it would the opposite reaction. A reaction of, "oh shit, what have we broke here?".
It really is a great implementation! It runs in its own Subsystem and even the mounted windows directories map permissions perfectly and don't get all messed up (FU Cygwin for that). You get dev tools installed by default and you can even install a window manager for it and run a VNC server. Apt-get also works, like everything works natively. You don't need separate packages like in Cygwin.
It removed my need to ever buy a Mac or ever need Linux again.
The first page was testament to my ignore list 😂Funny how those first few conspiracy theorists on the first page aren't posting much in the thread anymore. Probably realised the stupidity in their posts?
Last time I tried to use my DS4 on PC it was a hacked together ass nightmare so it doesn't surprise me that an update broke it.
Ok first of all thank you for the break down. I appreciate it. So from what I'm gathering here DInput is the default because its more versatile but if its truly no longer used in the vast majority of software then that versatility is kind of a moot point. Is the idea that switching these controllers over to XInput would result in compatibility issues? You mention that Dinput garuntees that the controller will map. Is that not the case with XInput? Are there controller that are incapable of remapping to fit the Xinput API? If so why is that? Also, why not just create a configuration tool for XInput to customize button assignments and ensure compatibility on a device by device basis? It just seems like something incredibly basic that would be implemented by now
Right I understand that but the idea of Linux being so much more user friendly is kind of blowing my mind. If an open source OS can create a vastly superior and more flexible implementation what is stopping MS exactly? Is Xinput just not flexible enough to allow for customization button assignments on a device by device basis?
Ok but I still dont understand why a driver is necessary for a device to work in XInput. It just seems like something that could easily be addressed by creating an integrated customizable configuration interface like I mentioned before. Especially since its something other much less profitable and popular OSs have managed to do.
I apologize if I am missing something obvious here. I probably am. But like I said the requirement for drivers in order to operate as an XInput device seems pretty unnecessary to me and something that given my experience with other implementations could be relatively easily remedied to create a less troublesome more seamless experience for the end user.