Compatibility Report

Hi @kisak-valve yes was using ntfs-3g with that drive. I have moved it to an ext4 drive and now the game starts up. It gives the same warning we saw with the open beta about windows version:

It does load into the game now, but gets stuck at the loading screen using constant 30% CPU usage. Adding the log:

steam-1517290.tar.gz

It keeps repeating 339.702:08f0:096c:fixme:keyboard:X11DRV_GetKeyboardLayout couldn't return keyboard layout for thread 08f4

Edit: Have tried resetting keyboard layout with sudo dpkg-reconfigure keyboard-configuration and restarting. As well as plugging in another keyboard. Neither have changed those errors looping forever.

Have also tried:

sudo dpkg-reconfigure locales
sudo update-locale LANG=en_US.UTF-8

Edit 2: Also seeing fixme:win:GetAltTabInfoW which doesn't look implemented at all https://github.com/wine-mirror/wine/blob/master/dlls/user32/misc.c#L195 that may be the cause?

I seem to be getting a new crash as of today:

Seems to be crashing like this at different times.

Attached the proton log here: steam-1517290.log.gz

I have moved it to an ext4 drive and now the game starts up

Please clean install the game if you moved it from NTFS to ext4. Also see if it happens without amdgpu-pro

@Evernow I have deleted and redownloaded the game. I am still getting stuck at the same point. However I also discovered I can cause it to error if I hit Alt+Enter or move the window.

steam-1517290.log

Using latest Proton Experimental

Edit: Have tried both amdgpu-pro drivers and latest mesa from oibaf 22.0~git2111150600.9d9de1~oibaf~f and get the same error as above, except the MESA one shows "6900 XT" instead of unknown card.

I have been playing this for a few days. It was running fine with the exception of online multiplayer booting you after a minute - probably EAC.
As of this morning even "solo" mode requires EAC to be functional. The only mode that is playable now is VIP Fiesta for some reason.

Have been able to avoid the "FindClosestMatchingMode" error by fullscreening immeadtly (Alt+Enter) when BF 2042 starts up. (Found that solution in an old EA fourm.)

I updated to bleeding-edge proton and latest mesa drivers. It still got stuck at the main screen, until I started frantically moving the mouse around in frustration and lo and behold...it slowly started turning darker and darker. So for some reason it needs a lot of mouse movement to progress past the splash screen on my system?

I was able to play through the demo conquest without issue on ultra settings. There were a few stutters starting out, but they quickly disappeared (better than BF4 currently is). Also tried doing single player and was instantly booted out after that, so until EAC is enabled for Linux, no point in trying more I guess.

Valve please ask them nicely to turn it on for us :smile:

when i start the game i get this

after that it will crash

here is my log:
https://gist.github.com/McMarius11/32d534f3af69595a92f28f59c1caa1f4

yeah valve is our only hope for EAC activation.

OS: Manjaro Linux
KERNEL: 5.10.85-1-MANJARO
CPU: Intel Core i5-7600K @ 3.80GHz
GPU: NVIDIA NVIDIA GeForce GTX 1070
GPU DRIVER: NVIDIA 495.46
RAM: 24 GB

Please valve go ask dice nicely to enable this for us. It's becoming a decent game now and I'd rlly want to play it on my Linux machine •́⁠ ⁠ ⁠‿⁠ ⁠,⁠•̀. Same issue happens, launches fine then kicks you out cause of eac

I tried running Battlefield 2042 with Proton Experimental Bleeding Edge but it gets stuck at the first screen (see image attached)

I can press Shift+F1 and the EA overlay is displayed. After some time the game closes automatically.

During the installation process, the installation of the EA client got stuck at the very end and I had to cancel it to make progress. I tried verifying the files and there was no error.

Since my last posting it does not even start up anymore. Please see the log attached.
steam-1517290.log

Replying to https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-1334485653

Same for me, game launches but getting stuck at the loading screen. The debug menu works (SHIFT + ^) and the frame counter shows something.

We are so close to having this game work on Linux with EAC.

Replying to https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-1383222349

After some time the game crashes with:

wine: Unhandled page fault on read access to 0000000048BF0020 at address 0000000142797D90 (thread 0890), starting debugger...

Using the following settings (GE-Proton7-35):

Same as @Af0x I tried to launch game but after start of Season 1 the game is crashing every time I try to run it, I'm using EA App launcher installed with help of Steam, Proton Experimental bleeding-edge. That's sad because even if DICE would enable Proton support game woudn't even launch.

Replying to https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-1408825161

if they enable support valves devs would fix it 100%

Replying to https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-1410160843

I would say support is enabled, as EAC is loading. Before they changed something you would not even get past EAC. This seems like some other weird bug.

Replying to https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-1410186843

Does it have the .so file? I haven't rlly looked lol

edit: it does not have the easyanticheat_x64.so file for it to work with proton

i remember when shatterline came out and it was using easyanticheat. it worked with proton but the devs didnt know about it and the version they were using was the wrong one. after a bunch of people asked they changed there version of eac and plopped the easyanticheat_x64.so to make it work with proton :)

https://github.com/HansKristian-Work/dxil-spirv/issues/134#issuecomment-1413157141
With this change to dxil-spirv the game appears to be displaying the menu, but it hangs after loading a map and a GPU_HANG message box appears (as described in https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-998338026).
Also, a message box with vkCreateComputePipelines assertion in winevulkan.dll is displayed 2 times during the loading process. I dismiss it each time using the Continue button.

P. S. You can copy the easyanticheat_x64.so from the Apex Legends installation if you have one.

When I go back to home I will try this, I didnt really heard about dxil-spirv, even if it loads into menu it's progress but with EAC, with .so file e.g. from Master Chief Collection is it even loading properley? As I know Proton support isn't enabled.

For me with the .so file from Apex now it gets stuck at the splash screen then chucks a error at me when using ge-proton7-48. hopefully and with more help we could get this working even if bf2042 doesn't support it

Proper fix is now available: https://github.com/HansKristian-Work/dxil-spirv/commit/9ef222ad3cb677c3e509cfda40de7ce477cdd78e.
I suggest trying the updated version of vkd3d-proton:
https://github.com/HansKristian-Work/vkd3d-proton/suites/10742817425/artifacts/538965379.

Proper fix is now available: HansKristian-Work/dxil-spirv@9ef222a. I suggest trying the updated version of vkd3d-proton: https://github.com/HansKristian-Work/vkd3d-proton/suites/10742817425/artifacts/538965379.

So is this game now working?

HansKristian-Work/dxil-spirv#134 (comment) With this change to dxil-spirv the game appears to be displaying the menu, but it hangs after loading a map and a GPU_HANG message box appears (as described in [#5305 (comment)](https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-998338026)). Also, a message box with vkCreateComputePipelines assertion in winevulkan.dll is displayed 2 times during the loading process. I dismiss it each time using the Continue button.

.

I have a subjective feeling that render thread(s) blocks on something, because sometimes I experience short hangs that don't result in the GPU_HANG message box, but once it appears, the image is not updated anymore at all and a crash dump is generated in %userprofile%\Documents\Battlefield 2042\CrashDumps.
P. S. I'm using proprietary nVidia Linux driver package version 515.57, I hope that's recent enough version to handle the latest vkd3d-proton.

I have far newer version of Nvidia driver on Arch I will return to home at Monday so I will write did it work.

it seems using the latest vkd3d-proton master it still gives a error on my amd card. ill post the crash logs when i can

backtrace.txt
heres the error i got using the latest proton experimental and latest vkd3d-proton master-9377ee1613267fdec0cf05e1b26347d0d50cad4c
idk if this will help but this was the error it gave me while sitting at the splash screen for a couple of minutes
This was on bottles using the ea app with a rx 6700

I get this crash if the game loading process gets stuck somehow (I assume). This happens sometimes for my setup, too. I just terminate BF2042.exe process if I see that the memory pool size doesn't grow during the loading. There are 2 kinds of this issue I experienced: when memory pool size is around 660 MB and around 2500 MB.

Also, it might be a good idea to remove the stored shader cache (stored in the %userprofile%\Documents\Battlefield 2042\cache directory) and vkd3d-proton.cache/vkd3d-proton.cache.write files in the game directory just to re-trigger shader compilation.

Oh! That's a new error. Using vkd3d-proton 2.7

Now changed just to Proton Experimental bleeding-edge and game starts, persists on splash screen like one minute with RAM usage at 2,7GB and then crashes. Tried like 15 times. Same RAM usage and same crash.

Specs:
CPU: Ryzen 5 3600
GPU: GTX 1660 Ti
Kernel: 6.1.9 linux
Drives: NVIDIA Proprietary 525.85.05
Proton: Proton Exp. bleeding-edge

I have exact problem. Only show splash screen and after some seconds crash.

Huge Game Crash Log: https://drive.google.com/file/d/1SnIYvnx12n4XIy83TRU5_RmaD7p-KQzN/view?usp=sharing

Specs:

CPU: I7-12700kf
GPU: AMD 6800XT
Driver: (Compatibility Profile) Mesa 22.3.4
Proton: Proton Exp

Guys next new error with latest NVIDIA driver 525.89.02

Right, apparently the nVidia driver is bugged at this point.
It fails here: https://github.com/HansKristian-Work/vkd3d-proton/blob/08909d98565065994612e529feb0cad04e498a8e/libs/vkd3d/state.c#L4682
so that return value of vkCreateGraphicsPipelines is completely random one that doesn't match any of those described in VK_RESULT enum.

Any update about this issue?

on the amd side i get a new error
backtrace.txt

Replying to https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-1448289868

Same as you with same Linux drivers, it's progress, that's good to see.

I don't think it's a progress. The game either hangs or crashes. IMHO the progress would look like game letting you to start a co-op/AI session at least.

trying the newest update with proton 8.0 i get a bunch of winevulkan errors then the same error where the game just halts on the splash screen before crashing :/

mine has the same problem

Replying to https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-1583007511

Can't fix it until dice allows proton to work with eac sadly which they don't seem to care about so..

Hello @pollux56, @JoaoVitoRoludo22, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. If you're using the Steam client beta, then please share Steam Runtime Diagnostics instead.

steam runtime diagnostics makes my desktop crash lol

https://gist.github.com/pollux56/63bac837fbfab4dc182ac269845b5e80

Hoped there would be improvements with the new season, but I see we're still at a standstill :(

Really hope EA will enable EAC someday (and that it is the only issue with the game on proton ...).

Hoped there would be improvements with the new season, but I see we're still at a standstill :(

Really hope EA will enable EAC someday (and that it is the only issue with the game on proton ...).

Iv opened quite a few issues on the ea forums but they don't care it seems. One community manager replied and said they had no plans at the time and that was over 8 months ago. I hope they relook into this as it's rlly simple enabling it but they have other important things like fixing recoil patterns on guns lol

Replying to [#5305 (comment)](https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-1583007511)

Can't fix it until dice allows proton to work with eac sadly which they don't seem to care about so..

The issue is not caused by EAC, but by incomplete or bugged vkd3d-proton implementation which creates bogus Spir-V shader binaries. The GPU driver just refuses to create graphics and/or compute pipeline with the set of shader blobs produced by it.

ok does this mean: we should be discussing this on a different issue to track over on another repo? {wine/proton?)

or it stays here?

I can say to you that with latest commit in dxil-spirv repo (https://github.com/HansKristian-Work/dxil-spirv/commit/5713a937560587f7dfe570e173fc4c07228e8787) BF2042 now works! I'm on latest nvidia driver version: 535.54.03 on arch linux kernel: 6.3.9.

I can say to you that with latest commit in dxil-spirv repo (HansKristian-Work/dxil-spirv@5713a93) BF2042 now works! I'm on latest nvidia driver version: 535.54.03 on arch linux kernel: 6.3.9.

Awesome, does multiplayer work too?

No they didn't enabled EAC support. Game kicks me after few seconds, with error that EAC authentication fails.

maybe to worth ask ea now however? (since the rest is ok to work)

how do you guys find best way to approach / reach out to those ea programming side developers?

maybe to worth ask ea now however? (since the rest is ok to work)

how do you guys find best way to approach / reach out to those ea programming side developers?

Everyone tried at EA Community Forums/Reddit/Twitter but they don't seem to care about it too much. You can search for it yourself on Answer HQ or here is link: https://answers.ea.com/t5/forums/searchpage/tab/message?advanced=false&allow_punctuation=false&filter=location&location=forum-board%3Abattlefield-2042-general-discussion-en&q=linux

I can say to you that with latest commit in dxil-spirv repo (HansKristian-Work/dxil-spirv@5713a93) BF2042 now works! I'm on latest nvidia driver version: 535.54.03 on arch linux kernel: 6.3.9.

Works for me as well. Thank you, @HansKristian-Work!

can confirm aswell that it is working on a amd card aswell!! only thing left is for dice to enable proton on eac :)

So now we have to attack DICE about turning on EAC.

I think what we really need is to make certain to reach the right key people within the DICE. And this is not really so much within our control as those other EA representatives who might carry forward the bug report / request to the right teams

Hard to say... but I would suggest to loot to those named representatives who presented in several of the prios BF new Season update videos. IDK

I have tweeted at them which are some that appear in those videos https://twitter.com/PolluxAU/status/1673471613487157248?t=m2WFgEhWOd-CCdSITmDGEA&s=19

Community manager responded to me this:

Hey [@Lobo6780],

The game has no official support for Linux or any other distro. The only official supported platforms for the game are Windows PC, Xbox and PS.

Thanks.

Community manager responded to me this:

Hey [@Lobo6780],

The game has no official support for Linux or any other distro. The only official supported platforms for the game are Windows PC, Xbox and PS.

Thanks.

Funny way to simply ignore the request and answer a question nobody asked. :middle_finger:

Community manager responded to me this:

Hey [@Lobo6780],

The game has no official support for Linux or any other distro. The only official supported platforms for the game are Windows PC, Xbox and PS.

Thanks.

@Lobo6780 can you link his reply here?

They just don't care about Linux gamers that are minority. If they won't enable EAC I will not buy next Battlefield and I offer you to do same thing.

Community manager responded to me this:
Hey [@Lobo6780],
The game has no official support for Linux or any other distro. The only official supported platforms for the game are Windows PC, Xbox and PS.
Thanks.

@Lobo6780 can you link his reply here?

Ofc here's link: https://answers.ea.com/t5/Technical-Issues/Battlefield-2042-Linux-EAC-support/m-p/12697479#M48937

Well I don't want to speculate too much but: on the one hand, there will be some people within EA who will assume or say they don't want to risk increasing cheaters. Because right now in 2042 all the cheating is gone away or under control. So that is a good situation. And certainly I myself don't want to encourage cheating either...

On the other hand EAC themselves has (on their official website) good simple guidance and support the necessary steps for how to enable EAC to be working well for both VMs and/or linux?

So overall my viewpoint is that developers for Battlefield (or their equivalent of whatever passes for a product manager these days)... that a sensible middle ground would be to quietly do a tryout. That is to say: don't publically admit or support fixing the EAC for linux. But instead just very quietly enable it on a trial bases. With no official support or anything like that. And then spend a few days / weeks monitoring how the online matches are going in terms of cheaters. If there is potentially any uptick or not. And depending (if there is an uptick). Then can still keep or widthold some option to silently take it away again.

Because (for sure) getting rid of cheating can and is in the scheme of things a higher priority not to spoil the gameplay. Than helping out the guys who are over on linux platform. And that is not necessarily a standpoint i disagree. It's just that EA is using a new and different anti cheat system now (than previously, which was the punkbuster one). So it needs to get over being too overly-cautious around such new AC system. And give the EAC a shot on linux. Perhaps EA might be thinking: ah well we need to try this on a different game somewhere else. And then pass the buck internally. But literally nobody wants to be waiting for that. Wheras silently switching it on, then being able to silently revoke that and switch back off. It just seems like the best way to make a step forwards. Without over committing too much that cannot be undone here.

Replying to https://github.com/ValveSoftware/Proton/issues/5305#issuecomment-1609440659

i understand your point of view but at the same time i dont. 1.4% of linux users do not usually cheat and cheats arent that popular in the linux realm. i dislike how companies think cheaters will increase by supporting linux as its not rlly true that could happen, they are using the same anticheat with the same reporting system so its not like anything would change in terms on banning people if linux players did cheat. hopefully it gets enabled tho as i just dont want windows installed anymore

i understand your point of view but at the same time i dont. 1.4% of linux users do not usually cheat and cheats arent that popular in the linux realm. i dislike how companies think cheaters will increase by supporting linux as its not rlly true that could happen, they are using the same anticheat with the same reporting system so its not like anything would change in terms on banning people if linux players did cheat. hopefully it gets enabled tho as i just dont want windows installed anymore

actually... completely agree with this viewpoint! 100%!!

it's more about how to respond to other people's concerns in a responsible fashion. to let demonstrate what EAC people themselves are saying, that their system should work (and also be effective on linux)

I kinda understand their point of view, because all anti-cheats on Windows works in kernel space (ring 0) so they can access every process on the system etc. but on Linux in Wine anti-cheats works in user space so technically we could write cheat to run as kernel module and circumvent anti-cheat? But that doesn't change anything regarding to that Respawn Entertaiment (one of EA studios) turned on EAC on Deck some time ago, and game works great.

https://twitter.com/PolluxAU/status/1686212913349148673?s=20

game still works and lets me into the game no issues but i still get kicked :(

https://twitter.com/PolluxAU/status/1686212913349148673?s=20

game still works and lets me into the game no issues but i still get kicked :(

Same thing((

everything works perfectly till EAC fail😞.

everything works perfectly till EAC fail😞.

until we ask, try to convince the bf2042 community manager that it's worth passing upwards / up the chain... to enable the EAC for linux!!!

everything works perfectly till EAC fail😞.

until we ask, try to convince the bf2042 community manager that it's worth passing upwards / up the chain... to enable the EAC for linux!!!

Iv already asked one of the lead devs in bf on the battlefield stream they did like 2 weeks ago and they simply said no.
I even said proton and they knew what I was talking about so I was very disappointed :(

We can keep asking tho until they give in lol

Like what everybody else said and me, the game works wonderfully but the anticheat is the only thing stopping you from playing public matches and can be enabled super easily on eac so there is simply no excuse to not enable it

I'll ask totalfps to see what he thinks lol

edit: he didnt reply :/

Yup, same here it works perfectly and seems to run as good as all older Battlefield titles run on Linux. The best way is to ask in a civilized way in this forum post.

I'd love if they at least would do a trail for maybe 4 weeks to see how bad things go when they enable Linux support. That'd at least allow gamers (on Linux) to officially prove their interest and give them metrics on how evil people are.

Even though the Linux user-base is small, considering the Steam Deck and maybe soon a refreshed, much more powerful version, would provide quite some potential to gain new players.

EA is transitioning to EA Anti Cheat for BF2042 with season 6.

https://www.ea.com/en-gb/games/battlefield/battlefield-2042/news/eaac-and-battlefield-2042
https://www.ea.com/security/news/eaac-deep-dive

All hope is lost for this game on Linux.

They ruined the series anyway. So no real loss

just updated and the game eabackgroundserv just sits in the background while nothing comes up, i hope ea and valve create a agreement on the anticheat as i would still like to play the game time and time again

here is a proton log if anyone wants to read whats happening
https://drive.google.com/file/d/1gF9uBZ0NH7mvjrtZlxUGeo24a-miQQGP/view?usp=sharing

Wine is no supported message

steam-1517290first.log
steam-1517290.log

Wine is no supported message

steam-1517290first.log
steam-1517290.log

Yep the kernel level anticheat they added made it not work completely, doubt it will ever be supported through proton

Sad EA doesn't prioritize this...