this post was submitted on 26 Nov 2024
289 points (98.0% liked)
Games
32701 readers
991 users here now
Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.
Weekly Threads:
Rules:
-
Submissions have to be related to games
-
No bigotry or harassment, be civil
-
No excessive self-promotion
-
Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts
-
Mark Spoilers and NSFW
-
No linking to piracy
More information about the community rules can be found here.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Curious as to why this happens. My bet is on Ubisoft tampering in windows kernel space. Probably some copy protection or anti-cheat BS
Aren't all of these SP games? The fuck they need anti-cheat for?
You know the cosmetics things that you could unlock using cheat codes 20 years ago in single player games ? You now have to pay for it. And they bloat your OS kernel to ensure that you don’t get those valuables skins without actually paying for it.
Lol yea long ass time ago, when crack engines where a thing or even console codes. The fuck....
And a lot of the items were introduced on the initiative of developers without any coordination with Marketing team
It's probably kernel level anti-piracy shit, but same results.
Ubisoft sells cosmetic stuff in their singleplayer games.
Most of it gets cracked anyways though, but I guess lol shit reason for them but only explanation.
They only need to make sure it's difficult enough the average user can't be bothered to figure out the workaround. I'm sure without looking they made a considerate sum from the neglected children market.
That's the truth, they wouldn't do it if they didn't make money off it.
I was curious too, and... Avatar appears to have a co-op mode. Not really high stakes for cheating.
Yeah, developers like to rely on undocumented or quirky behavior.
But then, Microsoft also likes to change code that may or may not behave like the documentation says it should.
Microsoft does a piss poor job of documenting things, so a certain level of reliance on undocumented behavior is hard to avoid.
That's no excuse for games hacking the kernel, though.
It was interesting learning about the insane shit firewalls and drivers did prior to vista.
Even after, some of it is pretty crazy.
Like the driver for controlling one vendor's LED lights had a generic PCI FW updater (or something similar) included that it exposed to user space. This meant a) changing the LED colours or parameters required a firmware update rather than the firmware handling input from the system to adjust colours without new code, and b) other software could use this and just change the bus id of the target to update other firmware willy nilly.
It also had to compete for bus time and sending a full firmware update takes more time than a few colour update parameters. Average case might be ok, but it would make worst case scenarios worse, like OS wants to page in from disk 1 while a game needs to read shader code from disk 2 that it needs to immediately send to the GPU but the led controller decides it's time to switch to the next theme in the list oh and there's some packets that just came in over the network and the audio buffer is getting low. GPU ends up missing a frame deadline for the display engine and your screen goes black for a second while it re-establishes the connection between GPU and monitor.
I’d be real interested to see if the problem continues, once someone disables the TPM piece of Win 11.