Compatibility Report

Here's an update:

• Installed the msacm32.dll through protontricks
• Ran the EAC installer again
• Try and run the game, The EAC launcher starts properly
• After that, a fatal error appears stating "Failed to load il2cpp"
• Verified game files to reset install script
• Tried to run the game again, "Failed to load il2cpp" pops up again

Looking online I assume something isn't right with the mono install.

• Uninstall game, install it again
• Do same thing, same issue

Hello, I have a similar problem, but don't have any dll Initialization issues:

System Information

• GPU: RX 7900 XTX
• Video driver version: mesa 23.1.6 and mesa 23.3_devel.177172 (both tested)
• Kernel version: 6.5.0 and 6.4.11 (both tested)
• Link to full system information report as Gist: https://gist.github.com/YourSandwich/f4f6a0f28553c0db6a8f4530f9ecb0b4
• Proton version: Proton Experimental, Proton 8.0-3, Proton GE 8-13

I confirm:

• [x] that I have checked whether there are updates for my system available.

steam-671860.log

Symptoms

Since Update 2.1.1 the game is crashing after the Unity Logo appears on game start.
I have reinstalled the game and deleted the proton prefix. Also disabled mangohud and gamemode.

I am running ArchLinux with the latest updates "Thu 2023-08-31 20:40:48 UTC"
DE: KDE Plasma + Pipewire 0.3.78 + X11

Yesterday the game worked flawlessly, I have done system and mesa updates since then but rolling back did not change the result.

Reproduction

1. Start the game on KDE X11

I also tried Wayland and it did not work. Then I run it on my steamdeck and it worked.

Tried gamescope like this gamescope -W 800 -H 600 -f -- %command% and this fixed the issue. So I assume maybe the game does not like my native resolution.

I tried again using gamescope -W 3440 -H 1440 -f -- %command% reverted to 800x600 and it stopped working as well

Reinstalled the game, tried it again, did gamescope -W 3440 -H 1440 -f -- %command% change the settings to Maximized Window and Custom Resolution. Closed the Game and removed gamescope.

Now it works again.

I have a more extreme version of the game crash after the unity screen under x11 using proton experimental. For me, the entire system hangs.

Game launches (and plays) fine under Wayland though, or if I use proton 7/8.

I left the system "hung" whilst I went to do other things and turns out the system isn't actually completely hanging, the whole system is just coming to an absolute crawl (alt+tab unresponsive etc) with the game running a ~60s/frame.

If I alt+tab and wait long enough, the game does reach the menu and appear to be running at a normal fps in the background, but the entire system chugs again as soon as I switch focus back to the game.

I also realized it's something to do with one of my screens being disabled in xrandr . If I re-enable my second monitor, the game launches and runs normally. Very strange.

There's a fairly annoying bug that I've encountered myself on multiple proton versions and seen a few times on protondb where framerate drops to around 10fps for a few seconds roughly once a match. Anyone else seen this?

kernal: 6.2.0-33-generic #33~22.04.1-Ubuntu
Nvidia 1650 Ti Mobile - driver version 535.113.01-0ubuntu0.22.04.1

Proton versions:

• 8.0-3 - Drop after EAC launch
• Experimental - Drop after EAC launch
• 7.0-6 - Works fine

It's a little surprising to me that with the new versions of Proton, some games lose compatibility.
Some older games work fine on 8.0-3, but some that completely surprise such behavior for some reason do not work.

I'm getting a similar event. The game launches but but never opens. It was working just a few days ago. I tried experimental, 804, and 706 proton which have different failure points in the log. Artix Linux AMD X11 KDE

Attached is log from experimental failure using PROTON_LOG=1 %command%
steam-671860.log

FYI: I still have that issue, and the game does not launch with Gamescope anymore.
But when I try to use gamescope and then remove the launch option again, then the games starts magically again.

@kisak-valve > Hello @Alex9001, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

here is gist from steam runtime

https://gist.github.com/Alex9001/0f1f16cdd9deb8690eb6c318e381b630

Thank you I can play battlebits again after installing a bunch of packages.

the game just hangs on a splashscreen (loops through the animation, doesn't freeze).
screenshot:

here's my system: https://gist.github.com/k1gen/9c2d5579b5f64770cf79e04e1f2cc426. I use GE-Proton8-25 everywhere, but with Proton Experimental and 8.0-4 the issue is the same. I remeber the game working in August-September. I also use these launch options: env -u SDL_VIDEODRIVER %command%, because without them after I press Play, I get an error window from EAC saying "Failed to initialize dependencies". I have the Proton EasyAntiCheat Runtime installed it before trying to launch the game itself (). Steam was installed with pacman, and doesn't use sandboxing stuff like firejail (which I first thought to be the culprit)

I don't understand why, but I built the 6.6.2 kernel with the usual olddefconfig and now the game works on Steam Proton 8 and GE-Proton8-25

I checked for the 6.2.0-37-generic kernel and it also works (it used to crash), apparently there was some kind of related game update

for my friend on fedora 39 it works just fine even without the launch options tinkering. for me on arch it doesn't work no matter what I try

I have 3 other Arch Guys for which the game also works flawlessly. It could be something specific like the GPU Models or whatever. We are all running kernel 6.6.2 and stable mesa on x11.

I have an RX 7900xtx

The others have RX 580 and RX 6700.

I have just switched to GE-Proton8-25 that has fixed it for me, at least for now. While switching to the wine version, I noticed that steam loaded my default prefix at ~/.wine instead of the steam prefix.

I suspect it's more of an EAC issue than BattleBit issue then

In the main menu it says that EAC is not installed. If I launch a separate application via EAC, it asks me to launch Steam....
In playtest/early start all works perfectly, but now I haven't been able to play for a couple of months.

I'm seeing black squares in the lower third of my screen.

Using an amd card with latest fedora.

the game just hangs on a splashscreen

the issue is still relevant for me, after updating the game to 2.2.2 and the kernel to 6.6.4

Game doesn't work on void linux.This is what I see after starting the game and connecting to the master server:
Make sure you have installed EasyAntiCheat and run the game with it.

Judging by the game logs, the anti-cheat is launched and working. There are service logs and something else incomprehensible about the progress of downloading something from the Internet. But no errors.
I tried installing Steam EasyCheat Runtime. Did "Install & Repair EAC". I tried installing vcredist in perfix. This does not affect the result in any way.

The only way I could play was to install Steam through a flatpak.

https://github.com/ValveSoftware/Proton/issues/7041#issuecomment-1830992541
this is still relevant

Game loads up for me and works great, until I try and load into a server, and then I get kicked by Anti-Cheat :/

My son and I are both running Arch Linux, and it works fine for him, but it boots me. We're both running Arch + i3.

Only difference is the GPU. We're both on AMD CPUs, but he's running an NVIDIA GPU, and I'm on AMD.

@Swivelgames try steam flatpak version. I have AMD ATI Radeon 680M(Integrated GPU) and game work well.

@Jipok That shouldn't have any correlation. My son is using an almost identical setup of Arch and isn't having issues. I also don't have flatpak installed, and would really like to avoid it if possible. I have tons of games already installed using the normal version of Steam and they work just fine.

I'd just like to note that on the Nobara Linux 39, Ryzen 5 5600x + 6600xt + 16gb of RAM and 1tb NVMe, running the latest 6.7.x kernel at the time yesterday, the game loads up fine and I'm able to select a class and everything from the menu, but the second I spawn my mouse is unusable.

Proton 8.0-5 exhibited the same issues, as did Proton 9.0 beta. Proton Experimental as well.

The only way I was able to actually use my mouse in-game after spawning was to switch to the slightly older GE-Proton-8-32 version. I'll be sticking with that until I see people say otherwise.

I am able to load and play the game, however, framerates when joining a server are terrible, between 20-30 FPS, and if I am not looking straight down, its even worse.

I did some tweaking, different versions and the like, and I was able to get it to run decently... for a time, it would seemingly randomly return to this low FPS state, and the only way it would recover is restarting the game.

I added PROTON_HIDE_NVIDIA_GPU=1 %command% as a launch option, and this did not prevent the random FPS drop, but it did allow the game to eventually recover FPS after some time of play.

I am currently running
KUbuntu 24.04 LTS
Proton-9.0-2
AMD 5900X
RTX 3090
nvidia-drivers-555 (Proprietary, stable)

In case it helps, I believe the frame-rate drop is due to the cpu hitting 100% load when processing destroyed buildings, not due to a graphical issue. mangohud shows 100% cpu load across all cores during the framedrops, and typically only during the first destroyed building of the game being open.

I can confirm it now works without issue for me. Unsure about the others problems however, if no other issues I would consider this closed.

I can confirm it now works without issue for me.

+1

I posted in #7721 and #1651 that I found (with the help of someone in the GZW Discord) an old workaround that Star Citizen lug-helper left over in my /etc/hosts. Commenting out or removing this line out in my /etc/hosts fixed the NullClient issue:

127.0.0.1	modules-cdn.eac-prod.on.epicgames.com #Star Citizen EAC workaround

Now EAC can communicate with the EAC servers again, instead of been looped back. 👍

The game kicked me because of EAC the last weeks. No proton version worked till now: proton_tkg_experimental.bleeding.edge.9.0.142850.20241213 installed via ProtonUp-Qt

with other proton versions today I couldn't launch the game because it couldn't download a packaged and thus can't connect to the master server. The bleeding edge proton version fixed that too. Sound is buggy and PULSE_LATENCY_MSEC=90 will result in a crash. But no errors and no EAC kicks anymore :)

Just wanna bring this back up because I am getting a major memory leak now. Not sure if it's the game or proton

Here's my sys info from steam runtime https://gist.github.com/Eris7090/fa016845a0bfaddbf9e0cee0d9613a75

I got the same memory leak issue. Loaded the game, took up all 32gb of ram I have, then OOMed and crashed. Haven't been able to load it since. Just says running on steam and then stops. Have restarted my system multiple times and also switched from hyprland to KDE, to no avail. Running on Wayland.

Game stopped to work after "Linux Runtime 4" and "Proton Hotfix" update. Most likely related to EAC, re-installation of EAC did not help. Using of "experimental" , "9" and "8" did also not help.
History: After the Linux Runtime 4 was installed, I had to switch from "experimental" to "hotfix" to make it work.
Worked flawlessly before these updates.

Workflow was always:

1. switch to proton version x
2. check files
3. re-install EAC
4. try to run game

No suspicious log entries (even none with PROTON_LOG), it just hangs in the splash screen after reaching 100% initialization state.

Runtime diagnostics: gist

Update: It works now with Proton 9.0-4