ValveSoftware / ValveSoftware/Proton
BlazBlue Cross Tag Battle (702890)
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: BlazBlue Cross Tag Battle
- Steam AppID of the game: 702890
System Information
- GPU: GTX 980
- Driver/LLVM version: Nvidia 430.26
- Kernel version: 4.19.60-1
- Link to full system information report as Gist: Gist
- Proton version: 4.11-1
Symptoms
Occasionally crashes when listing multiplayer lobbies quickly.
Reproduction
Run BBTAG.exe with Steam Play and Proton
4.2 log: steam-702890.log
4.11-1 log crash:
steam-702890-updated.log
4.11-1 log working: ( launched into multiplayer lobby )
steam-702890.log
Additional Information
This may relate to Blazblue Central Fiction (586140) too as the same render error was posted there.
4.2 error:
fixme:d3d9:d3d9_device_CreateRenderTargetEx stub!
Progress
4.2 error was patched in 4.11-1. This was merged into Proton 4.11-1 as 2b3955e
Using protonfixes with a winetrick for quartz removes one of the errors in the log.
The game runs. The offline modes and multiplayer lobby seems to work (regardless of quartz). Game occasionally crashes when listing multiplayer lobbies (especially if done quickly).
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 multiplayer lobby crash with Proton 4.11-1 and compare steam-702890-updated.log with the working steam-702890.log. Use the linked system information and logs to identify the difference associated with rapid lobby listing; done means the game no longer crashes in that scenario.
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