protonscr

FragPunk

protonopen appid 2943650Game compatibility - Unofficial
ValveSoftware/Proton#8503 · opened 2025-03-07 by pollux78 · updated 2025-08-21 · 31 comments · github · game page · search this game
2 matching comments, n / p to jump
Ppollux78 2025-03-07 github

Compatibility Report

  • Name of the game with compatibility issues:Fragpunk
  • Steam AppID of the game:2943650

System Information

I confirm:

  • [ ✅] that I haven't found an existing compatibility report for this game.
  • [ ✅] that I have checked whether there are updates for my system available.

steam-2943650.log

Symptoms

Play the game for long enough and it will crash on you, sometimes plasmashell will crash also with it which requires a restart, im using dx12/vkd3d also not dx11/dxvk

Reproduction

Play the game under dx12 and it will crash on you after playing long enough, like for me it took around a hour to happen

The game also likes to lose its cursor under dx11 sometimes which started happening after 5 hours of playing

?ghost 2025-03-07 github

well it does not even launch for me

Ppxlsec 2025-03-07 github

well it does not even launch for me

It initially didn't work for me either, but was fine after I restarted steam.

Play the game under dx12 and it will crash on you after playing long enough

+1


I would also like to add that the game is unplayable without gamescope for me, it really does not want to capture my cursor unless i make fast movements for some reason (Hyprland).

GPU: RX 7900 xtx 24GB
Video driver version: mesa 25.0.1-2
Kernel version: 6.13.5-2-cachyos
Proton version: proton-cachyos 1:9.0.20250227-1

Sswapnanil1 2025-03-08 github

It Launches for me and is kinda playable
The fps drops to 30-50 when on card selection screen appears (U need to select between 3 cards before starting a match)
It takes some time to get back to 141 fps (I locked it at that)
I'm on low setting with DX11 , Its just stutters when switching between in-game and Menu UI stuff

GPU: RX 570 4GB
Linux Mint 21.2
Video driver version: mesa 25.0.1
Kernel version: 6.13.6-Xanmod
Proton version: Proton-GE 25 (Offical Proton Version dont work)

Ffrozen-sea 2025-03-08 github

Game defaulted to DX12 mode and ran great, but I was getting "network disconnect" popups in game and when pressing ok on that it would close and show a crash reporter. Happened about once every 20-30 minutes, literally no signs of actual network issues. Switched to DX11 adn was able to play 2 hours straight without issues.

GPU: RTX 4070 Ti
Video driver version: 570.124.04
Kernel version: 6.13.5-2-cachyos
Proton version: bleeding-edge

FFloVito 2025-03-09 github

Game worked out of the box for me on Garuda KDE using DX11 because I switched to it immediately. I somehow knew id have issues with DX12. No crashes or any of that sort but the mouse cursor escaping the game window is something that happens constantly. Couldn't find a fix for the mouse except restarting the game and praying to proton.

GPU: RX 6700XT
Video driver version: 24.3.4
Kernel version: 6.13.5-zen
Proton version: Experimental and Hotfix

Ppollux78 2025-03-09 github

Replying to https://github.com/ValveSoftware/Proton/issues/8503#issuecomment-2708776603

It wasn't happening in gnome so maybe this is something KDE plasma needs to fix? I could open a bug report there also to see what they say

Ppxlsec 2025-03-09 github

Replying to https://github.com/ValveSoftware/Proton/issues/8503#issuecomment-2708820424

Behavior is also present for me on Hyprland, the game does not grab the cursor at all. On top of that the camera doesn't move unless the cursor is rammed into the edge of the monitor.

Here is a quick demo: https://youtu.be/hsV5uLKmQhQ

Qq4niel 2025-03-09 github

Replying to https://github.com/ValveSoftware/Proton/issues/8503#issuecomment-2708836032

Running the game with these launch commands solves the cursor issue for me. Of course, replace the resolution and refresh rate with your own.

Steam Launch Options: gamescope -ef -W 3440 -H 1440 -r 144 —force-grab-cursor — %command%

Ppxlsec 2025-03-09 github

Running the game with these launch commands solves the cursor issue for me. Of course, replace the resolution and refresh rate with your own.

Steam Launch Options: gamescope -ef -W 3440 -H 1440 -r 144 —force-grab-cursor — %command%

This is true, and during the beta this was my go to. But gamescope has once again broke for me and i only get a black screen after the anticheat.
Also mouse movements feel off in gamescope compared to just proton so i really don't like using it.

?ghost 2025-03-09 github

well it does not even launch for me

fixed it by removing game mode. i do not need game scope, cursor works fine.

Ppxlsec 2025-03-12 github

This is true, and during the beta this was my go to. But gamescope has once again broke for me and i only get a black screen after the anticheat.
Also mouse movements feel off in gamescope compared to just proton so i really don't like using it.

Found a fix for the black screen issue on gamescope. I think it's related to gamescope rendering the "privacy policy" window when starting the game. https://www.reddit.com/r/SteamDeck/comments/1j5jpiy/how_to_fix_fragpunks_black_screen_on_steam_deck/

TLDR: If you get a black screen after the anticheat in gamescope, start the without gamescope and accept the policy; then restart the game with gamescope and it should be fine. No clue what causes the privacy policy to reappear however.

33a33d 2025-03-18 github

Having an issue where I'll need to restart after 2-3 games, if not, my mouse will start to "de-sync" and it'll have a delayed turn/move animation. Basically, my game will have delayed mouse input by about 1-2 seconds.

GPU: 4090 24GB
Video driver version: NVIDIA Driver Version: 570.124.04
Kernel version: 6.13.6-arch1-1
Proton version: Experimental

Bbarbiefan 2025-03-26 github

Nvidia 3060 12GB
Arch
kernel 6.13.8.arch1-1
Hyprland 0.48.0-1
nvidia-dkms 570.133.07-1
proton experimental bleeding-edge

cursor in menus is fine, however when controlling a camera game locks cursor to the game window, but only registers movement on screen edges (window edges)

Ssimifor 2025-03-26 github

on kde plasma wayland and xorg I didn't get any mouse issues, have you tried if those issues happen outside hyprland?

Tterm1n4l 2025-03-30 github

proton experimental (bleeding edge) loads of stuttering in game after 3-4 matches

SSpeculate7348 2025-04-06 github

I have the same issue.

Ssimifor 2025-04-06 github

Those having performance issues over time, could you try changing your launch parameter to this and seeing if you still get the same issue? LD_PRELOAD="" %command%

Oopensourcecheemsburgers 2025-05-05 github

This is still an issue on the latest hyprland-git.

I have tried:

  • Changing all Hyprland configuration variables related to cursors and warping.
  • Using gamescope -ef --force-grab-cursor --backend sdl.
  • Installing the latest proton-tkg and setting DISPLAY= to force native Wayland. Runs perfect but still has the cursor bug.

This bug is consistent on XWayland, Gamescope, and native Wayland. The common denominator is Hyprland.

Tterm1n4l 2025-05-06 github

Those having performance issues over time, could you try changing your launch parameter to this and seeing if you still get the same issue? LD_PRELOAD="" %command%

I haven't had any issues with stuttering in fragpunk since using LD_PRELOAD="" in my launch params

Ppollux78 2025-05-30 github

Fragpunk now launches with just a neacinterface window error and then its a black screen, doesn't go any further.

Image

fragpunk issue.log

Cachyos, Kernel 6.15, Mesa 25.1.1, Proton Experimental

EDIT: Fixed

Bbarbiefan 2025-05-30 github

Arch 6.14.6-arch1-1, any proton version
Same issue, not getting past Initialization error 1

neacinterface

not this again...

Bbarbiefan 2025-05-31 github

They fixed it
no AC issues as of 31.05

Sswapnanil1 2025-05-31 github

Even though as a product FragPunk is new and microtransaction-heavy, I do respect the devs for silently supporting Linux. Hope the game gains more popularity and they openly show support for it.

Tterm1n4l 2025-07-08 github

After latest update, game is crashing either on login or during round load or once you try to move in round. I am running in wayland, but I tried using QT_QPA_PLATFORM=xcb and even tried PROTON_HIDE_NVIDIA_GPU=1 to see if this would resolve but issue remains. tried verifying files as well, but no joy. LD_PRELOAD="" and PROTON_ENABLE_NVAPI=1 also did nothing.

HHiredSaint 2025-07-09 github

This exactly, tried any proton version etc.

Bbinboupan 2025-07-10 github

Log is attached, I suspect it has something to do with the anti-cheat system.

steam-2943650.log

DDarksh21 2025-08-03 github

The games works using proton 6.3-8 version but with visual glitches, perhaps it can be fixed for other versions?

Bbonkmaykr 2025-08-04 github

The games works using proton 6.3-8 version but with visual glitches, perhaps it can be fixed for other versions?

I suppose this rules out it being anticheat related?

Tterm1n4l 2025-08-06 github

steam-2943650.log
it also works on 7.0-6 (and ge-7-55), I had to force -dx11 and I had to set STEAMDECK=1, and it wasn't very stable, but it's still a better experience than 6.3-8 (which doesn't work for me at all). I have attached my steam proton log

HHarmonyHana 2025-08-20 github

Been trying to get this to work in any way for the last few days, no proton version works, including the newest beta
i can get the game launched for maybe 10 seconds at most, at a low resolution, before a crash
Things ive tried.
proton 6.3, proton 10.0(Beta),proton hotfix, proton experimental, proton 9, Proton-GE-RSTP
-dx11, STEAMDECK=1,
verified files, reinstalled game, factory reset of OS,
i've tried both a 4070 as well as a 9070xt
of course, updated system as well as GPU drivers for both of those cards
without any further direction, im at the limit of my technical know how on what i can try to help further

steam-2943650.log
if at all useful, a long list of "81332.788:01a4:01a8:err:sync:RtlLeaveCriticalSection section 000006F6E60B6DD8 (null) is not acquired" lines right before exception backtrace. ( Line 15498 )

Tterm1n4l 2025-08-21 github

latest update looks like it has fixed the game was able to play a full match on proton experimental (bleeding edge)

Proton versions

Launch options

Launch lines