91–100 of 371 posts
Does this mean the end of custom accessibility controllers?
It does say "unauthorized", so I assume it should still be possible to get an official license to make a third party controller, though we'll have to see if that's actually going to be the case.
This is a money grab with the polish of a pro-gamer cheat-cleanup. Why do I say that? Microsoft can fix most of the 'cheats' that a software controller can implement in software. Auto-fire is trivial to detect, as is a KBM setup where it doesn't belong. Out of the ordinary joystick characteristics/speed/hysteresis/range would make it obvious to them which controllers are aftermarket if they cared to disallow them aft…
> players have been encountering error “0x82d60002” OT: Microsoft should be banned by decree from showing naked error codes to people, I've been fighting them for decades now
At least you can google for the error code, instead of having to search for a textual phrase and wade through countless pages of not-at-all-related crap.
This is a money grab with the polish of a pro-gamer cheat-cleanup. Why do I say that? Microsoft can fix most of the 'cheats' that a software controller can implement in software. Auto-fire is trivial to detect, as is a KBM setup where it doesn't belong. Out of the ordinary joystick characteristics/speed/hysteresis/range would make it obvious to them which controllers are aftermarket if they cared to disallow them aft…
So should they just give up on cheating devices?
> players have been encountering error “0x82d60002” OT: Microsoft should be banned by decree from showing naked error codes to people, I've been fighting them for decades now
At least you can google for the error code, instead of having to search for a textual phrase and wade through countless pages of not-at-all-related crap.
I get better error messages from the firmware of obscure embedded chips than from Microsoft Windows
> players have been encountering error “0x82d60002” OT: Microsoft should be banned by decree from showing naked error codes to people, I've been fighting them for decades now
At least you can google for the error code, instead of having to search for a textual phrase and wade through countless pages of not-at-all-related crap.
This is one reason the Steam Deck model of being an open console system is the future. Some dinosaurs wants to preserve the old locked-down console experience, where you have exclusive games, controllers and digital stores. But its just worse for the customer in every way.
Good thing Microsoft didn't just buy a major AAA game company to decrease the odds of that working.
Sony buying them would be much larger problem.
This is a money grab with the polish of a pro-gamer cheat-cleanup. Why do I say that? Microsoft can fix most of the 'cheats' that a software controller can implement in software. Auto-fire is trivial to detect, as is a KBM setup where it doesn't belong. Out of the ordinary joystick characteristics/speed/hysteresis/range would make it obvious to them which controllers are aftermarket if they cared to disallow them aft…
[..]
"if they cared to disallow them after only a few minutes of profiling the player."
Definitely not trivial and a gross over simplification. It will create a whole bunch of grey area's and endless tweaking. Which in turn will lead to people getting unfairly banned. Meaning Microsoft will then need to investigate these cases to unban them.
Earlier quoted context omitted.
Good thing Microsoft didn't just buy a major AAA game company to decrease the odds of that working.
Microsoft still releases majority of games for Windows. Sony buying them would be much larger problem.
> players have been encountering error “0x82d60002” OT: Microsoft should be banned by decree from showing naked error codes to people, I've been fighting them for decades now
At least you can google for the error code, instead of having to search for a textual phrase and wade through countless pages of not-at-all-related crap.