Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZACH-LIKE (1098840) #2822

Open
2 tasks done
Bumbadawg opened this issue Jun 19, 2019 · 7 comments
Open
2 tasks done

ZACH-LIKE (1098840) #2822

Bumbadawg opened this issue Jun 19, 2019 · 7 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues .NET Uses the .NET framework

Comments

@Bumbadawg
Copy link

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:

  • that I haven't found an existing compatibility report for this game.
  • 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

@kisak-valve kisak-valve added .NET Uses the .NET framework Game compatibility - Unofficial Games not expected to work without issues labels Jun 19, 2019
@Rohansi
Copy link

Rohansi commented Jun 28, 2019

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

@madewokherd
Copy link
Collaborator

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.

@madewokherd
Copy link
Collaborator

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.

@Bumbadawg
Copy link
Author

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

@cid0rz
Copy link

cid0rz commented Oct 13, 2019

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

@madewokherd
Copy link
Collaborator

madewokherd commented Jan 11, 2021

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).

@madewokherd
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game compatibility - Unofficial Games not expected to work without issues .NET Uses the .NET framework
Projects
None yet
Development

No branches or pull requests

5 participants