this post was submitted on 14 Feb 2024
51 points (100.0% liked)
PC Gaming
8551 readers
602 users here now
For PC gaming news and discussion.
PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates.
(Submissions should be from the original source if possible, unless from paywalled or non-english sources.
If the title is clickbait or lacks context you may lightly edit the title.)
founded 1 year ago
MODERATORS
That's not hijacking code. That's working on a data flow.
No, users were banned because AMD took it upon themselves to intercept and change code execution.
It was a completely fucking bonkers decision that anyone remotely aware of game development in any context should have known was literally guaranteed to get anyone who used it banned. It was not, and fundamentally cannot be, acceptable in a competitive game.
The only possible valid way to do it is by working with developers to make the required changes.
You have an authoritarian view on competitive gaming. And you're saying this should be a hard requirement for hardware development. That's an extreme point of view.
It's video games we're talking. If some asshat is cheating in a video game, that's irrelevant to hardware development.
I mean, do also endorse softwares that plague your kernel to prevent cheating? Why don't you use special hardware for your competitive gaming if that's so important?
The world doesn't live around competitive gaming.
It's a gaming only "feature" that is guaranteed to get 100% of people who use it banned.
Yes, intercepting code is bad.