Proton: Spelunky 2 (418530)

[radriaanse]

Compatibility Report

• Name of the game with compatibility issues: Spelunky 2
• Steam AppID of the game: 418530

System Information

• GPU: AMD Radeon RX 5700 XT
• Driver/LLVM version: mesa-git 20.3.0_devel.128754.1588644543d
• Kernel version: 5.8.12-zen1-1-zen
• Link to full system information report as Gist: https://gist.github.com/radriaanse/dd6563ba9b41c89f440432f8f7dddd74
• Proton version: 5.0-9

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-418530.log

Symptoms

Game doesn't launch, after launching shows a black screen and exits.

Reproduction

Install game, launch.

[kisak-valve]

Hello @radriaanse, err:steamclient:create_win_interface Don't recognize interface name: SteamUtils010 looks like a line of interest from the log.

[radriaanse]

Hi @kisak-valve, found a thread over on steam that states it should work with proton-tkg 5.18.r3.g9acfa3b8.
FWIW I tested it and this seems to be the case, I can run the game without any problems after using the other runtime.

Is there any logging I can share that might explain the difference between these two version?

[anlsh]

From what I've seen, the only people that seem to be able to get the proton-tkg fix working are Arch users (from this reddit thread, one success on arch and 3 failures on Ubuntu/PopOS).

I'm using PopOS myself, and the proton-tkg fix isn't working (in fact it's slightly worse: with 5.09 I'll at least get a short-lived black screen but with this no window opens at all).

I'll try compiling proton-tkg on my machine and report back

Failure logs with proton-tkg and with proton 5.0.9

Not sure what command @radriaanse used to generate his system info (if you tell me I'll use it), but I'm on PopOS 20.04, 1050Ti mobile, nvidia drivers 440.100

[Nightmaresiege]

@anlsh Some enterprising folks have posted a guide to getting this to work in Ubuntu 20.04 - https://steamcommunity.com/app/418530/discussions/0/2930112548420911027/

It is not for the faint of heart.

[fartsniffer104]

It works on Arch because Arch has glibc 2.32. If you have glibc 2.31 installed you can use proton-tkg 5.15 which worked for me on Fedora. I also needed to change the version to Windows 10 using WINEPREFIX=~/.steam/steam/steamapps/compatdata/418530/pfx/ winecfg

[anlsh]

@Nightmaresiege Thanks for the reference! I've gotten things to work with their process using some slight modifications for PopOS (detailed in the thread)

EDIT: I've also uploaded my binaries here https://github.com/anlsh/wine-tkg-git/releases/tag/5.18.r3.g9acfa3b8. They've worked for at least one other person so far

[radriaanse]

@anlsh I'm indeed using Arch so I had no issues there, the system info comes from Steam itself: Help -> System information

[DrWursterich]

There is also a precompiled version for Ubuntu: https://github.com/pgroudas/wine-tkg-git/releases/tag/5.18.r3.g9acfa3b8
Worked for me out of the box.

[makoConstruct]

After the game was updated, the game still doesn't launch, I no longer get a shortlived black screen, and I still get the "Warning: Windows version not supported [Ok]" window. This window was always a common symptom: https://www.protondb.com/app/418530

[mozo78]

It runs out-of-the-box with Wine 5.18 set to Windows 10. If the prefix is set to Win 7 the game still runs but "Windows version not supported" message appears at start.

[fartsniffer104]

Has anyone looked into why achievements aren't working? Would it require an update to the game or a patch to proton to fix them?

[anlsh]

@fartsniffer104 See one of the developers' posts here: I'm guessing it will require the devs to update the game to fix whatever bug exists on their side.

On the plus side, it seems the bug affects some windows users too, so I'm guessing a fix will come out eventually

[moben]

Running Spelunky 2 in a wine prefix with regular Steam for Windows installed, unlocking achievements works.

When Steam is installed in the prefix, starting Spel2.exe will actually start Steam (in wine) first. I believe that might be the reason why it fails in proton, the steam.exe that is running there might not behave 100% the same as Steam for Windows (e.g. it can't download and start games as it's only a bridge to the Linux Steam to trigger achievements and such.

[bruno-fs]

Running Spelunky 2 in a wine prefix with regular Steam for Windows installed, unlocking achievements works.

When Steam is installed in the prefix, starting Spel2.exe will actually start Steam (in wine) first. I believe that might be the reason why it fails in proton, the steam.exe that is running there might not behave 100% the same as Steam for Windows (e.g. it can't download and start games as it's only a bridge to the Linux Steam to trigger achievements and such.

Following @moben approach I could unlock some achievements. Good job mate!

[aeikum]

Hello. The Proton 5.13 release should fix achievements and other Steam client integration for Spelunky 2.

[makoConstruct]

That's wonderful news, but still doesn't launch for me. Log: https://gist.github.com/makoConstruct/27a5283dc40e7e965439ebe679782bec

Edit: updated my graphics drivers and it works!

[Thraix]

Does not launch for me either, just instantly crashes on launch

[Rognin]

Doesn't work for me either, on launch it says "running" for a while and then crashes

[radriaanse]

It works here just fine when switching to 5.13 from the proton-tkg build that was previously also working for me.
Achievements are now also rewarded, thanks @aeikum !

[fartsniffer104]

Achievements are now unlocking for me.

@Thraix @Rognin Try WINEPREFIX=~/.steam/steam/steamapps/compatdata/418530/pfx winecfg and setting "Windows Version" to "Windows 10". When it is set to Windows 7 the game does not run for me.

[Thraix]

@fartsniffer104 Do I put that into the game launch options or in a .profile file which is loaded on login? And where do I set the the Windows version? I dont think there is such an option in the steam game properties. Currently don't have my computer to test this, but thanks for the reply. Will try to test in in about 2 hours maybe.

[Rognin]

Achievements are now unlocking for me.

@Thraix @Rognin Try WINEPREFIX=~/.steam/steam/steamapps/compatdata/418530/pfx winecfg and setting "Windows Version" to "Windows 10". When it is set to Windows 7 the game does not run for me.

I tried to do that and got the following error:
wine client error:0: version mismatch 490/547.
Your wineserver binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?

Do you have any idea what might be causing it and how to fix it? As far as I'm aware I'm not using wine to run any programs at the moment.

[Cheogh]

Tharix you need to paste it into a terminal emulator like gnome-terminal.
Rognin it sounds like you need to update wine, using winecfg will use the system installed version of wine.

[Thraix]

ah, didn't realize this was a persistent config change, so I thought it would need more work. However this did not solve my problem, the game still instantly crashes (no screen or nothing, just says preparing to launch and then it dies).
This is the log from running steam from a terminal: https://gist.github.com/Thraix/75442e837a1d79ba58c22864169bce5b

[kisak-valve]

Hello @Thraix, x86_64-linux-gnu-capsule-capture-libs: code 2: Missing dependencies: Could not find "libnvidia-fatbinaryloader.so.435.21" in LD_LIBRARY_PATH "", ld.so.cache, /lib or /usr/lib
pressure-vessel-wrap[4103221]: Child process exited with code 1 in your log sounds similar to https://github.com/ValveSoftware/steam-runtime/issues/275

[Thraix]

OMG! thank you! seemed like I had an old version of opencl which somehow caused problems. Now the game is running and achievements are being unlocked!

[Thraix]

While I got it working mostly perfectly, there is still a problem with my xbox 360 controller not working if it disconnects whilst the game is running. It works fine if the controller is connected before I start the game, but if it disconnects, it wont reconnect again and I have to restart the game. This problem was not present in proton-tkg 5.18. But thanks for the achievement fixes anyways :smile:

[smcv]

there is still a problem with my xbox 360 controller not working if it disconnects whilst the game is running

This is a known issue with versions of Proton that run in a container runtime (currently only 5.13). Processes inside the container can't see input device hotplug events outside the container. A fix is in progress.

[MrAlcoholicFox]

Hello, I am using Proton-tkg 5.18.r3.g9acfa3b8.release, the game is running fine but I can't unlock any achievements. Can anyone help

[kisak-valve]

Hello @MrAlcoholicFox, please retest with mainline Proton 5.13-1. Looks like that third party Proton build is older (date it became available) than Proton 5.13.

[MrAlcoholicFox]

Hello @MrAlcoholicFox, please retest with mainline Proton 5.13-1. Looks like that third party Proton build is older (date it became available) than Proton 5.13.

I have tested with that and it doesn't launch the game. That's why I moved to the third party version

[daveknippers]

Hi. I'd like to share my experiences trying to get Spelunky 2 to work under proton 5.13-1.

I get a black screen on starting the game, then nothing happens. I get some music, but it just seems to be an ambiance loop. I'm forced to stop the game in steam.

system information report: https://gist.github.com/daveknippers/e4ff236ad9994d1e283a9cab16ec3d8e
proton log: https://gist.github.com/daveknippers/d53ba27a7147d5ac83d2a2e91b9760ea

Here's something I find very odd about this: the proton log suggests it's trying to do something with my intel integrated graphics card.

info:  D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info:  D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
info:  Device properties:
info:    Device name:     : Intel(R) UHD Graphics 630 (CFL GT2)
info:    Driver version   : 20.2.0

while this system has both an intel integrated card and an nvidia card, the intel card is disabled. i don't need to do anything with prime offloading or bumblebee or anything else, everything should just run under the nvidia card. there isn't a single reference to nvidia in the proton log file.

thank you for your time

edit: added the output from:
vulkaninfo https://gist.github.com/daveknippers/f5d571d0cbe39c5db1b10dc6d37ff4b4
Xorg.0.log https://gist.github.com/daveknippers/b3746006870d6f833ce846eb8e5cba06

[MrAlcoholicFox]

I got the same thing and I fixed it by installing a third party forked version of Proton and ran it with that

[kisak-valve]

@MrAlcoholicFox, please add PROTON_LOG=1 %command% to the game's launch options, run the game with Proton 5.13-1, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

@daveknippers, your Intel chipset is definitely not disabled, the laptop's display is hardwired to it. There's a known Pressure Vessel issue with vulkan layers noted in https://github.com/ValveSoftware/Proton/issues/4289 which might be having a hard time with your system configuration. You could try temporarily making the Intel Vulkan driver unavailable with something like sudo mv /usr/share/vulkan/icd.d/intel_icd.x86_64.json /usr/share/vulkan/icd.d/intel_icd.x86_64.json.disabled and check if that has an effect.

[daveknippers]

@daveknippers, your Intel chipset is definitely not disabled, the laptop's display is hardwired to it. There's a known Pressure Vessel issue with vulkan layers noted in #4289 which might be having a hard time with your system configuration. You could try temporarily making the Intel Vulkan driver unavailable with something like sudo mv /usr/share/vulkan/icd.d/intel_icd.x86_64.json /usr/share/vulkan/icd.d/intel_icd.x86_64.json.disabled and check if that has an effect.

you're actually a genius. that worked flawlessly. if i don't intend on using vulkan on intel should i leave that disabled?

[kisak-valve]

That's at your discretion. Please be aware that was only the 64 bit variant for the test and it'll get re-enabled next time you re-emerge mesa.

[daveknippers]

That's at your discretion. Please be aware that was only the 64 bit variant for the test and it'll get re-enabled next time you re-emerge mesa.

thank you, i can work with that.

[MrAlcoholicFox]

@MrAlcoholicFox, please add PROTON_LOG=1 %command% to the game's launch options, run the game with Proton 5.13-1, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

I literally try again and it starts working. I think it was because I was using no_d3d11 and I switched to PROTON_USE_WINED3D=1 %command%. Thanks anyways tho. Achievements are working as well

[MrAlcoholicFox]

It runs a lot slower then using the forked version tho

[jmc-figueira]

Hi!

I am also suffering from the issue where the game appears to load, only to silently fail without even so much as a window appearing on screen. The log (steam-418530.log) does not seem to be of much help.

My system information is as follows: https://gist.github.com/jmc-figueira/a1075b86c29263fb991d268678e3b421

[aeikum]

@jmc-figueira Looks like you have something non-standard going on with your Steam installation, which may be interfering with the container. /home/jmc-figueira/.steam/debian-installation is not a normal path.

[smcv]

/home/jmc-figueira/.steam/debian-installation is not a normal path

This should be harmless.

It's the equivalent of ~/.local/share/Steam in the Debian package for Steam (unofficial from Valve's perspective, official from Debian's perspective). Historically that package used ~/.steam, which was actively breaking games and Steam features, and its maintainer was unwilling to switch to ~/.local/share/Steam; using ~/.steam/debian-installation was a compromise to fix the broken situations while keeping the maintainer happy.