Revision Difference
proton#562962
<cat>Play.Intro</cat>
<title>Proton</title>
# Proton
All information regarding running and developing S&Box on Linux will described here.
All information regarding running and developing s&box on Linux will described here.
# Running
S&box needs some tinkering to work on Linux:
1. Change you're Proton Version to "Proton Experimental"
2. In the Terminal type this:⤶
1. Change your Proton Version to "Proton Experimental"
2. In the terminal type:⤶
```
sudo sysctl -w vm.max_map_count=16777216
```
After doing these steps, S&box should run fine.
<note>The Main Menu of S&box is Unstable on Linux and crashes after about 2-5 minutes. Just Open a Game quick enough and it will work since its only the Main Menu.</note>
This should be enough to get s&box to run for most people.
<note>The main menu can be unstable and may crash if open too long, but games should be stable.</note>
# Developing
At the time of writing *(October 2024)* you can launch s&box development tools via the steam launch options. Please note this is unstable and you will likely crash or have random issues.
At the time of writing *(November 2024)* you can launch s&box development tools via the steam launch options and everything works aside from the game window. If using x11, you can download a library from the library manager to fix this, but there's currently nothing you can do on Wayland.
# Troubleshooting
## How to use the proton logs
Proton logs sometimes could help solve issues with games not launching or working properly under proton. Proton logging can be enabled inside the launch options of s&box:
```
PROTON_LOG=1 %command%
```
If you want smaller log files but still keep useful information use this launch option:
```
WINEDEBUG=+error+threadname+debugstr+loaddll+mscoree PROTON_LOG=1 %command%
```
By default it should generate a file inside your home directory `$HOME/steam-590830.log` but it can be modified as well:
```
PROTON_LOG=1 PROTON_LOG_DIR='/path/to/log' %command%
```
## Input (e.g. movement) does not work
This is probably caused by having multiple keyboard layouts, adding `-input_button_code_is_scan_code` to your launch options fixes the problem
# Useful Resources:
1. [S&box proton github issues](https://github.com/ValveSoftware/Proton/issues/4940)
2. [Proton parameters guide](https://github.com/ValveSoftware/Proton#runtime-config-options)