ValveSoftware / ValveSoftware/Proton

Bomb Bots Arena (754050)

Open
#5,002 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Game compatibility - Unofficial
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Compatibility Report

  • Name of the game with compatibility issues: Bomb Bots Arena
  • Steam AppID of the game: 754050

System Information

  • GPU: RTX 3070
  • Driver/LLVM version: nvidia 470.57.02
  • Kernel version: 5.4.0
  • Link to full system information report as Gist
  • Proton version: 6.3-5

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-754050.log

Symptoms

Game crashes with Unity Crash Handler on startup

Reproduction

  • Just install and start game

Addition Info

The game used to work well before, PROTON_NO_ESYNC=1 helped though with some stutter on exploding bombs. Probably a recent update of the game causes now this issue as the unity player.log file indicates:
Unhandled exception: unimplemented function CFGMGR32.dll.CM_MapCrToWin32Err called in 64-bit code (0x000000007bc2f7e8).
Player.log
So to make the game start again it helps to use these launch parameters:
WINEDLLOVERRIDES="CFGMGR32=n" PROTON_NO_ESYNC=1 %command%

But there is a memory leak, as after like 3 rounds the game starts to heavily lag until it freezes and in top I can see it going steadily up to 80%+ memory allocation. This is reproducible on my machine.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing Bomb Bots Arena on Proton 6.3-5 with the attached steam-754050.log and Player.log, then compare behavior with and without the listed CFGMGR32 and ESYNC launch options. Investigate the reported CFGMGR32.dll failure and memory growth across several rounds. Done means the game starts and remains playable without the workaround or progressive freezing.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, unity
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.