protonscr

FBC: Firebreak

protonopen appid 2272540Game compatibility - Unofficial
ValveSoftware/Proton#8829 · opened 2025-06-19 by Athanasius · updated 2026-07-29 · 6 comments · github · game page · search this game
1 matching comments, n / p to jump
AAthanasius 2025-06-19 github

Compatibility Report

  • Name of the game with compatibility issues: FBC: Firebreak
  • Steam AppID of the game: 2272540

System Information

I confirm:

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

Symptoms

The game does actually run, but there's some sort of memory leak. It starts at a little under 4GiB for the affected process, and then during a Job (mission) it gradually increases, ending on around 8 GiB, a small dip between Jobs, and then by the end of the second Job it increases to around 13GiB, and during the third it reached as high as 18 GiB, and then the OOM killer kicked in and took the game down.

Graph of the 'RSS' value for the process: https://miggy.org/games/FBC-Firebreak/firebreak-linux-memory-usage.png

This does not happen in Windows 11 Pro. Memory usage doesn't even hit 8 GiB. Same graphical settings, that's with nvidia drivers 576.80. Obviously it could still be a game bug, but this points more at Proton, or supporting libraries.

Reproduction

Happens every time I play in Linux.

AAthanasius 2025-06-20 github

The game fails to fully start under Proton Experimental 1749849620 experimental-10.0-20250612c.

It starts playing the initial splash screen then crashes. I sent the crash report.

AAthanasius 2025-06-20 github

I tried GE-Proton10-4 (by unarchiving it in compatibilittools.d), and that also seems to exhibit this memory leak, but perhaps slower. Not had chance to do back to back Level 3 Jobs yet to recreate the same circumstances.

AAthanasius 2025-07-05 github

Memory leak still happening with GE-Proton10-8, maybe slower than that graph, but the game got OOM-killered again.

Also memory use was up to 18GiB by the end of 3 Jobs using Proton 9.0-4.

This is with nvidia drivers 575.64.03 now.

I know others on Linux running this game don't have the issue, so presumably there's some setting or hardware/drivers difference tickling it in my case.

Llostdharma 2026-01-26 github

Same here. The game eventually crashes after few hours of playing.

Bazzite 43
Proton Experimental
GeForce RTX 3070
Driver: 590.48.01
Linux: 6.17.7-ba25

Ttbeest 2026-04-13 github

For what it's worth: I was having performance issues, even on the lowest settings, on Proton Experimental and proton-cachyos-10.0-20260407, but Proton 9.0-4 seems to work fine for me.

Nope, something is still wrong. It maxes out my VRAM after a while, not so much my system RAM.

Linux 6.19.12-1-cachyos
Ryzen 5800X3D, RTX 3070Ti, 32GB RAM
Nvidia driver: 595.58.03

AAlexeySFdot 2026-07-29 github

Compatibility Report

  • Name of the game with compatibility issues: FBC: Firebreak
  • Steam AppID of the game: 2272540

System Information

  • GPU: NVIDIA GeForce RTX 4060 Ti 16GB
  • Video driver version: 610.43.03
  • Kernel version: 7.1.5-1-cachyos
  • Proton version: Proton Experimental (experimental-11.0-20260724c), Proton 10.0-4, Proton-CachyOS (all affected)

I confirm:

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

Symptoms

The game runs fine with Ray Tracing disabled.

Enabling any Ray Tracing option in the graphics settings causes an immediate crash.

After the crash, the game fails to launch on every subsequent attempt (the Ray Tracing setting is saved and applied at startup).

This happens on Proton Experimental, Proton 10, and Proton-CachyOS.

From the Proton log (Experimental): https://gist.github.com/AlexeySFdot/173be40a767f848e918301f7972f6660
Exception 0xc000001d at ... libnvidia-gpucomp.so.610.43.03 + 0x35eea0
err:vulkan:vkCreateComputePipelines Exception 0xc000001d in Unix call.

STATUS_ILLEGAL_INSTRUCTION occurs inside NVIDIA's GPU compiler library during vkCreateComputePipelines when the game tries to create ray tracing / compute pipelines.

Reproduction

  1. Launch the game with Proton Experimental / Proton 10 / Proton-CachyOS.
  2. Go to Graphics settings.
  3. Enable Ray Tracing (any level).
  4. Apply → immediate crash.
  5. Try to start the game again → crash on launch.

Proton versions

Error codes