ZACH-LIKE

protonopen appid 1098840Game compatibility - Unofficial.NET

ValveSoftware/Proton#2822 · opened 2019-06-19 by Bumbadawg · updated 2021-01-11 · 7 comments · github · game page · search this game

BBumbadawg 2019-06-19 github

Compatibility Report

Name of the game with compatibility issues:
Steam AppID of the game:

System Information

GPU: GTX 1070
Driver/LLVM version: 430.26
Kernel version: 4.15
Link to full system information report as Gist:
Proton version: 4.2-7

I confirm:

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

Symptoms

Game starts but no window, no sound.

Reproduction

Start the game.

(log got huge in no time, lots of hidden symbols in it)
steam-1098840.log

RRohansi 2019-06-28 github

Looks like the game is outputting everything to the log. Makes sense, since ZACH-LIKE is just a console application.

Mmadewokherd 2019-08-07 github

Normally, when starting a program with CreateProcess or ShellExecute and using the appropriate flags, a console would be created automatically for console executables. Unfortunately, that's not possible when using the 'wine' command as Proton does.

I suppose Proton could examine the .exe headers to determine if it's a console executable, but I'm not sure we want to write a PE parser in Python for this.

Mmadewokherd 2019-08-07 github

I've just been informed that Proton starts programs through its own steam.exe which uses CreateProcess. In theory, all we have to do is set the CREATE_NEW_CONSOLE flag when calling CreateProcess.

BBumbadawg 2019-08-08 github

Reporting for 4.11: still the same (first 9M of the log only here, hidden symbols present)
steam2-1098840.log

Ccid0rz 2019-10-13 github

I have the same Issue, I have tried with all available versions of proton with no luck.

Mmadewokherd 2021-01-11 github

We now get this error:

[ERROR] FATAL UNHANDLED EXCEPTION: System.ArgumentOutOfRangeException: Windows error 87
Parameter name: left/top
  at System.WindowsConsoleDriver.SetWindowSize (System.Int32 width, System.Int32 height) [0x0006d] in <ed5b1988ac884bedabd2689d15e79ae5>:0 
  at System.ConsoleDriver.SetWindowSize (System.Int32 width, System.Int32 height) [0x00000] in <ed5b1988ac884bedabd2689d15e79ae5>:0 
  at System.Console.SetWindowSize (System.Int32 width, System.Int32 height) [0x00000] in <ed5b1988ac884bedabd2689d15e79ae5>:0 
  at launcher.Program.Initialize () [0x00000] in <cd7437ce453a4ecc8e194c88d44aa0f0>:0 
  at launcher.Program.Main (System.String[] args) [0x00022] in <cd7437ce453a4ecc8e194c88d44aa0f0>:0 (1)

The application asks for a console size of 120x36.

I was able to work around this by setting the default console buffer size in the registry. It seems to still have trouble setting the correct window size, but at least it doesn't crash.

In HKEY_CURRENT_USER\Console I set ScreenBufferSize to a DWORD value of 240078 (hexadecimal).

Mmadewokherd 2021-01-11 github

Setting WindowSize to that same value of 240078 works around the issues with resizing the window.

Nothing extracted yet.