Dive into the controversial start of "Battlefield 6" with this eye-opening video! As the early access beta kicks off, reports of cheating have surfaced, rais...
Valve is also barely a blip in the market when it comes to this, funny enough.
Valve’s data can be more or less officially pulled and steamdb lists them as having 1 million concurrents in whatever the default window is (looks like this month). Call of Duty claims to be closer to 70 million but most conservative estimates agree they are at least in the low 10s of millions of “active players” rather than anyone who just popped in to check their dailies to see if they wanted to do them.
Personally? I think the vast majority of games (including Battlefield…) would be perfectly fine with VAC and I like VAC. But there are reasons that the studios that make more money than some small nations on their games (as opposed to their storefront, which is what VAC actually is based on) literally pay for more invasive solutions.
I mean yeah, thats why I said longest lived, not ‘most popular’.
But I am glad you agree that… VAC is reasonable, and works pretty darn well.
But this leads into Part 2…
Why does VAC work pretty darn well?
Beyond the technicals of the methods of AC…
Because if you fuckup bad enough, your entire Steam Library can be deleted.
Steam is a platform.
Every single other major company that is trying to force Kernel AC on the PC market is acting as if they do, or should just also be the de facto platform, as they are on consoles.
Yep, cheat on Xbox or PS and your account can get banned there too… but a PC is more than a gaming console, has a lot more private stuff on it than one, typically.
Valve are PC natives so they never pushed for Kernel AC.
They just allow, and now warn you about Kernel AC from other mega publishers on their platform, and these other game publishers.
Their whole thing is that they want you to use their platform instead of Steam. They’ve pretty much all done it at this point, at least tried… Ubisoft, Rockstar, MSFT/GFWL, etc etc etc
And they want to force Kernel AC down your throat on your PC as well as consoles… because it gives them more data, which they can use themselves, and sell to data brokers.
… Anyway, the funniest part?
EAC and BattleEye have offered full support to game devs to get their AC working on linux via Proton… for 3 to 4 years now.
It comes with their licensing agreements.
But management almost never cares to tell development to actually use this support thst they are already paying for!
… Because they get lots of money from MSFT, and MSFT hates Linux.
Also, if you go on areweanticheatyet … you can see that almost every single AC system of any kind, in the last 10 years… has at least one game that showcases it working on Linux.
This means that it is provably, entirely possible to get nearly all AC systems working on Linux, as some game dev team has done this.
Its just that most game dev teams, under most management… are not directed to.
There is no real technical reason why AC cannot be made to work in a satisfactory way on Linux.
At best, it is dev/management laziness/nonprioritization, at worst, it is publishers not wanting to upset MSFT.
Valve is also barely a blip in the market when it comes to this, funny enough.
Valve’s data can be more or less officially pulled and steamdb lists them as having 1 million concurrents in whatever the default window is (looks like this month). Call of Duty claims to be closer to 70 million but most conservative estimates agree they are at least in the low 10s of millions of “active players” rather than anyone who just popped in to check their dailies to see if they wanted to do them.
Personally? I think the vast majority of games (including Battlefield…) would be perfectly fine with VAC and I like VAC. But there are reasons that the studios that make more money than some small nations on their games (as opposed to their storefront, which is what VAC actually is based on) literally pay for more invasive solutions.
To the first chunk:
I mean yeah, thats why I said longest lived, not ‘most popular’.
But I am glad you agree that… VAC is reasonable, and works pretty darn well.
But this leads into Part 2…
Why does VAC work pretty darn well?
Beyond the technicals of the methods of AC…
Because if you fuckup bad enough, your entire Steam Library can be deleted.
Steam is a platform.
Every single other major company that is trying to force Kernel AC on the PC market is acting as if they do, or should just also be the de facto platform, as they are on consoles.
Yep, cheat on Xbox or PS and your account can get banned there too… but a PC is more than a gaming console, has a lot more private stuff on it than one, typically.
Valve are PC natives so they never pushed for Kernel AC.
They just allow, and now warn you about Kernel AC from other mega publishers on their platform, and these other game publishers.
Their whole thing is that they want you to use their platform instead of Steam. They’ve pretty much all done it at this point, at least tried… Ubisoft, Rockstar, MSFT/GFWL, etc etc etc
And they want to force Kernel AC down your throat on your PC as well as consoles… because it gives them more data, which they can use themselves, and sell to data brokers.
… Anyway, the funniest part?
EAC and BattleEye have offered full support to game devs to get their AC working on linux via Proton… for 3 to 4 years now.
It comes with their licensing agreements.
But management almost never cares to tell development to actually use this support thst they are already paying for!
… Because they get lots of money from MSFT, and MSFT hates Linux.
Also, if you go on areweanticheatyet … you can see that almost every single AC system of any kind, in the last 10 years… has at least one game that showcases it working on Linux.
This means that it is provably, entirely possible to get nearly all AC systems working on Linux, as some game dev team has done this.
Its just that most game dev teams, under most management… are not directed to.
There is no real technical reason why AC cannot be made to work in a satisfactory way on Linux.
At best, it is dev/management laziness/nonprioritization, at worst, it is publishers not wanting to upset MSFT.