Barkley's Justice
Member
fffffff
fffffff
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.
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.
One more anti-game monopoly stunt from Windows 10, and I will make sure they get the Konami Treatment.
(FYI, I never really used my DS4 on Windows 10 anyway, I just love my diverse gaming community)
It's called an OS update. Of course stuff is going to break.
Wow, people are defending that an OS update breaks stuff? Modern Software Engineering is so bad, it actually trains people to expect shoddy workmanship.
As a computer scientist, you don't need to explain to me how hard making correctly working stuff can be, I know that bugs happen, but I don't feel like an organisation like MS is spending enough time on these hard technical realities and much more on terrible monetisation techniques. And I really feel like this is more a general trend in software developement and less something specific about MS.Are you a developer? If not, have you ever developed anything? Fixing bugs can easily lead to unforeseen consequences, elsewhere. I think it's arrogant to come in and make a post like that "MSE is so bad". Operating systems, whether it's Windows, Linux, OSX or whatever, are incredibly complicated, and stuff breaks all the time.
Wow, people are defending that an OS update breaks stuff? Modern Software Engineering is so bad, it actually trains people to expect shoddy workmanship.
Send an email to MS stating how you think it's diabolical that in their regression pack they don't include playing a subset of games with a third party community driver which uses depreciated libraries.It happens, but I don't feel like an organisation like MS is spending enough time on these hard technical realities and much more on terrible monetisation techniques. And I really feel like this is more a general trend in software developement and less something specific about MS.
In a related note, the current update gives me some weird error messages about the NT kernel failing, so I'm sorry if I don't think it's terribly arrogant to call them bad engineers.
As a computer scientist, you don't need to explain to me how hard making correctly working stuff can be, I know that bugs happen, but I don't feel like an organisation like MS is spending enough time on these hard technical realities and much more on terrible monetisation techniques. And I really feel like this is more a general trend in software developement and less something specific about MS.
In a related note, the current update gives me some weird error messages about the NT kernel failing, so I'm sorry if I don't think it's terribly arrogant to call them bad engineers.
If you're a computer scientist, you should be aware how complicated this stuff is. I still believe it's incredibly arrogant of you to assume, that the engineers and developers working on Windows are bad at their job. In my mind, it shows that you have absolutely no idea what you're talking about.
What is your area of expertise?
If the guy with the CS degree thinks that some of the bugs / errors are of a basic level that shouldn't have made its way past testing / been made in the first place ...... I am inclined to listen to him.
The level of complication of a system or item is not an excuse for basic errors.
What is your area of expertise?
If the guy with the CS degree thinks that some of the bugs / errors are of a basic level that shouldn't have made its way past testing / been made in the first place ...... I am inclined to listen to him.
The level of complication of a system or item is not an excuse for basic errors.
I didn't say they are bad in general, but I don't feel like they did a good job with what should be a routine update. Again, never had an OS bluescreen on me during the update process.If you're a computer scientist, you should be aware how complicated this stuff is. I still believe it's incredibly arrogant of you to assume, that the engineers and developers working on Windows are bad at their job. In my mind, it shows that you have absolutely no idea what you're talking about. You can disagree with their decisions, their direction, but if you think Microsoft hires bad engineers as a general rule, I'm not sure what to tell you.
I work in IT. "The guy with the CS degree" doesn't have access to the source code and probably has no idea how good the engineers at Microsoft are, hence when he claims that they are "bad", it comes across as incredibly arrogant. Also, he hasn't written (from what I can see) if he think the bugs are of a "basic level" (how do you define "basic level" and/or "basic errors" in development?) or not.
I didn't say they are bad in general, but I don't feel like they did a good job with what should be a routine update. Again, never had an OS bluescreen on me during the update process.
I think I'll wait a few weeks, maybe a few people will figure out how to get past that error (I tried it a second time and the same thing happened)
Fair enough, but your opinion is based solely on assumption, like you are claiming the "arrogant" poster is also doing.
What is your area of expertise?
If the guy with the CS degree thinks that some of the bugs / errors are of a basic level that shouldn't have made its way past testing / been made in the first place ...... I am inclined to listen to him.
The level of complication of a system or item is not an excuse for basic errors.
I work in IT. "The guy with the CS degree" doesn't have access to the source code and probably has no idea how good the engineers at Microsoft are, hence when he claims that they are "bad", it comes across as incredibly arrogant. Also, he hasn't written (from what I can see) if he think the bugs are of a "basic level" (how do you define "basic level" and/or "basic errors" in development?) or not.
I don't feel like an organisation like MS is spending enough time on these hard technical realities and much more on terrible monetisation techniques. And I really feel like this is more a general trend in software developement and less something specific about MS.
Hardware in general is much more stable than software. Stuff like model checking became really popular for circuitry. I'm not saying formal verficitation is a panacea that will fix everything, but looking how unreliable modern software is in my experience and I'm not even comparing it to stuff in the 70ies or 80ies since I didn't live back then (though the basic Unix tools from back then are among the most stable pieces of software I have ever known) it's clearly not enough to just have good engineers (how ever you measure that) but you need good leadership and direction. And everything good about Windows 10 has been completely overshadowed by how terrible MS is at focusing on stuff that makes an OS great.I've seen iPhones brick during updates, Windows-installations failing/blue-screening and Android-phones rebooting on their own. It happens and isn't necessarily due to bad coding. Hardware-failures are also a common reason for crashes.
I wouldn't say hardware failures, I'd say it's hard to encounter for every hardware variation and every current state the OS is in when updating is the main reason for this.I've seen iPhones brick during updates, Windows-installations failing/blue-screening and Android-phones rebooting on their own. It happens and isn't necessarily due to bad coding. Hardware-failures are also a common reason for crashes.
Hardware in general is much more stable than software. Stuff like model checking became really popular for circuitry. I'm not saying formal verficitation is a panacea that will fix everything, but looking how unreliable modern software is in my experience and I'm not even comparing it to stuff in the 70ies or 80ies since I didn't live back then (though the basic Unix tools from back then are among the most stable pieces of software I have ever known) it's clearly not enough to just have good engineers (how ever you measure that) but you need good leadership and direction. And everything good about Windows 10 has been completely overshadowed by how terrible MS is at focusing on stuff that makes an OS great.
Am I claiming that this view is purely professional and not flavored by my personal bias? No, but I'm sorry if your argument seem like dogmatic apolegetics to me.
Id say Microsoft are only just about getting the amount of flak they deserve for their terrible engineers and leaders performance. They could and should get more flak though.
Is there a general thread for the Windows 10 Anniversary Update *cough* 0x80070057 *cough*
Seriosuly, this update won't even appear on my Windows Update, even after having unchecked the Defer Upgrades option.
Maybe I was a tad emotional. But I don't think even the people at MS can currently claim (if they are being honest) that they are currently making the best of their abilities. I guess if you get paid well enough that doesn't hurt to much, but still.Indeed, hardware is more stable than software. But blaming crashes, bugs and what have you on "bad engineers" (which is what you wrote) doesn't make sense.
Maybe I was a tad emotional. But I don't think even the people at MS can currently claim (if they are being honest) that they are currently making the best of their abilities. I guess if you get paid well enough that doesn't hurt to much, but still.
I'm all for pulling on MS when they pull shady shit, but this is on Sony. Why they've not released drivers for Windows is beyond me.
That said I once again feel vindicated in sticking with 8.1.
The cause is once again, a so far undetermined Windows process is enumerating and connecting to all HID devices. This enumeration should be better filtered as it should only apply to certain GUID or device classes such as keyboards and mice and not also to devices that also appear in HID enumeration such as gamepads.
This issue was corrected once before in Windows 10 as the early releases had the same issue.
Current workaround is to disable then re-enable the HID device in device manager. Other programs will then be able to access it exclusively again.
We've literally had Windows 10 updates that accidentally broke Microsoft's own god damn controller.
But no, it's a conspiracy.
Xbox One controller has also been broken by the update.
With which games?
Yes.I don't feel like an organisation like MS is spending enough time on these hard technical realities and much more on terrible monetisation techniques.
Tim Sweeney certainly doesn't need "redemption".I like how every time Windows breaks something it's going to be seen as Sweeny's redemption.
Windows is trying to connect to all HID devices and this breaks things when an application requires exclusive access. They reintroduced a bug they had before. This would affect all HID gamepads/devices in programs/devices that require exclusive access.