I'm a bit concerned as well if any other anti-cheat might detect Vulkan as a cheat somehow and get me perma-banned right off the bat...
I know BFV had some issues with that previously, never heard of or had this happen in any other previous title, really need some sort of dev answer on if this might be the case or not.
Linux players got banned because WINE announces itself as WINE.
Apex was running fine until they turned on EAC, Then you could start up Apex but Apex did not allow you to connect to any server because the "Wine Apex Module" could not be loaded.
You got a message but no ban.
I expect the same behaviour with BF2042.
If EA / DICE starts banning people for using WINE they are unfair.
Instead of banning a message "Unsupportet OS" should be sufficent.
The beta opens on linux, EAC does not complain!
Proton 6.3-7 is 'working' however, the game does give one error before opening.
"Detected Windows version 18362. The required Windows version is : 19041 or later. Please update Windows."
I'll be testing with the latest GloriousEggroll build when I have a moment, I'd assume this could be fixed with updating the prefix or something else in wine 🙂
Latest version of glorious eggroll didn't work, same 'error' the application does launch after closing it so it might not actually impede anything...
Anyone know how to spoof the windows build version in wine/proton?
Upon further investigation, while EAC does not complain, logs show it doesn't start properly either :/
What @ibk_xD said.
I don't think they're racing to make the BF launch, i think it's much more likely to be enabled closer to the steam deck launch.
That said, there's been a lot of incremental updates on the betas just in the last few months, so who knows.
Thanks for testing it out for the rest of us though!
Still no luck, I think EAC is definitely at fault here.... Logs don't look too good.
Also, not sure if I changed something or some sort of patch was pushed but I can't get this to open at all with the latest GE wine version, I seem to need to use a 32-bit prefix instead since origin needs to talk to steam in order to launch bf.exe.
Same thing as with Apex ... but ok its a beta i didnt expect the beta to run with "eac on" on my linux system.
Hopefully they enable it in the full game release.
Well I played for a minute before the EAC kick and it was butter smooth, hopefully we'll see EAC enabled for Proton before the Steam Deck launch.
Third paragraph, last sentence. (already posted by @Shotgun_Susan)
Aside from the SDK update, those "few clicks on the epic developer's portal" need to happen, so keep the thread alive until someone can confirm they'll either enable it or not.
If the SDK isn't updated yet though, that obviously doesn't help either.
Again thanks to those of you dabbling with this during the beta so the rest of us can take the plunge when it's "safe".
Well now we have confirmation of how the new EAC for Proton works, thanks to Brawlhalla devs that were the first to enable it.
BMGTom on Reddit:
The steps are to upgrade to EOS SDK 1.17 (released September 23rd) and then enable a client module for Linux. I suspect you'll see more games with support over the next few months, especially with Steam Deck being Linux based. Most developers have longer patch timelines than we do.
Hopefully we'll see this enabled for BF2042 in the future.
