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:

• that I haven't found an existing compatibility report for this game.
• 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]

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

[Creekie1337]

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

[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

[Weldify]

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?

[SupinePandora43]

using s&box native vulkan

@Kaydax, how?

[Kaydax]

using s&box native vulkan

@Kaydax, how?

-vulkan

[Kaydax]

using s&box native vulkan

@Kaydax, how?

-vulkan

For anyone reading this for steam deck, currently native vulkan is in heavy development and should not be used as on both windows and linux, s&box has weird issues with amd as well so using it just breaks more things
(Image taken from the s&box discord)

[WapaMario63]

Anyone else have the game consume 10GB of RAM along with very heavy CPU usage just by being on the menu? RAM usage keeps on increasing overtime so there might be an insane memory leak going on. My guess is on the graphics API side since the workaround to fix this is with the -vulkan option, but since that implementation is brand new, some materials are still broken (mainly transparent materials like leaves and windows, but also some character models).

Here are my proton logs, they seem identical at first glance so I have no idea if it can help:
DXVK
Vulkan

Proton 8.0-2, Radeon RX 6800, Ryzen 2700X

[WapaMario63]

Tools no longer launch after a game update and crash the exact moment "Bootstrap..." is shown in the splash window. Happens on Proton 8.0-2 (including the 8.0-3 pre-release), Proton Experimental and GE Proton 8-6.

Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at NativeEngine.EngineGlobal.Plat_EndJumpList(IntPtr)
   at Sandbox.JumpListBuilder.Dispose()
   at Sandbox.JumpListManager.BuildJumpList()
   at Sandbox.LocalProject.Initialize()
   at Sandbox.LocalProject.Startup()
   at Sandbox.Engine.Bootstrap.Init()
   at Managed.SandboxEngine.Exports.SandboxEngine_Bootstrap_Init()
   at NativeEngine.EngineGlobal.SourceEngineInit(CMaterialSystem2AppSystemDict)
   at Sandbox.SourceEngineApp.Initialize()
   at Sandbox.Program.LaunchGame()
   at Sandbox.Program.Main()

Logs: steam-590830-8.0-2_toolscrash.log (DXVK)

Next thing that now happens is that rendering of blend materials flicker, I though it was an issue with my own map at first, but it happens on every other map that makes use of that type of material as well. Screenshot on Construct:

Also, the -vulkan option does not render anything anymore, just a black screen with the UI still able to receive input, and the memory leak from my last post seems to stop at around ~18-19GB of RAM.

[WapaMario63]

After mentioning this on the s&box discord, the problem is the engine is making use of native win32 functionality that might not be implemented in wine/proton. Specifically: https://learn.microsoft.com/en-us/windows/win32/api/shobjidl_core/nn-shobjidl_core-icustomdestinationlist

[5FB5]

New fun thing. Without -vulkan flag I have a broken geometry textures like in screenshot by WapaMario63, but with working cubemaps.
On enabled flag I have a normal geometry, but cubemaps are broken

[SortaUnknown]

i'm suffering from a strange bug where, upon booting the game, steam labels it as "running", but no game window ever pops up, and it stops "running" after a few seconds. tested on Proton 7 and 8
AMD computer running on Debian 11
here is my proton log
steam-590830.log

[kisak-valve]

Hello @SortaUnknown, Proton 8.0 and newer requires that the video driver provide Vulkan 1.3. From your Proton log:

warn:  Skipping Vulkan 1.2 adapter: AMD RADV RENOIR (ACO)
warn:  Skipping Vulkan 1.0 adapter: llvmpipe (LLVM 11.0.1, 256 bits)
warn:  DXVK: No adapters found. Please check your device filter settings and Vulkan setup.

This tells us that your video driver is older than mesa 22.0, and too old for continued support with Proton.

[Etaash-mathamsetty]

i'm suffering from a strange bug where, upon booting the game, steam labels it as "running", but no game window ever pops up, and it stops "running" after a few seconds. tested on Proton 7 and 8 AMD computer running on Debian 11 here is my proton log steam-590830.log

you can upgrade to debian 12 to resolve the issue

[SortaUnknown]

upgraded to debian 12, same issue continues but logs are very different (looks like vulkan is firing up now)
steam-590830.log

[Rune580]

Can't launch either the game or the editor, a black window quickly flashes and disappears, tried Proton 8 and Experimental.
steam-590830.log

[kisak-valve]

S&box ToType error (sandbox gamemode)

Issue transferred from #7024.
@kuba64534 posted on 2023-08-18T09:19:33:

when i load in to the sandbox game there's error it says "ToType - please add ability to sandbox curvel"

[THEKAI64]

Game leaks memory pretty heavily for me,
I'm on Fedora 38 and I am using proton 8 (same thing happens on experimental)

[Blisto91]

@THEKAI64 Which driver. There is a big known memory leak affecting a bunch of games using radv in mesa 23.1.6. It has already been fixed but isn't included in a stable release yet.

[kisak-valve]

The Game thinks im offline?

Issue transferred from #7185.
@Crasher0711 posted on 2023-10-21T10:39:49:

No idea how this github reporting works but ill just sum it up here (if this even is the place for these kind of reports)

S&Box basically thinks im offline constatly which im, well, not, and on steam im also online, restarting, verifying game files and reinstalling didnt help so ill just make a report bout it. I also used to have that bug where the game only showed a black screen no matter what but that somehow just dissapeared after waiting a few weeks. If you need like pc specs of anything lmk.

[Kaydax]

Replying to #4940 (comment)

On the topic of the dev tools, here is another screenshot of the dev tools and whats happening:

I feel like this is more of an issue of how wine handles sizing child windows. The game view in the dev tools are a native child window created by the engine, but hidden and then painted and bound to a QT widget in the dev window. The game view itself should, like on windows, size itself according to the QT widget size and position... yet under proton/wine, it seems to size itself based on the size of the monitor itself. If I were to set the game size to 1920x1080, it will make the game view inside the widget actually 1920x1080 instead of 1080p retaliative to the widget

[SupinePandora43]

steam-590830.log
Instant crash, proton doesn't notice this and the status is still "Running"

[kisak-valve]

Hello @SupinePandora43, err:steamclient:create_win_interface Don't recognize interface name: SteamUser023 looks like the line of interest in your Proton log.

SteamUser023 looks like it was introduced in SteamWorks SDK 1.57 which was added to Proton in 8.0-3. Please retest with Proton 8.0 (or newer).

[Kaydax]

Game works perfectly out of box now, no need for any fixes. It does however have weird graphical glitches on the steam deck, but that is not proton related as much as s&box now is using native vulkan for its graphics.

The only issue now still are the dev tools, of which everything but the game view works. The game view is a very weird issue as its most likely due to this error here: 05:20:52 engine/Qt QtCriticalMsg: EnableNonClientDpiScaling() failed for HWND 0x3300fe (120) (Call not implemented.) as the way the game view works is by rendering a secondary window (The game window) inside of QT, and setting its DPI to be the same as the size of the game view widget. The game is rendering fine, but when being scaled to try and fit the widget, it scales to the monitor and not the widget size, thus causing very broken visuals (As seen here: #4940 (comment))

[KingKrouch]

When I try to mess with the developer tools in Proton, there's egregious screen flickering (regardless of what I do), and the editor window has a problem with being unable to resize, move, or close the window (unless I close the game manually from Steam).

From what I can gather, using MANGOHUD=0 %COMMAND% stops the screen resizing issue.

EDIT: Seems like this doesn't work for me anymore.

[RiQuY]

From what I can gather, using MANGOHUD=0 %COMMAND% stops the screen resizing issue.

MANGOHUD=0 %COMMAND% doesn't solve it for me.

[Meister1593]

For me, performance is really, really low and inconsistent most of the time
Both gpu and cpu and underutilized
GPU: rx 6600 xt
CPU: r5 5600x,
OS: KDE plasma, archlinux on 6.10.3-zen1-1-zen kernel (happens on regular as well)
freesync 144hz monitor

In the menu it's anywhere from 28 to 130 fps, in construct and simple gamemodes it's from 8-10 to 40, but mostly 8-10
Used proton 9, then applied fixes from https://wiki.facepunch.com/sbox/proton (win10, vulkan) but that didn't help either.
Disabling vsync helps a bit (marginal performance difference), though still inconsistent
Graphics is 4x anti-aliasing and trilinear filtering, at 1080p
steam-590830.tar.gz (logs)

[Kaydax]

@Meister1593

You dont need the fixes from the wiki, that is currently outdated. All you need is Proton Experimental. Performance is not caused by Proton, the game itself has just really bad performance currently, Facepunch is working on improving it

[Meister1593]

@Meister1593

You dont need the fixes from the wiki, that is currently outdated. All you need is Proton Experimental. Performance is not caused by Proton, the game itself has just really bad performance currently, Facepunch is working on improving it

Yes, it worked even without wiki fixes, i first tried without them completely and only then found abot wiki. Proton 9 worked same as experimental, so no need for that as well.

[DrakeFruit]

Getting weird colors instead of reflections on my steam deck, using proton experimental

[vertiKarl]

I'm not sure if this is a Linux-only issue, but it seems like the gamemode "Trouble in Terrorist Town" crashes on load.

Here is my s&box log:
sbox.log
and also my proton log:
steam-590830.log.zip

Also I need to run s&box with the launch option -adapter 1 to force amdvlk instead of mesa drivers, this brings my performance from around 20 fps to 150+