ValveSoftware / ValveSoftware/Proton
Green Hell (815370)
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: Green Hell
- Steam AppID of the game: 815370
System Information
- GPU: Radeon RX Vega 56
- Driver/LLVM version: Mesa 18.3.0 - LLVM 7.0.0
- Kernel version: 4.15.0-43-generic
- Link to full system information report as Gist: Link
- Proton version: 3.16-4
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.
Log: steam-815370.log
Symptoms
In full-screen mode the mouse stops working in menus sometimes. Alt-tabbing results in mouse working in the menus but not in first person mode. The full-screen doesn't capture the mouse after alt-tabbing.
On some occasions the character starts spinning while looking up or down (when body-inspect and backpack were open together). Restarting the game fixes this.
Reproduction
I can reproduce the character spinning by going into the body-inspect view, opening the backpack and applying a bandage. Closing everything after that results in the character spinning because of high mouse sensibility.
That the mouse stops working in the menus just happens kind of random.
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 mouse failures in Green Hell with Proton 3.16-4, using the full-screen, alt-tab, body-inspect, backpack, and bandage sequences described in the report. Inspect steam-815370.log and the linked system information to identify whether the menu input, mouse capture, or spinning behavior is recorded; done means the reported input problems are consistently resolved and verified against those reproductions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100