I'll give them a few days to fix this and if not I'm requesting a steam refund for the game, season pass and any other $ spent.
Fuck this kernel level access bullshit.
The game now doesn't start if you have modified .inis to tweak graphics settings or disable frame smoothing. Which means players with low end PCs that could make the game more playable (like me) with those tweaks are now SOL.
Thanks, Capcom.
Ya, we'll see about that. They deployed a patch that requires a highly invasive modification to my system. Sounds like a breach of contract to me.Unless you have less than 2 hours played, don't think that's going to fly with Steam maybe if this blows up and it gets more traction because that rootkit bullshit shouldn't be permitted like at all.
So I am hearing this is actually trying to load an unsigned driver at run time? Don't fresh installs of Windows 10 with Anniversary Update not allow unsigned drivers at all (unless you disable stuff)? This seems like a really bad idea either way!
So I am hearing this is actually trying to load an unsigned driver at run time? Don't fresh installs of Windows 10 with Anniversary Update not allow unsigned drivers at all (unless you disable some stuff)? This seems like a really bad idea either way!
Since this driver is so small, it's also extremely easy to tell what it does. After taking a look, I would never let this product run on my machine.
The driver first registers itself using a pseudo-randomly generated name. That's kind of suspicious. It also doesn't specify any security, so any user at any privilege level can attempt to open and control the device. That's bad.
It sets up custom handlers for opening the device object, closing the device object, and performing ioctls on the device object. This is pretty normal, although a driver that didn't set up basic security when creating its device should perform security checks when opening the device. This driver does not.
The ioctl handler is where everything "interesting" happens. It checks for control codes 0xAA012044 and 0xAA013044, does some buffer size checks, disables data execution protection and then runs the arbitrary code passed in through the ioctl buffer with kernel permissions.
In short, this driver creates a back door which can allow a non-privileged user to run code with permissions of the kernel.
https://www.reddit.com/r/Games/comm...c_update_is_accessing_kernel_level_in/d7z4eev
Yeah this is definitely something you should consider removing ASAP until it's fixed.
What the hell is this? What have they done to the game?
I actually uninstalled yesterday but I stupidly waited until the update was done. Guess I have to go dll digging lol
How safe am I if I just don't play the game? I don't actually need to uninstall if I don't touch SF5, right? It's only dangerous when the game runs it?
How did they think this was OK?
How did they think this was OK?
Good advice. I'll keep the game installed for now -- I assume Capcom is going to fix this ASAP, though I'm probably optimistic -- but at least delete the file.Do a search for capcom.sys just in case. I wouldn't have it installed either, honestly.
What the hell is this? What have they done to the game?
They're getting their money back was their thinking.
I know that much, I meant by using this means.
Good advice. I'll keep the game installed for now -- I assume Capcom is going to fix this ASAP, though I'm probably optimistic -- but at least delete the file.
Have you seen the "daily" challenges? Capcom has Zero respect for their dwindling fan base and they still don't get it.
I'm sorry - I've been in the dark - what's wrong with the daily challenges?
How did they think this was OK?
They don't seem to have thought much beyond that.
They're not Daily like they promised, but weekly.
The time for them varies. Some are longer than others.They're not Daily like they promised, but weekly.
We are in the process of rolling back the security measures added to the PC version of Street Fighter V.
After the rollback process to the PC version, all new content from the September update will still be available to players.
We apologize for the inconvenience and will have an update on the time-frame for the PC rollback solution soon.
https://twitter.com/StreetFighter
Theyre in the process of rolling back the new security measures.
At least theyre fixing it quickly
Basically this post if your question wasn't rhetorical
Have you seen the "daily" challenges? Capcom has Zero respect for their dwindling fan base and they still don't get it.
AKA they got caught and are now trying to destroy the evidence harder than Palmer Luckey's girlfriend
DirectInput has been deprecated since 2005 when Xinput was introduced, and MS stopped recommending that anybody still use it after 2011. I'm not sure what the big deal about DirectInput is, it's Sony's responsibility to implement Xinput support for Dualshock controllers instead of relying on a decade-obsolete standard.
Does anyone know if the "official" wireless adapter Sony released for the Dualshock 4 finally implements Xinput support for PS4 controllers on PC?
No, this isn't right. I have v-sync off via the .ini file and I can run the game. Initially after the update, I couldn't run it, but after running the game as an administrator, it's been ok.
And with that money you can unlock a color a week. Assuming it's affordable.
Capcom needs to get rid of the idiots that keep making these decisions.