Proton icon indicating copy to clipboard operation
Proton copied to clipboard

GRIS (683320)

Open dreamer opened this issue 5 years ago • 16 comments

Compatibility Report

  • Name of the game with compatibility issues: GRIS
  • Steam AppID of the game: 683320
  • ProtonDB link: https://www.protondb.com/app/683320

System Information

  • GPU: GTX 770
  • Driver/LLVM version: NVIDIA 418.56
  • Kernel version: 5.0.5
  • Link to full system information report as Gist: link
  • Proton version: 4.2-2

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.

steam-683320.log

Symptoms

The game starts and shows menu. Once "New game" is selected, screen turns white and game hangs. Closing windows closes application, but sometimes it crashes.

Reproduction

Select "New game" in main menu.

Workarounds

The community already identified that the problem here is lack of Windows Media Foundation support in wine - tracked in #1464 (game attempts to load mfplat.dll).

For users who would like to test the game anyway, @Mastergatto already documented necessary steps in this comment. I tried and these worked (I needed to google for some archived version of zipped file mentioned in the comment) - so far I played through the first "level" of the game and it works perfectly, including controller support.

As a side note, the same "white screen" problem affects not only Linux users, but also some Windows users, as indicated in "Common issues" thread in Steam Discussions.

dreamer avatar Apr 07 '19 02:04 dreamer

After manually applying the <Workaround removed by moderator> patch, game is almost fully playable. However, game freeze when singing to unlock the secret scene (see 2:16:15).

Use taskset -c 0-15 command% as launch command to solve the problem

nolddor avatar May 09 '20 18:05 nolddor

Hello @nolddor, the workaround you linked is legally problematic and has been removed.

kisak-valve avatar May 09 '20 19:05 kisak-valve

Uops! sorry for that, I hadn't idea about the legal terms of the provided link. Thanks for doing it

nolddor avatar May 09 '20 19:05 nolddor

Hi, the white screen appears even when using Media Library DLLs. I tried to employ Proton 4.11, 5.0, 5.13, and Experimental - the result is the same.

antoscha avatar Dec 13 '20 23:12 antoscha

Just a heads up regarding the current state of this game - with current Proton Experimental it goes in-game without any workaround. Everything works properly but the video files for the smoke effects (and probably other things further in the game that I haven't tested) still don't play properly. This will likely be solved with further improvements to Media Foundation support on Wine.

AniLeo avatar Dec 24 '20 01:12 AniLeo

with current Proton Experimental it goes in-game without any workaround.

Nope, it hangs at the start as previously.

antoscha avatar Dec 24 '20 18:12 antoscha

No, it doesn't on my setup, I literally just played it

AniLeo avatar Dec 24 '20 19:12 AniLeo

Game starts and works well with latest Proton 6.3-2, but some videos don't show up (you can see the TV screen that means "no codec"). An example of this is right at the start of the game.

ziabice avatar Apr 11 '21 16:04 ziabice

Still not working - shows the white screen at start.

antoscha avatar Feb 16 '22 11:02 antoscha

Ok, now it works for me, no tweaks were required.

antoscha avatar Feb 15 '23 19:02 antoscha

PROTON_USE_WINED3D=1 %command% - with this launch command the game starts for me, but there is no sound.

zoli111 avatar Sep 16 '23 10:09 zoli111

Even though GRIS says it is Steam Deck verified on the store page I can not get it to run. Tried Proton 8.0-5, 6.3-8 and GE-Proton8-28 & 30 but it crashes to an error screen during the Nomada/Devolver logo intro which says "GRIS has encountered an error and must close". First attemtped to play docked then switched to handheld but no change.

This are the contents of my latest error.log

If I run it with the PROTON_LOG=1 flag the following shows in the log

Crash!!!
Wwise: Cannot create streaming I/O device.
 
(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

WwiseUnity: Failed to initialize the sound engine. Abort.
 
(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

2427.143:0130:01e8:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\dbghelp.dll" at 000000023ECB0000: builtin
Wwise: Term() called before successful initialization..
 
(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Trying to run it with the PROTON_USE_WINED3D=1 flag causes it to crash before the intro screen with the message "Failed to initialize player" and complains about DirectX 11 and up to date drivers.

edit: Found an 8 month old post on reddit with the exact same issue, they state it fixed itself after a couple reboots (which I also already did) https://www.reddit.com/r/SteamDeck/comments/131ou5s/gris_crashing_on_startup_on_steam_deck/ So maybe it is not Proton related?

LeLobster avatar Feb 07 '24 00:02 LeLobster

I tried playing it for few minutes and it generally works on 8.0-5. On Experimental and 9.0 Beta, on exit fatal error in gc: GetThreadContext failed error pops up. On Experimental with WINEFSYNC_FUTEX2=0 %command% the issue is not reproducible.

System Information Report: https://gist.github.com/Soveu/15733e99aa857aaf763d26bffbeda6cd Proton log: steam-683320.log

Reproduction: Launch game > Continue > Quit > Exit Just launching the game and exiting right in the menu doesn't trigger the error, level has to be loaded

Soveu avatar Mar 10 '24 10:03 Soveu

Hello @Soveu, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

kisak-valve avatar Mar 10 '24 13:03 kisak-valve

@kisak-valve I have updated the comment above

Soveu avatar Mar 11 '24 16:03 Soveu

@Soveu I was able to reproduce the issue, however, it's not a proton 9 regression as it can also happen on proton 8. WINEFSYNC_FUTEX2=0 also doesn't prevent it, as proton doesn't make use of that environment variable.

It appears that it doesn't happen every time, sometimes it happens several times in a row, and sometimes it's the opposite, but the problem has been noted. Thank you for the report.

simifor avatar Mar 11 '24 19:03 simifor