S&box (590830)

[matty45]

Compatibility Report

• Name of the game with compatibility issues: S&box
• Steam AppID of the game: 590830

System Information

• GPU: AMD ATI Radeon RX 5700 XT
• Driver/LLVM version: Mesa 21.1.3
• Kernel version: 5.12.14-artix1-1
• System Info
• Proton version: 6.3-5

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

Symptoms

Game launches fine but multiplayer does not work at all.

Reproduction

Launch the game and try to connect to server either via the console or using the find game feature.

[matty45]

Update: Changed Proton version to 6.5-5 and game runs fine now, however cannot connect to anyone in multiplayer. Game uses steam p2p.

[kisak-valve]

Hello @matty45, can you also share a Proton log with Proton 6.3 and trying to use multiplayer?

[matty45]

Hello @matty45, can you also share a Proton log with Proton 6.3 and trying to use multiplayer?

steam-590830.zip @kisak-valve

[kisak-valve]

Thanks, possible line of interest from the log: err:steamclient:create_win_interface Don't recognize interface name: STEAMTV_INTERFACE_V001

We've seen that before with Half-Life:Alyx, but the lack of the interface didn't have a substantial effect on the game. I have my doubts that it's a good hint here as well.

[jas0n098]

The lack of STEAMTV_INTERFACE_V001 is what's causing this. The game calls SteamInternal_FindOrCreateUserInterface on this interface, which fails, making the game print CNetworkSystem::Init() m_SteamAPIContextClient.Init ( ) failed (no Steam?). This results in Steam's P2P feature not functioning and thus breaking multiplayer.

[Creekie1337]

For whatever reason I am not even able to start a game (singeplayer - 1 player), the game just crashes. Main menu works and renders fine so I'm not sure what the issue is. RX 570, Proton 6.3-6.

steam-590830.zip

[kisak-valve]

Hello @MilkGames, these look like some lines of interest from the log:

err:steamclient:create_win_interface Don't recognize interface name: STEAMREMOTESTORAGE_INTERFACE_VERSION016

err:steamclient:create_win_interface Don't recognize interface name: SteamInput005

Assertion failed: func, file ../src-wine/dlls/dbghelp/symbol.c, line 397

[kisak-valve]

ec16f4c5c93607aa4ccf784b7a57d579d496b87b looks like it adds those interfaces. Please retest with Proton Experimental.

[Creekie1337]

Confirmed fixed on Proton Experimental, multiplayer and singleplayer both work fine.

[xDShot]

Doesn't start steam-590830.log

[xDShot]

nwm, re-verifying proton experimental cache and reoving compat data fixed

[Okxa]

Seems to get stuck at the facepunch logo. With proton experimental.

Log has atleast these sort of things:

12590.693:0128:01f8:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xdb9afd8c,4,(nil))
12592.217:0128:02e8:err:ntdll:RtlpWaitForCriticalSection section 0000000104630618 "?" wait timed out in thread 02e8, blocked by 02dc, retrying (60 sec)

full log:

steam-590830.log

[mastopgunaf]

The game doesn't launch, it gets stuck on the Facepuch logo for me too. I'm using Proton Experimental. Verified Proton's file integrity and deleted the compatdata folder. I also noticed that it sometimes produces a much larger log (>100MB in size) because it goes into an infinite loop somewhere. Most of the time though it gets stuck on RtlpWaitForCriticalSection timeout:

13607.924:0030:0048:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x1a1fd8c,4,(nil))
13607.928:0030:00e0:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x4a9fd8c,4,(nil))
13607.928:00d4:00f8:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0x2c4fd8c,4,(nil))
13608.620:010c:0150:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xbeaffd8c,4,(nil))
13608.620:010c:0154:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xc041fd8c,4,(nil))
13608.620:010c:0158:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xc052fd8c,4,(nil))
13608.620:010c:015c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xc063fd8c,4,(nil))
13608.620:010c:014c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xbe9efd8c,4,(nil))
13608.634:010c:0160:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xc1f5fd8c,4,(nil))
13608.638:010c:0164:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xc3b0fd8c,4,(nil))
13608.649:010c:0168:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xc570fd8c,4,(nil))
13608.660:010c:016c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xc730fd8c,4,(nil))
13608.686:010c:0170:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xc9f2fd8c,4,(nil))
13608.690:010c:0174:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xca03fd8c,4,(nil))
13608.707:010c:0178:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xca14fd8c,4,(nil))
13608.733:010c:017c:trace:seh:NtQueryInformationThread (0xfffffffffffffffe,12,0xca25fd8c,4,(nil))
13610.297:010c:026c:err:ntdll:RtlpWaitForCriticalSection section 000000012A680618 "?" wait timed out in thread 026c, blocked by 0274, retrying (60 sec)
13610.297:010c:0248:err:ntdll:RtlpWaitForCriticalSection section 000000012A680618 "?" wait timed out in thread 0248, blocked by 0274, retrying (60 sec)
13610.297:010c:0254:err:ntdll:RtlpWaitForCriticalSection section 000000012A680618 "?" wait timed out in thread 0254, blocked by 0274, retrying (60 sec)
13610.297:010c:01a0:err:ntdll:RtlpWaitForCriticalSection section 000000012A680618 "?" wait timed out in thread 01a0, blocked by 0274, retrying (60 sec)
13610.297:010c:01a4:err:ntdll:RtlpWaitForCriticalSection section 000000012A680618 "?" wait timed out in thread 01a4, blocked by 0274, retrying (60 sec)
13610.297:010c:0244:err:ntdll:RtlpWaitForCriticalSection section 000000012A680618 "?" wait timed out in thread 0244, blocked by 0274, retrying (60 sec)
13610.297:010c:0260:err:ntdll:RtlpWaitForCriticalSection section 000000012A680618 "?" wait timed out in thread 0260, blocked by 0274, retrying (60 sec)
13610.297:010c:0270:err:ntdll:RtlpWaitForCriticalSection section 000000012A680618 "?" wait timed out in thread 0270, blocked by 0274, retrying (60 sec)
13610.297:010c:0194:err:ntdll:RtlpWaitForCriticalSection section 00000000BBE304D8 "?" wait timed out in thread 0194, blocked by 0148, retrying (60 sec)

Full log: steam-590830.log

Kernel version: 5.13.19_1

[alasky17]

Hi folks - the crashing/hangs should be fixed with the latest experimental release (experimental-6.3-20211027). Please report back on this thread (with logs) if you continue to get consistent hanging or crashes :)
Pinging everyone who commented since there aren't that many - @mastopgunaf @Okxa @xDShot @MilkGames @jas0n098 @matty45

[Creekie1337]

Looks like it works fine for me.

[mitsuruu]

After an update to the game today, running under Experimental seems to crash the game instantly upon loading any maps/gamemodes. If you run into an SSL error when connecting, change the Windows version in the prefix to Windows 7, as the default Windows 10 seems to cause those issues.

[ShadowBrian]

Doesn't seem to be working on the Steam Deck as of today, getting API errors likely related to SSL, no idea how to "change the windows version prefix" on deck, assuming that'd even fix it

Edit: got it working thanks to someone on the S&Box discord, so in the end I needed to install "protontricks", set the game to compatibility mode (proton experimental), run it in desktop mode (which generates all the required files), and execute flatpak run --branch=stable com.github.Matoking.protontricks 590830 win7 with it all installed on the main drive. Linux is great you guys....

[SupinePandora43]

S&Box editor doesn't have any access to files other than required to run.

[alasky17]

@ShadowBrian @Cameron-Stuart and anyone else - the most recent experimental update should have fixed all of the SSL errors with win10 prefixes. I would greatly appreciate it if y'all could switch the prefix back to win10 and let me know if you are still seeing any SSL errors when trying to load into various games etc.

[mitsuruu]

@ShadowBrian @Cameron-Stuart and anyone else - the most recent experimental update should have fixed all of the SSL errors with win10 prefixes. I would greatly appreciate it if y'all could switch the prefix back to win10 and let me know if you are still seeing any SSL errors when trying to load into various games etc.

I've updated to Proton Experimental about 5 minutes ago and started with a fresh prefix, and managed to get it working. It still shows the SSL errors, but the content itself loads. Not sure exactly what's actually erroring out, but as you can see it's loading the list of gamemodes and it also lets me download content and load into games.#

[ShadowBrian]

Works flawlessly on experimental for me, no SSL issues or errors at all. Only thing coming up in the console is "unknown command or convar 'tcmd' !" which I doubt is a proton issue.

[5FB5]

Log for my problem posted above by matt Log.log

[jas0n098]

Log for my problem posted above by matt Log.log

Install protontricks and run protontricks 590830 d3dcompiler_47 to work around it until wine's own d3dcompiler_47 is fixed.

[5FB5]

Log for my problem posted above by matt Log.log

Install protontricks and run protontricks 590830 d3dcompiler_47 to work around it until wine's own d3dcompiler_47 is fixed.

It helps launch the game, but it crashes on loading

Updated log: Log.log

[lannior]

The game doesn't launch for me. Experimental - steam-590830-experimental.log 7.0-3 - steam-590830-7.0-3.log

[SupinePandora43]

How to allow full filesystem access?

[kisak-valve]

Hello @SupinePandora43, see the discussion on https://github.com/ValveSoftware/steam-runtime/issues/470.

[5FB5]

Well, now it works on a different game mods

[CrezyDud]

it only crashes on sanbox servers; S& Blox, spire and tf2 work fine Heres my log Log.log

[CrezyDud]

(may be because of rendering, since it sends information to the server fine)