- cross-posted to:
- PCGaming@kbin.social
AMD users should think twice before installing driver update 23.10.1.
- andyburke ( @andyburke@kbin.social ) 10•1 year ago
people really enjoy the boot of anti-cheat on their necks.
maybe these companies could move their cheat detection to the server where they control the code. maybe don’t just send all player positions so wall-hacks become impossible. maybe use some machine learning to look at input patterns and detect when a player is sending things that don’t look human.
the list of things companies could do to actually fix cheating in pvp games is long and all they want to do is pay for ridiculous anti-cheat that impacts normal users.
ridiculous.
- falsem ( @falsem@kbin.social ) 8•1 year ago
Erroneous bans, they intend to reverse them once AMD implements a fix:
AMD’s latest driver has made their “Anti-Lag/+” feature available for CS2, which is implemented by detouring engine dll functions.
If you are an AMD customer and play CS2, DO NOT ENABLE ANTI-LAG/+; any tampering with CS code will result in a VAC ban.
Once AMD ships an update we can do the work of identifying affected users and reversing their ban. @AMD - t�m ( @finickydesert@lemmy.ml ) 2•1 year ago
So lag is officially part of counter strike?
- conciselyverbose ( @conciselyverbose@kbin.social ) 8•1 year ago
If you inject code, they ban you. Seems pretty straight forward.
They said they’ll unban when they can identify them correctly, but it’s not their fault.
- thingsiplay ( @thingsiplay@kbin.social ) 4•1 year ago
The Anti-Lag software from AMD seems to get flagged as some sort of cheating from the Anti Cheat software by Valve, as it tempers the Counter Strike code. In other words, its not compatible. AMD should have tested and worked together with Valve, before shipping the update. It’s not to blame Valve, because the Anti Cheat software works as intended, but AMD, because they did not work with Valve before launching their software.
- Midnitte ( @Midnitte@kbin.social ) 1•1 year ago
Anti-lag has been in the amd drivers for a long time. This seems more to be caused by Valve rushing CS2 out the door so the drivers couldn’t be thoroughly tested.
- conciselyverbose ( @conciselyverbose@kbin.social ) 2•1 year ago
No, it’s caused by AMD deciding hijacking CS’s execution was acceptable.
It’s more standard than standard that you can’t do that in a competitive game.
- Big P ( @peter@feddit.uk ) English1•1 year ago
I thought it was pretty well understood that if you modify game DLLs you get banned, why did they attempt to add this feature?