ValveSoftware / ValveSoftware/Proton

Beat Saber (620980)

Open
#6,638 46 comments 2 reactions 0 assignees View on GitHub

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: Beat Saber (unity_alpha branch)
  • Steam AppID of the game: 620980

System Information

  • GPU: PowerColor RX 6600 XT
  • Driver/LLVM version: Mesa 22.3.6-1
  • Kernel version: 6.1.18-200
  • Link to full system information report as Gist:
  • Proton version: Proton experimental, Proton 7.0-6 (same issue)
  • Arch distrobox container under Fedora Silverblue 37

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.

steam-620980.log

Symptoms

Can't launch it on newest version that uses OpenXR instead of OpenVR. It shows logo for a split second and closes.

Bonelab on latest beta (openxr powered game) under proton works fine.

Reproduction

Always.

  1. Change beat saber beta to unity_alpha
  2. Run SteamVR (be it alvr, or native headset)
  3. Run Beat Saber
  4. Crash

Additional notes

In logs there is mentions of missing extension like XR_KHR_D3D12_enable, which is not implemented by Proton at the moment, which is probably the reason it can't start.
Tried to run with -force-vulkan but it crashes with InitialiseGraphicsEngine error (probably wasn't built with vulkan support)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached steam-620980.log and the referenced wineopenxr/openxr.c extension-handling section. Reproduce the failure using the unity_alpha branch, SteamVR, and the listed Proton versions, then compare the OpenXR initialization messages with the missing XR_KHR_D3D12_enable extension. Done means Beat Saber starts successfully on the affected configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
game-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.