Compatibility Report
- Name of the game with compatibility issues: DarkStory Online
- Steam AppID of the game: 1020780
System Information
- GPU: AMD Radeon RX Vega 56/64
- Driver/LLVM version: AMD AMD VEGA10 (DRM 3.35.0, 5.4.0-109-generic, LLVM 12.0.0)
- Kernel version: 5.4.0-109-generic
- Link to full system information report as Gist: here (The laptop is an Acer Predator Helios 500 with AMD hardware.)
- Proton version: 7.0-2
I confirm:
Symptoms
When the game is started, shortly after the splash window appears, two error dialog boxes also appear (see below for a screenshot depicting these dialog boxes). When the two error dialog boxes are closed out, after a brief pause, the splash window disappears. The program produces no further observable behavior, but it remains running as a process and must be killed (such as by clicking the "Stop" button within the Steam client's UI).
Reproduction
The above behavior occurs consistently when running the game using Proton version 7.0-2 (as well as other Proton versions that I've tried, including Proton Experimental as of the time of this report; the latest third party fork GE-Proton7-17 also produces this behavior, too). This game's ProtonDB entry suggests that nobody else has managed to get this game working in Proton yet, either.
steam-1020780.log
Compatibility Report
System Information
I confirm:
Symptoms
When the game is started, shortly after the splash window appears, two error dialog boxes also appear (see below for a screenshot depicting these dialog boxes). When the two error dialog boxes are closed out, after a brief pause, the splash window disappears. The program produces no further observable behavior, but it remains running as a process and must be killed (such as by clicking the "Stop" button within the Steam client's UI).
Reproduction
The above behavior occurs consistently when running the game using Proton version 7.0-2 (as well as other Proton versions that I've tried, including Proton Experimental as of the time of this report; the latest third party fork GE-Proton7-17 also produces this behavior, too). This game's ProtonDB entry suggests that nobody else has managed to get this game working in Proton yet, either.
steam-1020780.log
