ValveSoftware / ValveSoftware/Proton
Vampire Survivors (1794680)
Nobody has claimed this yet.
- 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: Vampire Survivors
- Steam AppID of the game: 1794680
System Information
- GPU: NVIDIA GeForce RTX 2070 SUPER
- Driver/LLVM version: NVIDIA-SMI 510.68.02 Driver Version: 510.68.02 CUDA Version: 11.6
- Kernel version: Linux fedora 5.17.6-300.fc36.x86_64 (#)1 SMP PREEMPT Mon May 9 15:47:11 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
- Link to full system information report as Gist: https://gist.github.com/FilBot3/66a0a18cec49aa860b892bd2e552fd2d
- Proton version: Proton 7.0-2, Proton Exp 7.0-20220511, GE-Proton 7.17-1
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.
PROTON_LOG
Symptoms
Game would not launch without PROTON_LOG=1 set. Would throw the following error with all listed versions of Proton.

Reproduction
Install Vampire Survivors. Use default Proton, or Proton Experimental, or GE-Proton.
Works seemingly with PROTON_LOG=1 %command% set and using Proton Exp and GE-Proton. Default proton would say that launcher.sh. However now upon relaunching with the configurations I did before, it is now working. So, inconsistent behavior.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce Vampire Survivors with default Proton, Proton Experimental, and GE-Proton, using the launch command and PROTON_LOG setting described in the report. Start by inspecting the attached Proton log and the reported launcher.sh failure; done means the game launches consistently without requiring PROTON_LOG=1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100