ValveSoftware / ValveSoftware/Proton
GTFO (493520)
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: GTFO
- Steam AppID of the game: 493520
System Information
- GPU: Gigabyte Radeon RX 5700 XT Gaming OC 8G
- Driver / LLVM version: amdgpu 5.4.7.20.10 / 4.5 Mesa 19.3.4 / LLVM 9.0.0
- Kernel version: 5.3.0-51-generic
- Link to full system information report as Gist: [link]
- Proton version: 5.0-7 / 4.11-13. Also tried using Glorious Eggroll version 5.6-GE-2.
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.
Symptoms
The game simply will not start using any of the tried Proton versions. The game will briefly show an Unity crash handler and then close.
Reproduction
Launch the game using the hardware and drivers provided in System information.
Proton log
- Link to Proton log as Gist: [link]
Workarounds
-
I managed to get around the launch crash with OpenGL-based wined3d renderer by using launch options
PROTON_USE_WINED3D=1 %command%. This did however come with severe rendering issues in the main game. 2D interfaces like the menus and the game HUD worked fine. Would you prefer if I opened a separate issue for using wined3d? -
I managed to get it working properly with the LLVM compiler framework by using launch options
RADV_PERFTEST=llvm. However, I happened upon this solution at random, and it seems to not be an intended way to use Proton.
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
Start by reproducing the launch failure with the listed Proton versions, hardware, and driver details, then inspect the linked Proton log and the reported wined3d and RADV_PERFTEST workarounds. Done means determining and addressing the Unity crash without introducing the severe rendering issues described.
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