Open voidpointertonull opened 7 months ago
Tried it on my oled deck with Experimental, it just gets stuck on the spinning steam logo for like 10-30 seconds before silently exiting out to the game library page.
It takes quite a while to exit likely because it's making massive crash dumps.
Actually I wanted to include that in the original post, just had too much going on already. Beware of /run filling up after multiple runs! Took me a while to figure out that "out of space" really just meant that, and it wasn't an obscure error message as implied by some search results. Didn't expect crash dumps to land there in tmpfs with an apparently 10% of total memory limit on Ubuntu with Flatpak at least.
A Proton developer has informed me that the game runs with an internal test version of Proton 9. So we can expect the game to work once that is released. Furthermore, one of the game developers has also expressed interest in releasing a native Linux version of the game at a later date.
In the meantime, it's possible to run the game outside of Steam (without Steam achievements / cloud save) with the Linux version of NW.js, by installing it with your package manager.
E.g. Archlinux: yay -S nwjs-bin
Then launch the game from the terminal or a script:
nw "$HOME/.local/share/Steam/steamapps/common/Sheepy A Short Adventure/package.nw"
Ran it on Fedora 39 with Wine 9.2 and it works just fine with that. So Proton 9 will likely fix its issues.
Works fine with Wine 8.21 (on Arch). No luck with proton thoug.
Hello @ading2210. your comment was removed because it's a copyright violation (A MrSuicideSheep™ Project. Sheepy: A Short Adventure © Copyright Seeking Blue Records™ Inc. 2021. All rights reserved.
on the Steam page).
Apparently a relevant fix got into Proton Experimental already, bleeding-edge not even required. Just started the game, was pleasantly surprised to get into the menu, but didn't play, so consider this more of a heads up than confirmation of everything being fine.
Compatibility Report
System Information
I confirm:
steam-1568400.log
Symptoms
Attempted everything Steam offers from Proton 4.2-9 to Proton Experimental [bleeding-edge]. A window may or may not pop up for a short time when starting the game, but there's always a "crash".
The game seems to be based on Chromium ("nwjs" apparently). The crash appears to be misleading, it seems to be always some kind of failed check aborting the main process. In the uploaded log, delay_load_failure_support.cc bails apparently on a DLL load failure based on some Windows-specific callback, but I'm not familiar enough with the details to judge it well, the Chromium source was just helpful in figuring out a few bits and pieces.
Proton 7.0 appeared to be somewhat more promising as it failed elsewhere which could be determined to be a problem with bcryptprimitives.dll missing. Providing that lead to sandboxing checks failing. Using --no-sandbox led to the failure of api-ms-win-core-realtime-l1-1-1.dll not having a function implemented yet, but couldn't even source a replacement for that, more up to date Wine and Proton packages don't even seem to have the file at all.
Older Proton versions fail with a not implemented syscall problem, so likely those are too old already to be worthy to even look for regressions.
Also attempted to get it going on another setup with an Intel iGPU, but that exhibited the same symptoms. Others apparently got somewhat further before the recent transition from beta to public availability: https://www.protondb.com/app/1568400
Attempted to replace the files with various nwjs releases, both Windows and Linux, but that direction was just a whole another can of worms. Apparently other nwjs related bug reports are not suffering from this specific problem. Didn't succeed with libEGL.dll removal, PROTON_USE_WINED3D=1, or dxvk.conf DX version degradation, all which helped in some other cases.
Reproduction
Just start the game.