protonscr

Battle Brothers

protonopen appid 365360Game compatibility - UnofficialRegression
ValveSoftware/Proton#4148 · opened 2020-08-25 by Mart-Bogdan · updated 2024-07-14 · 6 comments · github · game page · search this game
MMart-Bogdan 2020-08-25 github

Compatibility Report

  • Name of the game with compatibility issues: Battle Brothers
  • Steam AppID of the game: 365360

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.

Protonlogs:

Default settings:
steam-365360-no-opengl-hack.log
With applied OpenGL hack:
steam-365360-opengl-hack.log

Symptoms

With default proton settings game launches and shows a black screen, only cursor could be seen.

Reproduction

Launch game from steam with default options.

Hotfix

I've noticed on Lutris page recommended setting: add environment variable MESA_GL_VERSION_OVERRIDE: 3.3COMPAT

I've tried editing wineprefix user.reg to add env variable but didn't helped (perhaps it only visible from within windows, not from OpenGL driver)

Then I've launched steam as MESA_GL_VERSION_OVERRIDE=3.3COMPAT steam it helped.

later I've altered game launch settings as:

MESA_GL_VERSION_OVERRIDE=3.3COMPAT %command%

Readiness

With this fix ONLY issue with game is flickering cursor, but in other aspects game is playable, sound and other stuff works.

Suggestion

Add this environment variable as default setting.

P.S. would test on RX 590 this week, perhaps issue is actually with my Intel videocard.

Kkisak-valve maintainer 2020-08-25 github

Hello @Mart-Bogdan, this sounds like the expected result for mesa/i965. It advertises OpenGL 3.0 for compat contexts (and supports OpenGL 3.3 core contexts) and you've found a reasonable workaround if it works.

With newer hardware, mesa/iris exposes support for higher compat contexts, but iris support has not been extended backwards to support Sandybridge. My understanding is that the Intel devs have pondered what it would take to add support, and wiring up support for older than Broadwell chips would slow down the newer driver for all users, which is why it hasn't been prioritized.

MMart-Bogdan 2020-08-26 github

I confirm that on AMD RX590 game runs on Linux like a charm and It could be moved to the lsit of supported by Proton titles!

No mouse flickers, stable 58-60 FPS.

System Info: https://gist.github.com/Mart-Bogdan/b03853384b8df14c56ff113adc9ec01e

GPU: Radeon RX 590
Driver/LLVM version: 4.6 (Compatibility Profile) Mesa 20.0.7 (POLARIS10, DRM 3.36.0, 5.6.15-1-MANJARO, LLVM 10.0.0)
Kernel Version: 5.6.15-1-MANJARO
Proton version: 5.0-9

P.S. setting compatibility env variable tweak didn't affect the game and it runs normally without cursor flickering. I still suggest enabling this env variable by default. (But I'm not an expert and have no clue what is it doing, perhaps I am wrong)

WWasmachenDennSachenSo 2024-07-04 github

This game is not able to launch on Proton 9.0-2+. Proton 8.0-5 is working.

I think the culprit is the following line in the log:
10340.690:0124:0128:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x53b520

It does not exist in the logs which are generated with version 8.0-5.

Proton 9.0 Experimental: steam-365360.log
Proton 8.0-5: steam-365360.log

Kkisak-valve maintainer 2024-07-04 github

Hello @WasmachenDennSachenSo, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.

It might be interesting to test how the game behaves with the launch options set to PROTON_DISABLE_NVAPI=1 %command%.

WWasmachenDennSachenSo 2024-07-05 github

Here you go,

The game is starting in Proton 9.0-2+ with the variable PROTON_DISABLE_NVAPI=1 set!

System Information: https://gist.github.com/WasmachenDennSachenSo/eac5f9887616f3acde5958f8168bb4e2
Runtime Information: https://gist.github.com/WasmachenDennSachenSo/4cbc3a8c08692defddc8b27bbb3561ad

WWasmachenDennSachenSo 2024-07-14 github

Thank you for this blazingly fast fix! :)