ValveSoftware / ValveSoftware/Proton

Radio Commander (871530)

Open
#3,136 1 comment 0 reactions 0 assignees View on GitHub

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: Radio Commander
  • Steam AppID of the game: 871530

System Information

  • GPU: Vega 56
  • Driver/LLVM version: Mesa 19.2.0/8.0.1
  • Kernel version: 5.3.5
  • Link to full system information report as Gist:
  • Proton version: 4.11-7

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.

Running with no options (other than DRI_PRIME=1 %command%)

steam-871530.log

Game's "output_log.txt" from "%APPDATA%\LocalLow\Serious Sim\Radio Commander"

output_log.txt

Also tried without DXVK, same result:

steam-871530-PROTON_USE_WINED3D.log

Game's "output_log.txt" from "%APPDATA%\LocalLow\Serious Sim\Radio Commander":

output_log.txt

I have also tried to run with PROTON_NO_D3D11 But game exits immediately, I assume there is no earlier direct-x fallback

Symptoms

Application starts with black screen with mouse cursor (which appears to move around the screen fine, for a while) and "jittery" audio playing.

Interaction (clicks and keyboard presses) unresponsive.

Trying to halt the application via the window manager or alt-F4 sometimes freezes Gnome.

Screenshot from 2019-10-10 20-58-31

Reproduction

Install App.
Try to run

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

Start by reproducing Radio Commander 871530 with Proton 4.11-7 using the reported launch configuration, then compare steam-871530.log, the DXVK-disabled log, and the game's output_log.txt. Done would mean identifying a confirmed cause and a validated compatibility fix, but the report does not name a source file or failing test.

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
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.