ValveSoftware / ValveSoftware/Proton
PowerbeatsVR (appid 810500)
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: PowerbeatsVR
- Steam AppID of the game: 810500
System Information
- GPU: AMD Radeon RX 6800 XT
- Driver/LLVM version: Mesa 20.3.1-1
- Kernel version: 5.10.1-103-tkg-bmq
- Distribution: Arch Linux
- Link to full system information report as Gist: https://gist.github.com/Patola/6caf42ff20f69f1bc95b527ef7714a31
- Proton version: 5.13-4, 5.0-10, 4.11-13 - tested all of these and even Proton Experimental, also for these tried with PROTON_NO_FSYNC=1 and PROTON_NO_ESYNC=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.
Symptoms
Game starts, presents a black screen and then either hangs forever or crashes back to SteamVR
Reproduction
1 - Call SteamVR
2 - Once inside SteamVR, call the game
3 - it starts by fading to black then either crashes or hangs forever.
Sending the log for Proton 5.13-4 (no extra variables) and 4.11-13 (no fsync and no esync). If you need the others please say
steam-810500-proton-5.13-4.log
steam-810500-proton-4.11-13-no-fsync-and-esync.zip
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 comparing steam-810500-proton-5.13-4.log with steam-810500-proton-4.11-13-no-fsync-and-esync.zip while reproducing the black-screen failure through SteamVR. Trace the failure far enough to identify why PowerbeatsVR hangs or crashes, then verify that the game reaches a usable state on a supported Proton configuration.
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