protonscr

SCP: Secret Laboratory Graphics and performance issues after Nvidia driver update

protonclosed appid 700330
ValveSoftware/Proton#8890 · opened 2025-07-08 by CitrineSilly · updated 2025-07-08 · 1 comments · github · game page · search this game
CCitrineSilly 2025-07-08 github

Note: i forgot to label this and it seems i cant label it myself, Could someone mark this with the compatiblity issues: unofficial label please

Compatibility Report

  • Name of the game with compatibility issues: SCP: Secret Laboratory
  • Steam AppID of the game: 700330

System Information

  • GPU: Nvidia RTX 3060
  • Video driver version: Nvidia 575.64.03 (Steam system info says im using mesa 21.5.3 for some reason? Not sure why, im fairly inexperienced with gpu drivers)
  • Kernel version: 6.15.5-arch1-1
  • Link to full system information report as Gist:
  • Proton version: Proton Hotfix (Jun 27 2025)

I confirm:

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

Proton log:
Proton is not generating logs

Local Game log:
Player.log

Symptoms

Game runs at 2-15 seconds per frame
Graphical artifacts are present on certain bloom objects
As a result of the performance issues audio does not work either except for some crunchy snippets of audio

Image example w/o fps counter:
Image

Reproduction

  1. Open game
  2. Join a server
  3. Issue will happen
Kkisak-valve maintainer 2025-07-08 github

Hello @CitrineSilly, we're using one issue report per unofficially supported game title, and usually I'd transfer this issue report to #4229, however, you've correctly identified that you have a video driver issue instead of a Proton issue.

You're running Steam in a Flatpak environment, and the installed NVIDIA driver inside that environment doesn't match the host system. The NVIDIA proprietary driver requires that the running kernel module, 32 bit userspace libraries, and 64 bit userspace libraries are all installed and exactly the same version to work properly. Since Flatpak is involved, that extends to both inside and outside that container environment. Tell Flatpak to do an update cycle, and if that doesn't help, then report the issue to the Flatpak package maintainers.

Closing as not a Proton issue.

Proton versions