ValveSoftware / ValveSoftware/Proton
EVERSLAUGHT (appid 1530750, VR)
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: EVERSLAUGHT
- Steam AppID of the game: 1530750
System Information
- GPU: AMD RX 6800 XT
- Driver/LLVM version: mesa 21.1.5-1
- Kernel version: 5.13.6-184-tkg-bmq
- Link to full system information report as Gist: https://gist.github.com/Patola/a69ef95b1b481d585b42f7796cfb0204
- Proton version: 6.3-5
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
There are two problems.
- First one is that the steam overlay complains that it can't find /common/EVERSLAUGHT/actions.json. This one was seemingly resolved by copying actions.json from other game (Shadow Legend VR). The file contains a simple description of the joystick binding.
- Second one is that instead of starting in the VR headset, the game starts on the screen (and is unresponsive in that state)
Reproduction
- Just launch the game.
The attached proton log was generated with the game being run with the other game's actions.json.
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 EVERSLAUGHT with Proton 6.3-5 and inspect the attached steam-1530750.log, focusing on the missing actions.json warning and the non-responsive desktop launch. Check the expected path /common/EVERSLAUGHT/actions.json and compare behavior with and without the copied file. Done means the game launches in the VR headset without the reported overlay error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100