ValveSoftware / ValveSoftware/Proton

DEAD OR ALIVE Xtreme Venus Vacation (958260)

Open
#2,773 65 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Game compatibility - Unofficial Regression XAudio2
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Compatibility Report

"DEAD OR ALIVE Xtreme Venus Vacation"
Steam AppID: 958260

System Information

I confirm:

  • [ Y ] that I haven't found an existing compatibility report for this game.
  • [ Y] that I have checked whether there are updates for my system available.

PROTON_LOG = https://gist.github.com/supashang/282852ad5e0a9b46962a1fc523859921
[Edit]

Symptoms

Launching the game presents a grey box with no buttons to launch.
Quitting the game leaves running process "DOAX VenusVacation Launcher" consuming 97% of the CPU time until it is killed.

Reproduction

  1. Launch the game as normal from Steam.
  2. Quit the launcher by pressing the close button.
  3. Observe the "DOAX VenusVacation Launcher" process after closing the window.
  4. Desktop feels sluggish while process is running.
  5. Kill the process to recover.

Note: At this time, the game is region locked in the west, so may be hard to reproduce the error for those in that region. Although it is able to be downloaded behind a VPN.
Source: https://www.oneangrygamer.net/2019/03/dead-or-alive-xtreme-venus-vacation-is-region-blocked-on-steam-but-theres-a-fix/80921/

ProtonDB: https://www.protondb.com/app/958260

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

The report names no source files, tests, or code entry points; start with the linked Proton log and the listed reproduction steps for the launcher process. Done would require a confirmed resolution for the grey launcher and the high-CPU process, with a regression test only if the project provides a relevant test location.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.