ValveSoftware / ValveSoftware/Proton
Stanley Parable (221910)
Open
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: Stanley Parable
- Steam AppID of the game: 221910
System Information
- GPU 1: AMD ICELAND (DRM 3.35.0, 5.4.0-65-generic, LLVM 11.0.0)
- GPU 2: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
- Driver version: 3.0 Mesa 20.3.4
- Kernel version: 5.4.0-65-generic
- Link to full system information report as Gist: https://gist.github.com/rybak/6dd42cb97a3e61008d755989198948c7
- Proton version: 4.11-13, 5.13-6 and Experimental
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.
- that the PROTON_LOG=1 has been added to the launch options, but only version 4.11-13 has produced a log file: https://gist.github.com/rybak/f05b36914c166c660f15bea1e4688468
- that after adding PROTON_LOG=1, Proton 5.13-6 and Proton Experimental didn't produce a log file.
Notes
- I use
DRI_PRIME=1 PROTON_LOG=1 %command%for the custom launch command.
Symptoms
- With Proton 5.13-6 or Experimental, the game doesn't start at all (i.e. it crashes before I see anything).
- With Proton 4.11-13, the game launches, but the viewport for the game is broken – only one sixths of the game's output is visible. The following screenshot was made in fullscreen:

- Without Proton, the game launches fine (whole screen is visible), but the game crashes during loading after pressing "Begin the game" (as described in a Steam Community discussion).
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
Begin by reproducing the three reported cases with Proton 4.11-13, 5.13-6, and Experimental using the documented DRI_PRIME=1 PROTON_LOG=1 %command% launch options. Compare the available Proton log and system information with the startup, viewport, and loading failures described in the report. Done means identifying a reproducible compatibility cause or confirming the relevant behavior has changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- computer-graphics, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100