ValveSoftware / ValveSoftware/Proton
SENRAN KAGURA ESTIVAL VERSUS (502800)
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: SENRAN KAGURA ESTIVAL VERSUS
- Steam AppID of the game: 502800
System Information
- GPU: NVIDIA GeForce GTX 1070
- Driver/LLVM version: nvidia 520.56.06
- Kernel version: 6.0.9-zen1-1-zen
- Link to full system information report as Gist: https://gist.github.com/Isaiahmag/d8603493cf217fdb241ddb6b273dd8a1
- Proton version: Proton 7.0-4 and Proton Next (7.0-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 and Reproduction
When attempting to join or create a lobby after a short period of time if everyone doesn't ready up soon enough something randomly triggers the game to crash. The game doesn't crash if you get past the lobby but when you re-enter the game is very likely to crash. Everything else in the game is playable to start to finish singleplayer wise.
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 with the attached steam-502800-proton-7.0-4.log and steam-502800-proton-next.log, then reproduce the lobby crash using the reported Proton versions and system information. Compare joining or creating a lobby, waiting before readying, and re-entering multiplayer. Done means the triggering behavior is identified and the lobby path no longer crashes, with evidence from a repeatable test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100