UnsupportedShow Details
Unknown
Frequent crashes
Window would open around 5 minutes into playing. If clicked "ok" it would crash the game. If clicked off the window you would get an extra 2-3 minutes if gameplay before the game crashes by itself.
-dx11
crashes at the end of every round
gamemoderun %command%
Lots of Low-Level errors and Fatal errors
-dx11
I get stable ~115 FPS with rare drops to ~70. All settings are maximum, FSR on quality.
After enabling -dx11, the game stopped crashing. Everything is great, I recommend it!
Playable but crashes around the 15 - 20 minute mark.
Consistently crashed after around 15 minutes of playing with the message "A fatal error has occured"
With DX11, the game is very much playable, maybe a bit less performances than on windows
%command% -dx11
without DX11, it crashes randomly
-dx11
Was getting fatal error pop up which can be ignored for some time but eventually the game crashes. Played a few matches just now with -dx11 as the steam launch option and it seems stable :)
20-30fps at very low settings and fsr set to ultra performance, fsr frame gen is optional but ideal
-dx11
YOU MUST LOWER SETTINGS, you will get maybe 20-30fps at 15 watts
-dx11
need to add -dx11
I cant recomend this game in its current state because of the lack of optimisation and the fact that FPS is unstable
%command% -dx11
max 24FPS when playing game , lowering resolution and quality had no impact
It always just popped up a little window saying "Fatal Error". Steam discussion page posts report problems too.
Tested various proton versions and launch command options
Judging from the variety of reports, this seems highly unstable. Even if it works now it may stop working soon.
Not worth buying at the moment
Crashes a ton. I haven't been able to complete a game yet.
-dx11
crashes every few minutes, unplayable after updates
gamemoderun %command% -dx11
Game crashes after 5 minutes without -dx11
gamemoderun mangohud %command% -dx11
I use dvorak and I can't configure O to walk backwards. This bug is also present in windows. I use lutris to set qwerty layout in this game only.
-dx11 argument is necessary to avoid crashes. In Tumbleweed map linux performs even better than windows 10~ fps more. In the rest of the maps I have ~12-3 fps less than in windows.
Just Change or Make Control Layout
cant see any progress after launching the game again after a crash
crashes after 5-10 minutes of gameplay
Mouse occasionally will lose focus, can be fixed with a simple click.
The game will crash/close after about ten minutes. No error message or logs.
I truly hope that the anticheat isn't to blame, it would be quite a loss if this game no longer works on Linux.
%command%/Binaries/Win64/Bodycam-Win64-Shipping.exe
Crashing with LowLevelFatalError
Full Error Message: LowLevelFatalError [File:D:\build++UE5\Sync\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 954] Rendering thread exception: LowLevelFatalError [File:D:\build++UE5\Sync\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 341] Direct3DDevice->CreateTexture2D(TextureDesc,SubResourceData,OutTexture2D) failed with error E_INVALIDARG at D:\build++UE5\Sync\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Texture.cpp:323 Size=1000x1000x1 PF=2 Format=DXGI_FORMAT_B8G8R8A8_UNORM(0x00000057), NumMips=1, Flags=D3D11_BIND_RENDER_TARGET D3D11_BIND_SHADER_RESOURCE , Usage:0x0, CPUFlags:0x0, MiscFlags:0x2, SampleCount:0x1, SampleQuality:0x0, SubresPtr:0x0000000000000000, SubresPitch:0, SubresSlicePitch:0
0x00000001428cf2f0 Bodycam-Win64-Shipping.exe!UnknownFunction [] 0x00000001428b5ab0 Bodycam-Win64-Shipping.exe!UnknownFunction [] 0x00000001428c34fe Bodycam-Win64-Shipping.exe!UnknownFunction [] 0x0
No issues with performance before crashes. When it crashes, it crashes instantly to desktop. Tested Proton 9 and Experimental. Same results for both.
%command%/Binaries/Win64/Bodycam-Win64-Shipping.exe
some of the audio was echoing when starting the game in the main menu but relaunching fixed the issue.
was able to play a few matches initially without issue and then the game crashed to desktop without an error message. Ever since the first crash to desktop, the game has crashed consistently since every time now.
Game performs great and the gameplay is amazing but now getting consistent crashes to desktop without an error message after playing a match for a few minutes.
OBS_VKCAPTURE=1 gamemoderun mangohud %command%/Binaries/Win64/Bodycam-Win64-Shipping.exe
Set global illumination setting to LOW to avoid rubberbanding, other than that it runs pretty well out of the box
Started the game, main menu worked for 3 minutes. Game crashed, now shows a black screen everytime i launch it.
Indie devs and linux support dont mix well.
In the menu screen its completely fine but when loaded into a map, it runs terribly
If you really want to play this game, use Windows.
No walls
%command%/Binaries/Win64/Bodycam-Win64-Shipping.exe
When starting a game a lot of things won't render like walls. I also see a lot of artifacting. This makes the game unplayable. no combination of changeing the setings changes these problems.
Opens into wine's default file explorer
Probably a way to fix it using protontricks, can't be bothered figuring it out. I am not technical enough to understand what I am doing.
Really good experience. Now i have a reason to buy a better GPU.
Running on GTX1080 overclocked, the game runs anywhere from 30 to 70fps depending on the map on low settings. Low settings means visible pixels sometimes
The menu is broken (no ui only background) after trying to exit the store or some other menus. This is fixed with a restart. Otherwise it is the same bugs as on windows...
Runs great! At the moment you have to select the game exe from the binary folder on start for it to launch...
I didn't do anything special and it just works for me. It does open the wine file explorer and I have to click the Bodycam.exe but otherwise it seems fine.
%command%/Binaries/Win64/Bodycam-Win64-Shipping.exe
The Multiplayer works well. Without changing the launch arguments, it will launch wine file explorer where you have to double click the exe. However with these launch arguments, the exe will launch properly.
the game itself works flawlessly out of the box, once you've launched it
when launching from steam only a file explorer window opens where you have to navigate to the .exe and run it manually
You have to click the executable manually
The only issue is that steam opens the wine explorer, so you gotta go the the above folder and double tab on the game exe
Works! the wine explorer thing initially stopped me, but thanks to the people on protondb i was able to play and enjoy it
The online function does not work completely; you can host games yourself, but no one can join.
When starting the game, you need to find and launch the game executable (exe) in the Win64 folder yourself. If you start the game via Steam, a window manager will appear after a while. There, you need to find the exe file and double-click it.
The game can be launched under Pop!_OS, but an issue occurs where only a window manager appears on startup. In the window manager, you need to navigate to the Win64 folder, find the game executable, and double-click it. After doing this, the game starts without problems. I play with the highest settings, and the game runs very smoothly without any lags. However, I can only host games and cannot join any.
Game was only playable once, crashed, and now displays a black screen then proceeds to crash after 120 seconds.
I had to manually execute the .exe file. When you press play on Steam, a WINE files popup window will appear and nothing else happens unless you select the game's .exe in the binaries folder.
Issues seem unrelated to my system: my Framework laptop 16 (AMD CPU & GPU, Arch KDE Wayland) suffers from the same issues.
