ValveSoftware / ValveSoftware/Proton
Uberlaufer (or Überlaüfer) (appid 1391540)
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: Uberlaufer
- Steam AppID of the game: 1391540
System Information
- GPU: AMD Radeon RX 6800 XT
- Driver/LLVM version: Mesa 21.3.0
- Kernel version: 5.15.3-220-tkg-bmq
- Link to full system information report as Gist: https://gist.github.com/Patola/7b647e9baf20e40cb64ccfd77cbb2b12
- Proton version: 6.3-7
- Note: tested in VR with the Oculus Quest 2 via ALVR. Before running the game, ran other game (Arizona Sunshine) to ensure VR was working correctly; after the game failed to start (waited for a couple minutes after the "play" button went back to green), ran Arizona Sunshine again and all was good.
- Note (2): I have a Valve Index that's out of service for the moment, will be back in a few weeks.
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
- Game doesn't start.
Reproduction
- Try to start the game by clicking in from within SteamVR home or from pressing PLAY on the steam client with SteamVR running. It won't start.
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 reading the attached steam-1391540.log and reproducing the launch failure with Proton 6.3-7 through SteamVR, using the reported Mesa, kernel, GPU, and ALVR setup. Determine whether the report provides enough evidence for a compatibility diagnosis or fix; done means the game launches successfully in the affected VR configuration or the failure is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, 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