protonscr

Super Battle Golf

protonopen appid 4069520Game compatibility - Unofficial
ValveSoftware/Proton#9850 · opened 2026-06-03 by Cheese-King-of-Denmark · updated 2026-06-04 · 5 comments · github · game page · search this game
4 matching comments, n / p to jump
CCheese-King-of-Denmark 2026-06-03 github

Compatibility Report

  • Name of the game with compatibility issues: Super Battle Golf
  • Steam AppID of the game: 4069520

System Information

  • GPU: NVIDIA GeForce RTX 3060 Ti
  • Video driver version: NVIDIA 535.309.01
  • Kernel version: 6.17.0-35-generic
  • Link to full system information report as Gist:
  • Proton version: 10.0-4

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 lags horribly from launch and multiplayer connectivity is almost completely broken. It worked perfectly well in version 10.0-3

Ssimifor 2026-06-04 github

@Cheese-King-of-Denmark the game is working fine for me on amd and nvidia, including multiplayer (at least from joining a random room). But it should be noted that nvidia's driver branch 535 originally came out in 2023, it'd be better to try a newer branch as it is likely affecting things negatively

CCheese-King-of-Denmark 2026-06-04 github

@simifor Just a few days ago it was working perfectly fine with that driver, so I think that seems unlikely. The only thing that's changed is the update from Proton 10.0-3 to 10.0-4.

Kkisak-valve maintainer 2026-06-04 github

That's not possible. Proton 10.0-4 was released in January https://github.com/ValveSoftware/Proton/releases/tag/proton-10.0-4.

CCheese-King-of-Denmark 2026-06-04 github

@kisak-valve Well, Proton updated in between me playing and it working and then it not working. So far as I can tell, it changed from 10.0-3 to 10.0-4. Maybe I'm mistaken, but regardless it was working fine and then it wasn't, without either the game or my PC being updated, but Proton did update.

Ssimifor 2026-06-04 github

@Cheese-King-of-Denmark proton should have updated long ago, are you sure you didn't see another version update? And given that I can't repro on my end and that there aren't any other reports so far, I still think your best course of action is going with a more recent driver version and seeing if that makes a difference, and if it doesn't you need to supply the information you omitted from your original report, namely the gist with steam's "system information" output and a proton log.

Proton versions