Vac bans mean you can’t play on vac secured servers. Nothing happens to your other games. For a competitive multiplayer game some anticheat detection is wanted. People changing their dll’s to gain a competitive advantage is cheating. AMD making and distributing this unintentional cheat doesn’t change that.
I agree that buying directly or through GoG and backing up your games is the best thing to do. But this incident isn’t really related to that.
Sure, my comment is directly aimed at a comment stating Valve would basically brick your steam account for this, though. It’s disinformation I’ve seen at too many places this week or oddly enough. While Valve as the CS2 publisher preemptively told players they would unban people once their dlls were normal again.
I loved BG2 and it was one of my favourite games ever for a very long time. Though when I read the old BG sub on Reddit it seems people there disliked everything I loved and hyperfocused on things I just considered part of the vehicle to deliver an amazing story that allowed so much freedom and depth that made you feel emotional and connected. I had tried to replay BG2 but the mechanics are so, so outdated now and distracting.
BG3 over delivers on the choice depth, story and connection but does so with an updated, fun and much better engine with much more mechanics.
Valve is now reversing VAC bans due to AMD drivers in CS2, according to patch notes (store.steampowered.com) angielski
Recently there was a thing where VAC would erroneously flag AMD’s antilag+ feature as cheating, and issue a ban....
'We owe them a huge debt': Baldur's Gate 3 lead writer hopes they did '90s BioWare proud (www.pcgamer.com) angielski