Having a similar issue with proton 5.0-9 where the glyph launcher works fine but when i launch trove it just launches a window, black screen, and after like 5 seconds at most it closes
system info report: https://gist.github.com/grian32/4fa1d45269cebe97565124eeb8f4bd98
steam log: https://gist.github.com/grian32/68c3106634184ace9f6b7b4716e08f9f

Hello @grian32, Proton uses DXVK to translate DirectX 9/10/11 to Vulkan, and the Intel Sandybridge chipset in your system does not support Vulkan, which leads to the failure you're seeing.

You might get lucky by adding PROTON_USE_WINED3D=1 %command% to the game's launch options which tells Proton to use wine's DirectX to OpenGL render path, but this comes with a significant performance penalty and is not considered supported.

Thanks! I'll try that.

Hi. I also tested this game and although PROTON_USE_WINED3D=1 %command% makes it work on my hardware, this is not an ideal solution. I am running 10th gen intel and it still wont work

steam-304050.log

https://gist.github.com/camatthew/c05e1ff19ccd97bab52859154b8f56f3

I see you have the amdvlk (amd vulkan driver) 32bit package installed and also nvidia vulkan driver (nvidia-utils)
Can you see if it changes anything when you remove amdvlk to be sure it isn't messing with you?

sudo pacman -R lib32-amdvlk

Alternatively if you are not using them for anything specific you can also remove nvidia-utils. Unless you have a hidden nvidia gpu i'm not seeing.

sudo pacman -R nvidia-utils lib32-nvidia-utils

Edit: Ninjaed by kisak :grin:

proton experimental (as of today), the game launches with black screen (launcher works tho), settings button in launcher immidietaly closes the popup which does not allow me to do anything

@KaspianDev proton log please :slightly_smiling_face:
Also a steam system information report (Steam -> Help -> System Information). Attach it as a github gist or text file

Proton 9 (beta) + Proton Experimental

The Glyph launcher works but the game crash immediately

steam-304050.log

Hello @MrNessuno, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

info: Required Vulkan extension VK_KHR_surface not supported looks like a key detail in your Proton log. DXVK is not able to finish starting up.

Here is my runtime diagnostic. And... well i re-tested with Proton 7 clearing the compactdata folder and I have the same problem, so isn't the version but something on my pc I guess

https://gist.github.com/MrNessuno/54efbb7c7f34cdd2bd5452ef64505d43

more info added:
vulkaninfo | grep VK_KHR_surface
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1

Thanks, it looks like you do not have a 32 bit Vulkan driver installed. I'd add the lib32-vulkan-radeon system package and retest.

ehm, ty ^^ didn't know 32bit mesa packages were required for some games.

well, new report then:
Proton Experimental + Proton 9 (Beta)

Still unable to play correctly, interacting with Inventory or Marketplace cause a crash like Proton 8:

steam-304050.log

Log with Proton 7 working fine:
steam-304050.log

@MrNessuno Thank you for the report! We saw slightly different behavior from what you listed in your report, but we hope that the crash you reported is fixed in current Proton 9.0-experimental. Please let me know if you are still seeing the crash with experimental-9 :)

@MrNessuno Thank you for the report! We saw slightly different behavior from what you listed in your report, but we hope that the crash you reported is fixed in current Proton 9.0-experimental. Please let me know if you are still seeing the crash with experimental-9 :)

With Proton Experimental everything seems to work fine again ^^

Of note, Trove has an issue with occasionally crashing and taking steam down with it. On steam deck this results in around 30-60s of black screen before the watchdog kicks in and restarts steam. I encounter this issue around 4-5 times a day with no reliable method to reproduce other than playing for an extended time. Latest example occurred on Proton 9.0-3, and has occurred on both LCD and OLED steam decks.

On rare occasions, after such a steam restart, the connection to the server is unnaturally slow, causing 5 minute login times and disconnects when changing areas. Rebooting the steam deck fixes this issue. Considering the symptoms, I assume -that- issue is a SteamOS issue that happens to exhibit itself through Trove more blatantly than most games.

EDIT: The second issue is a steam client issue. Disregard for this issue. The crash issue mentioned logs in steam as out of memory though, which is strange since it is never anywhere near the memory limit. Must be a very sharp memory leak or something.

I've been testing it out a bit, and I'm more confused than I was. Limiting Trove's RAM access via systemd-run doesn't stop the out of memory crash, but the crash also doesn't seem to occur when it's actually out of memory. I've attached a btop graph of the memory during the crash, it never got anywhere near full. Also, it seems the wait for steam to start back up may actually be a wait for winedevice to shut down.

EDIT: Confirmed SSHing in and running pkill -9 winedevice will cause steam to immediately start back up. Not doing so can take multiple minutes.

New PTS Update with XIGNCODE3 Anti-Cheat broke the game.
This the error:

Gemini, so AI WARNING, told me that Proton (and the Wine translation layer it is built on) has not yet implemented the WSCEnumProtocols32 function inside its version of WS2_32.dll. It has the standard WSCEnumProtocols function, but it is missing the 32 variant.
Is this true?

Replying to https://github.com/ValveSoftware/Proton/issues/2986#issuecomment-4651060536

Missing export for WSCEnumProtocols32, which is present in the Windows' WS2_32.dll.
An alias in wine/dlls/ws2_32/ws_32.spec will fix this specific issue.
I believe the alias is fine, because Wine doesn't have separate catalogs either way.

Credits go to lilly0tsuki from Discord

The steps I took to build ws2_32 with WSCEnumProtocols32 added. I don't know if it's needed to match the wine/proton version for the one you're using, but I did this for GE-Proton10-34.
For build dependencies check: gitlab(.)winehq(.)org/wine/wine/-/wikis/Building-Wine

1. git clone GITHUB_URL/ValveSoftware/wine.git
2. cd wine
3. git checkout 1729f00 (version used by GE-Proton10-34)
4. Use the editor of your choice for ./dlls/ws2_32/ws2_32.spec and add @ stdcall WSCEnumProtocols32(ptr ptr ptr ptr) WSCEnumProtocols
5. ./autogen.sh
6. ./configure --enable-archs=i386,x86_64
7. make -C dlls/ws2_32
8. Copy over the files:

cp dlls/ws2_32/i386-windows/ws2_32.dll ~/.local/share/Steam/compatibilitytools.d/GE-Proton10-34/files/lib/wine/i386-windows/ws2_32.dll
cp dlls/ws2_32/x86_64-windows/ws2_32.dll ~/.local/share/Steam/compatibilitytools.d/GE-Proton10-34/files/lib/wine/x86_64-windows/ws2_32.dll

1. Play

@MrNessuno at what point is it supposed to crash? I didn't need to do anything to get ingame with proton experimental, are you supposed to do anything specific while ingame to trigger the issue?

@MrNessuno at what point is it supposed to crash? I didn't need to do anything to get ingame with proton experimental, are you supposed to do anything specific while ingame to trigger the issue?

Try the PTS version with the new Anti-Cheat, press Play, enjoy the crash

The PTS should now work with the Proton - Experimental bleeding edge branch (beta branch for the experimental tool). The upstream fix is different from the dll hack mentioned in the comment above - please let me know if you have any connection issues with the PTS on the bleeding-edge experimental branch.