Gauntlet Slayer Edition: Required launch options and no controller support (258970)

[John-P]

Gauntlet Slayer Edition plays really well but has a few minor issues:

• Hangs when the quit button on main menu is pressed.
• Minor lighting glitches, mostly just on the first campaign level.
• Controllers are not recognized (tested PS3 edit: and Xbox 360) says 'no xinput controller detected'.
• No audio out. Although, this may be because I am unable to tab out. A few games send audio out to the wrong device for me (Kubuntu 18.04) and I often have to tab out to fix it.

[P4NCH1]

In my SteamOS PC works fairly well by defining some launch parameters:

PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=1 %command%

Without those it immediately closes itself or launches into a black screen.

System Information

• GPU: AMD Radeon R7 Kaveri 1GB
• Driver/LLVM version: Mesa 17.2.4/5.0.0
• Kernel version: 4.14.0-0.steamos.81-amd64
• Full system information: here
• Proton version: 3.7-6

By the way, is Gauntlet. Title is wrong :)

[John-P]

Fantastic! Those launch options fixed most of the problems I was having. After I successfully played for 20 minutes on first launch it was crashing on launch after that. Odd that it worked first time with no launch options. Also, it fixed the crash on clicking quit. Controller support is still not working though. Fixed the typo in the title.

[P4NCH1]

@John-P , make sure that Steam is detecting well your gamepad (Settings > Controller Settings). At least my generic PS3-like gamepad works fine for this game.
I tried letting SteamOS start on BPM (Big Picture, the default mode) and is all working fine too.

[John-P]

@P4NCH1 Hmm. Both controllers appear in steam settings and work for games with linux support but not this one in proton unfortunately. When I click 'controller' in game it says 'No gamepad detected. Only XInput compatible controllers are supported.'

[ghost]

Game menu freezes up after a couple seconds without PROTON_NO_ESYNC=1 set. Otherwise I'm having no trouble running at max detail on a GTX980 (396.54) on Arch Cinnamon using kernel/bluez bt DS3 driver.

@P4NCH1

PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=1 %command%

Without those it immediately closes itself or launches into a black screen..

Should not need or use WineD3D11. Performance is pretty terrible. I suspect your system is not configured to suppport Vulkan? I believe Kaveri APUs should support it hardware-wise, can you confirm working native Vulkan support?

[P4NCH1]

@SeeK-ntr0py , if you are talking to me, I actually don't know how to check if my OS is capable to use Vulkan or not over this hardware, but I can say that I'm pretty tired of having to change things everywhere to get games work on an OS that should be working like a spacecraft over the other ones in this topic. Day to day I'm getting more and more desapointed on Valve's care over SteamOS.

Getting back to topic, can you tell me a way to check if SteamOS 2.0 is compatible with Vulkan on my hardware?

[ghost]

@P4NCH1 sorry, yeah, quoted wrong person heh. I don't really use SteamOS, but I believe vulkaninfo should be available via the vulkan-utils ( or possibly vulkan-tools) package. check the output from vulkaninfo and it should tell you if there are any problems.

You might also try vktest as building it might solve any missing dependencies. Finally, I know there are at least a few native-Linux Vulkan titles on Steam like Mad Max and Rise of the Tomb Raider which might be interesting to try if you own any them.

[John-P]

@SeeK-ntr0py I have Mad Max but PS3 and Xbox 360 controllers don't work there for me. They work with Tricky Towers though. I also have Tomb Raider (not rise of) which is also linux native but have not tried controllers with that yet.

[P4NCH1]

@SeeK-ntr0py Late answer but this weekend I've switched to (my fallback OS) Linux Mint and after adding Padoka's ppa my system should now support Vulkan :) In the week I'll test this game again and one of the native-Linux Vulkan tittes that you mentioned, I have Rise of the Tomb Raider but never test it until now cause I'm still ending the previous one.

[liberodark]

Online and xbox controller work with 3.16-4 Beta and https://github.com/simons-public/protonfixes

[FurtadoPires]

Can't start the game with any available proton version, it just closes after "preparing to launch".

My machine

Proton log

[kisak-valve]

Hello @FurtadoPires, your log hints that you may have encountered #944 or similar.

[FurtadoPires]

Hello @FurtadoPires, your log hints that you may have encountered #944 or similar.

@kisak-valve this is probably my case since we had rule change in the TZ rule this year (our current president abolished DST) and I'm indeed using America/Sao_Paulo.

So can I expected this to be fixed once Proton hits 4.13+?

[kisak-valve]

Based on #944, it would be a good idea to retest when Proton 4.11-3 becomes available.

[FurtadoPires]

Based on #944, it would be a good idea to retest when Proton 4.11-3 becomes available.

Tested with 4.11-3, same problem unfortunately.

[FurtadoPires]

As requested by @kisak-valve

Log with proton 4.11-3. Still crashing at launch.

[FurtadoPires]

Managed to launch after use PROTON_USE_WINED3D11=1 %command%

[kisak-valve]

Since that env variable made a difference, please verify you have the mesa-vulkan-drivers and mesa-vulkan-drivers:i386 packages installed with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386.

[FurtadoPires]

Since that env variable made a difference, please verify you have the mesa-vulkan-drivers and mesa-vulkan-drivers:i386 packages installed with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386.

It was missing, now it's working out of the box.

[sanawu]

Does NOT work with Proton 5.13 on Linux Mint 20 with 390 NV proprietary drivers (no later drivers can be used on my GPU)

Game launches then terminates after blank window

I generally do not use layers like WINE, but I thought I would try some games I have on Steam, and so far 2 out of 2 in a row have not worked, I certinally will NOT be purchasing any game that is not NATIVE to Linux after this experience and will let the old games be just that, old, and never again purchase a Steam Play only game, if I get the ones I have to work, great, but that's it, no more new ones

[FurtadoPires]

Does NOT work with Proton 5.13 on Linux Mint 20 with 390 NV proprietary drivers (no later drivers can be used on my GPU)

Your ancient drivers might be the problem, try to start the game using PROTON_USE_WINED3D=1 %command% and see if it change something

[kisak-valve]

Hello @sanawu, sounds like you have a Fermi generation nVidia video card. Proton uses DXVK to translate DirectX 9/10/11 to Vulkan and there is no Vulkan driver support available for that hardware generation, making it unsupported by Proton.

As @FurtadoPires, you may get lucky by setting PROTON_USE_WINED3D=1 %command% in the game's launch options, which tells Proton to use wine's DirectX to OpenGL render path. This comes with a significant performance penalty and is not considered supported.

[sanawu]

Does NOT work with Proton 5.13 on Linux Mint 20 with 390 NV proprietary drivers (no later drivers can be used on my GPU)

Your ancient drivers might be the problem, try to start the game using PROTON_USE_WINED3D=1 %command% and see if it change something

@FurtadoPires

It is the only drivers available on Linux for my GPU, that is how it is and this game does not require the latest GPU to run it runs on Windows more than fine, updating GPU's in laptops isn't exactly easy

Maybe the driver story will get better when GNU/Hurd is released with a proper driver model (since monolothic kernels are so ancient, to use your terminology)

what is %command% we just use that?

@kisak-valve

UPDATE: I just used that, it seems to work but it won't let me flip between other app windows running it always jumps to the foreground so flipping between desktop/apps and the game is not possible (reference #358 )