From 1ae5b467f5fede31717dd6b4e33d9ea02a9f1b63 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:14:19 +0100 Subject: [PATCH 01/14] known-issues: Stop mentioning pre-2023 names Signed-off-by: Simon McVittie --- doc/steamlinuxruntime-known-issues.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/doc/steamlinuxruntime-known-issues.md b/doc/steamlinuxruntime-known-issues.md index 64150d03..5776c685 100644 --- a/doc/steamlinuxruntime-known-issues.md +++ b/doc/steamlinuxruntime-known-issues.md @@ -25,17 +25,13 @@ The "Steam Linux Runtime 1.0 (scout)" compatibility tool (application ID 1070560) combines Steam Runtime 1 libraries with a Steam Runtime 2 container, and is used to run historical native Linux games. -Before September 2023, this was (confusingly) labelled "Steam Linux Runtime". -The old name might still appear in some contexts. The "Steam Linux Runtime 2.0 (soldier)" tool (application ID 1391110) is used to run Proton 5.13 up to 7.0 and is also used internally by the "Steam Linux Runtime" tool. -Before September 2023, this was labelled "Steam Linux Runtime - soldier". The "Steam Linux Runtime 3.0 (sniper)" tool (application ID 1628350) is used to run Proton 8.0 and some newer native Linux games. -Before September 2023, this was labelled "Steam Linux Runtime - sniper". Disabling Steam Play disables all Steam Linux Runtime tools ----------------------------------------------------------- From f6664860ab59e70f2359324dbef3c6fb25aa377e Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:15:19 +0100 Subject: [PATCH 02/14] known-issues: Mention the existence of SLR 4 steamrt/tasks#854 Signed-off-by: Simon McVittie --- doc/steamlinuxruntime-known-issues.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/steamlinuxruntime-known-issues.md b/doc/steamlinuxruntime-known-issues.md index 5776c685..fbe6cacf 100644 --- a/doc/steamlinuxruntime-known-issues.md +++ b/doc/steamlinuxruntime-known-issues.md @@ -31,7 +31,10 @@ used to run Proton 5.13 up to 7.0 and is also used internally by the "Steam Linux Runtime" tool. The "Steam Linux Runtime 3.0 (sniper)" tool (application ID 1628350) is -used to run Proton 8.0 and some newer native Linux games. +used to run Proton 8.0 up to 10.0 and some newer native Linux games. + +The "Steam Linux Runtime 4.0" tool (application ID 4183110) is +used to run Proton 11 or newer and some newer native Linux games. Disabling Steam Play disables all Steam Linux Runtime tools ----------------------------------------------------------- From fa3c6a446ac183ae1d9c6b9c954a962356b58bda Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:16:19 +0100 Subject: [PATCH 03/14] known-issues: Disabling Steam Play is no longer possible Fixed in November 2024. Reference: https://github.com/ValveSoftware/steam-for-linux/issues/9852 Signed-off-by: Simon McVittie --- doc/steamlinuxruntime-known-issues.md | 18 ------------------ 1 file changed, 18 deletions(-) diff --git a/doc/steamlinuxruntime-known-issues.md b/doc/steamlinuxruntime-known-issues.md index fbe6cacf..4b23efa4 100644 --- a/doc/steamlinuxruntime-known-issues.md +++ b/doc/steamlinuxruntime-known-issues.md @@ -36,24 +36,6 @@ used to run Proton 8.0 up to 10.0 and some newer native Linux games. The "Steam Linux Runtime 4.0" tool (application ID 4183110) is used to run Proton 11 or newer and some newer native Linux games. -Disabling Steam Play disables all Steam Linux Runtime tools ------------------------------------------------------------ - -In Steam's global settings, there is an option to turn off all Steam Play -compatibility tools. -As well as disabling Proton, this also disables Steam Linux Runtime 3.0 -(sniper), which will result in games that require this runtime being -launched in a way that does not work. -This is a Steam client issue: it should not allow launching the affected -games in this configuration. - -Games affected by this include Dota 2, Endless Sky and Retroarch. - -Workaround: in Steam's global Settings window, go to the Compatibility tab -and ensure that "Enable Steam Play for supported titles" is checked. - -([steam-for-linux#9852](https://github.com/ValveSoftware/steam-for-linux/issues/9852)) - Switching Steam Linux Runtime branch sometimes requires a Steam restart ----------------------------------------------------------------------- From 77af18e734da3666be63b9f6d49c109fedda5920 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:19:03 +0100 Subject: [PATCH 04/14] known-issues: steam-for-linux#9835 will probably affect SLR 4.0 Unconfirmed (we don't have an example SLR 4.0 game yet) but switching from SLR 3.0 to 4.0 is mechanically similar to switching from scout to SLR 3.0. steamrt/tasks#854 Reference: https://github.com/ValveSoftware/steam-for-linux/issues/9835 Signed-off-by: Simon McVittie --- doc/steamlinuxruntime-known-issues.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/steamlinuxruntime-known-issues.md b/doc/steamlinuxruntime-known-issues.md index 4b23efa4..3162d665 100644 --- a/doc/steamlinuxruntime-known-issues.md +++ b/doc/steamlinuxruntime-known-issues.md @@ -40,7 +40,9 @@ Switching Steam Linux Runtime branch sometimes requires a Steam restart ----------------------------------------------------------------------- When a game that was previously using an older runtime environment switches -to Steam Linux Runtime 3.0 (sniper), sometimes the Steam client will +to Steam Linux Runtime 3.0 (sniper) +or Steam Linux Runtime 4.0, +sometimes the Steam client will continue to run that game in the older runtime until it is restarted. This is a Steam client issue: it should switch to the new runtime automatically. From 5d43c3b67f1286201a82ff54263a6cf3718b7772 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:19:50 +0100 Subject: [PATCH 05/14] known-issues: steam-for-linux#9844 was fixed in 2024 Reference: https://github.com/ValveSoftware/steam-for-linux/issues/9844 Signed-off-by: Simon McVittie --- doc/steamlinuxruntime-known-issues.md | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/doc/steamlinuxruntime-known-issues.md b/doc/steamlinuxruntime-known-issues.md index 3162d665..06d97bca 100644 --- a/doc/steamlinuxruntime-known-issues.md +++ b/doc/steamlinuxruntime-known-issues.md @@ -55,21 +55,6 @@ all subsequent game launches should work correctly. ([steam-for-linux#9835](https://github.com/ValveSoftware/steam-for-linux/issues/9835)) -Forcing use of Steam Linux Runtime 1.0 (scout) for games requiring SLR 3 ------------------------------------------------------------------------- - -It is currently possible for users to configure games to be run -under Steam Linux Runtime 1.0 (scout), even if the game requires -Steam Linux Runtime 3.0 (sniper), which often will not work. -This is a Steam client issue: it should not allow this configuration. - -Games affected by this include Dota 2, Endless Sky and Retroarch. - -Workaround: in the game's Properties, go to the Compatibility tab and -ensure that "Force the use of a specific compatibility tool" is unchecked. - -([steam-for-linux#9844](https://github.com/ValveSoftware/steam-for-linux/issues/9844)) - Flatpak app limitations ----------------------- From 36c129ea016407c16c2c9c4a41460030500f7022 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:20:43 +0100 Subject: [PATCH 06/14] known-issues: Shorten the Flatpak section Flatpak 1.12+ is widespread now. Signed-off-by: Simon McVittie --- doc/steamlinuxruntime-known-issues.md | 18 ------------------ 1 file changed, 18 deletions(-) diff --git a/doc/steamlinuxruntime-known-issues.md b/doc/steamlinuxruntime-known-issues.md index 06d97bca..446e767a 100644 --- a/doc/steamlinuxruntime-known-issues.md +++ b/doc/steamlinuxruntime-known-issues.md @@ -68,26 +68,8 @@ the container runtimes, you will need: * An operating system where [unprivileged users can create user namespaces](https://github.com/flatpak/flatpak/wiki/User-namespace-requirements#unprivileged-bubblewrap) (non-setuid bubblewrap) - - * Debian >= 11, but not Debian 10 or older - * RHEL/CentOS >= 8, but not RHEL/CentOS 7 or older - * Arch Linux with the default `linux` kernel, - but not `linux-hardened` and `bubblewrap-suid` - * Most other recent distributions, e.g. Ubuntu - * Flatpak 1.12 or later - * Ubuntu 18.04 and 20.04 users can get this from - [the PPA](https://launchpad.net/~flatpak/+archive/ubuntu/stable/), - and it is included in Ubuntu 22.04 LTS - * Debian 11 users can get this from - [official backports](https://backports.debian.org/Instructions/), - and it is included in Debian 12 - -As a workaround, users of older versions of Flatpak can try using -[a community build of Proton](https://github.com/flathub/com.valvesoftware.Steam.CompatibilityTool.Proton) -which uses the freedesktop.org runtime instead of Steam Runtime 2. - ([#294](https://github.com/ValveSoftware/steam-runtime/issues/294), [Proton#4268](https://github.com/ValveSoftware/Proton/issues/4268), [Proton#4283](https://github.com/ValveSoftware/Proton/issues/4283), From f51bb37e8dcd612a5ece7d04d499f524b56f4ee6 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:22:52 +0100 Subject: [PATCH 07/14] known-issues: Non-Steam games can be made to run under SLR now Reference: https://github.com/ValveSoftware/steam-runtime/issues/228 Signed-off-by: Simon McVittie --- doc/steamlinuxruntime-known-issues.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/doc/steamlinuxruntime-known-issues.md b/doc/steamlinuxruntime-known-issues.md index 446e767a..b9ae21fe 100644 --- a/doc/steamlinuxruntime-known-issues.md +++ b/doc/steamlinuxruntime-known-issues.md @@ -282,15 +282,6 @@ Workaround: Move it to your home directory, as above. ([#257](https://github.com/ValveSoftware/steam-runtime/issues/257)) -Non-Steam games ---------------- - -Non-Steam games are not currently supported. - -Workaround: don't use Steam Linux Runtime for those games yet. - -([#228](https://github.com/ValveSoftware/steam-runtime/issues/228)) - Audio ----- From b9754fc6b65418b407efe1d69d409e8f8e326a0f Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:23:57 +0100 Subject: [PATCH 08/14] known-issues: Stop saying that SLR 1.0 is experimental It has been the default since November 2024. Reference: https://store.steampowered.com/news/collection/steam/?emclan=103582791457287600&emgid=4472730495692571024 Signed-off-by: Simon McVittie --- doc/steamlinuxruntime-known-issues.md | 17 ----------------- 1 file changed, 17 deletions(-) diff --git a/doc/steamlinuxruntime-known-issues.md b/doc/steamlinuxruntime-known-issues.md index b9ae21fe..cbf0135b 100644 --- a/doc/steamlinuxruntime-known-issues.md +++ b/doc/steamlinuxruntime-known-issues.md @@ -359,23 +359,6 @@ fixed the easier cases). Workaround: use bind mounts instead. [#321](https://github.com/ValveSoftware/steam-runtime/issues/321), [#368](https://github.com/ValveSoftware/steam-runtime/issues/368)) -Common issues and workarounds specific to 'scout' -------------------------------------------------- - -Using the Steam Runtime 1 `scout` runtime in a container is considered -experimental, and is not expected to work for all games. Native Linux -games that were compiled for Steam Runtime 1 `scout` are intended to be -run in the older `LD_LIBRARY_PATH`-based Steam Runtime. - -### Updating "Steam Linux Runtime 1.0 (scout)" compatibility tool - -Due to a Steam limitation, after updating to version 0.20210630.32 or -later, it is necessary to exit from Steam completely and re-launch Steam, -so that the updated compatibility tool configuration will be loaded. -Until Steam has been restarted, trying to launch a game with the -"Steam Linux Runtime 1.0 (scout)" compatibility tool will show an error message -asking for a Steam restart. - Reporting other issues ---------------------- From ba1a7bf370c120b3ca884ac510c3c80916f31316 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:32:44 +0100 Subject: [PATCH 09/14] reporting-bugs: Mention SLR 4.0 steamrt/tasks#854 Signed-off-by: Simon McVittie --- doc/reporting-steamlinuxruntime-bugs.md | 24 ++++++++++++++++++------ 1 file changed, 18 insertions(+), 6 deletions(-) diff --git a/doc/reporting-steamlinuxruntime-bugs.md b/doc/reporting-steamlinuxruntime-bugs.md index dc6f26eb..2560d9f4 100644 --- a/doc/reporting-steamlinuxruntime-bugs.md +++ b/doc/reporting-steamlinuxruntime-bugs.md @@ -8,13 +8,19 @@ It consists of: * pressure-vessel, a container launching tool * a *runtime*, providing a set of libraries for games to use -There are currently three runtimes available: +There are currently four runtimes available: + +* [Steam Linux Runtime 4.0](https://gitlab.steamos.cloud/steamrt/steamrt/-/blob/steamrt/steamrt4/README.md) + (steamrt4), + [app ID 4183110](https://steamdb.info/app/4183110/) + is used to run official releases of Proton 11 or newer. + We expect it to be used for newer native Linux games in future. * [Steam Linux Runtime 3.0 (sniper)](https://gitlab.steamos.cloud/steamrt/steamrt/-/blob/steamrt/sniper/README.md), [app ID 1628350](https://steamdb.info/app/1628350/) - is used to run official releases of Proton 8.0 or newer, - and some native Linux games such as Dota 2, Endless Sky and Retroarch. - We expect it to be used for other newer native Linux games in future. + is used to run official releases of Proton 8.0 to 10.0, + and increasingly many native Linux games such as + Dota 2, Endless Sky and Retroarch. * [Steam Linux Runtime 2.0 (soldier)](https://gitlab.steamos.cloud/steamrt/steamrt/-/blob/steamrt/soldier/README.md), [app ID 1391110](https://steamdb.info/app/1391110/) @@ -79,9 +85,12 @@ log. The easiest way to get this is: * Find the Steam Library directory where the runtime is installed, typically `~/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier` - for Steam Runtime 2 'soldier' or + for Steam Runtime 2 'soldier', `~/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper` for Steam Runtime 3 'sniper' + or + `~/.local/share/Steam/steamapps/common/SteamLinuxRuntime_4` + for Steam Runtime 4 * Version numbers for some important runtime components are in `VERSIONS.txt` @@ -134,7 +143,9 @@ select a different branch from your Steam Library, in the same way you would for a game: follow the same procedure as , but instead of the properties of CS:GO, change the properties of the -tool named *Steam Linux Runtime 3.0 (sniper)*, +tool named +*Steam Linux Runtime 4.0*, +*Steam Linux Runtime 3.0 (sniper)*, *Steam Linux Runtime 2.0 (soldier)* or *Steam Linux Runtime 1.0 (scout)*. @@ -163,6 +174,7 @@ If something works in one branch but fails in another branch, that's very useful information to include in issue reports. Please be as clear as you can about which version works and which version fails. You can check the current version by looking at +`SteamLinuxRuntime_4/VERSIONS.txt`, `SteamLinuxRuntime_sniper/VERSIONS.txt`, `SteamLinuxRuntime_soldier/VERSIONS.txt` or `SteamLinuxRuntime/VERSIONS.txt`. From fdeecd61080bbf35bb175908f3b6ffeb980b0804 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:33:42 +0100 Subject: [PATCH 10/14] reporting-bugs: Use easier instructions for swapping among runtimes These also generalize nicely to all versions of SLR. Signed-off-by: Simon McVittie --- doc/reporting-steamlinuxruntime-bugs.md | 27 +++++++++++++------------ 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/doc/reporting-steamlinuxruntime-bugs.md b/doc/reporting-steamlinuxruntime-bugs.md index 2560d9f4..68598c46 100644 --- a/doc/reporting-steamlinuxruntime-bugs.md +++ b/doc/reporting-steamlinuxruntime-bugs.md @@ -241,22 +241,23 @@ game's setup commands have finished. ### Changing the runtime version If you download a file named -`com.valvesoftware.SteamRuntime.Platform-amd64,i386-soldier-runtime.tar.gz` -from , +`SteamLinuxRuntime_4.tar.xz` +from , you can use it as a runtime instead of the one provided by Steam. -Create a new directory in `SteamLinuxRuntime_soldier`, for example -`SteamLinuxRuntime_soldier/my_soldier_platform_0.20200604.0`, -and unpack the tarball into that directory so that you have files like -`SteamLinuxRuntime_soldier/my_soldier_platform_0.20200604.0/metadata` and -`SteamLinuxRuntime_soldier/my_soldier_platform_0.20200604.0/files/bin/env`. +Unpack it, rename the resulting directory to something like +`SteamLinuxRuntime_4_test_3.0.20260415.224995` +and move it into `steamapps/common` next to the production version of +`SteamLinuxRuntime_4`. Then select it from the list of runtimes in [the test-UI](#test-ui). -For the "Steam Linux Runtime 1.0 (scout)" environment, the closest equivalent -is to download a file named `steam-runtime.tar.xz` from -from -and unpack it into the `SteamLinuxRuntime` directory, so that you have -files like `SteamLinuxRuntime/steam-runtime/version.txt`. This will be -used in preference to the scout runtime that comes with Steam. +A similar process can be used for +`SteamLinuxRuntime_sniper.tar.xz` +from , +`SteamLinuxRuntime_soldier.tar.xz` +from , +or +`SteamLinuxRuntime.tar.xz` +from . ### SDK runtimes From d8ea048f6766a387916cf84dad03269e85128a53 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:34:08 +0100 Subject: [PATCH 11/14] reporting-bugs: Use non-legacy URL for SDK runtimes I haven't rewritten this to refer to steamrt4 or sniper at this stage. Signed-off-by: Simon McVittie --- doc/reporting-steamlinuxruntime-bugs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/reporting-steamlinuxruntime-bugs.md b/doc/reporting-steamlinuxruntime-bugs.md index 68598c46..8fbe628a 100644 --- a/doc/reporting-steamlinuxruntime-bugs.md +++ b/doc/reporting-steamlinuxruntime-bugs.md @@ -263,7 +263,7 @@ from . If you download a file named `com.valvesoftware.SteamRuntime.Sdk-amd64,i386-soldier-runtime.tar.gz` -from , +from , you can use it as a runtime. Create a new directory in `SteamLinuxRuntime_soldier`, for example `SteamLinuxRuntime_soldier/my_soldier_sdk_0.20200604.0`, and unpack the tarball into that directory so that you have files like From 020447a7e949e93793ffc39c1d280ad71d1c5105 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:35:35 +0100 Subject: [PATCH 12/14] goals: Mention SLR 4.0 instead of the defunct medic branch steamrt/tasks#854 Signed-off-by: Simon McVittie --- doc/goals.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/goals.md b/doc/goals.md index 04d3bd59..1a70544a 100644 --- a/doc/goals.md +++ b/doc/goals.md @@ -108,11 +108,12 @@ released in 2019. It is used to run Proton 5.13 up to 7.0. Steam Runtime version 3, 'sniper', is based on Debian 11 'bullseye', released in 2021. It is otherwise similar to soldier. -It is used to run Proton 8.0 or later, and some native Linux games +It is used to run Proton 8.0 up to 10.0, and some native Linux games such as Dota 2, Endless Sky and Retroarch. -Similarly, Steam Runtime version 4, 'medic', is likely to be based on -Debian 12 'bookworm', which was released in 2023. +Similarly, Steam Runtime version 4, 'steamrt4', is based on +Debian 13 'trixie', which was released in 2025. +It is used to run Proton 11 or later. #### New glibc From c2e636d58633eb5634c9cfa5df6a000ecb392b14 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:44:14 +0100 Subject: [PATCH 13/14] issue template: Ask for SLR_4 version number, too steamrt/tasks#854 Signed-off-by: Simon McVittie --- .github/ISSUE_TEMPLATE/ISSUE_TEMPLATE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE.md index 8161e6b0..5ea96cb2 100644 --- a/.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE.md +++ b/.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE.md @@ -14,6 +14,7 @@ about: Issues with the Steam runtime * What versions are listed in `steamapps/common/SteamLinuxRuntime/VERSIONS.txt`? * What versions are listed in `steamapps/common/SteamLinuxRuntime_soldier/VERSIONS.txt`? * What versions are listed in `steamapps/common/SteamLinuxRuntime_sniper/VERSIONS.txt`? +* What versions are listed in `steamapps/common/SteamLinuxRuntime_4/VERSIONS.txt`? #### Please describe your issue in as much detail as possible: From dee6cb554512e9dc065a4b46facbddc77ccc82de Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Tue, 28 Apr 2026 15:44:46 +0100 Subject: [PATCH 14/14] README: Recommend Steam Linux Runtime 4.0 (steamrt4) for new titles steamrt/tasks#854 Signed-off-by: Simon McVittie --- README.md | 41 +++++++++++++++++++++++++++++++---------- 1 file changed, 31 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 872aeff0..0c2e6a0a 100644 --- a/README.md +++ b/README.md @@ -28,15 +28,26 @@ This is implemented as a series of Steam Play compatibility tools, and is referred to as the Steam [container runtime][], or as the *Steam Linux Runtime*. -Newer native Linux games such as Counter-Strike 2 and Dota 2 -run in an environment referred to as `Steam Linux Runtime 3.0 (sniper)`, -which is a [Steam Runtime 3 'sniper'][sniper] container. -This is the recommended environment for developers of new native Linux games. +Newer native Linux games can run in an environment referred to as +`Steam Linux Runtime 4.0`, +which is a [Steam Runtime 4 'steamrt4'][steamrt4] +container. +This is the recommended environment for developers of new native Linux games, +and developers of existing games can switch to it as part of a game update +if desired. To target this environment, -developers should compile their games in the [sniper SDK][], +developers should compile their games in the +[steamrt4 SDK][], then set up a Launch Option that supports Linux, and use the Installation → Linux Runtime menu item in the Steamworks -partner web interface to select the sniper runtime. +partner web interface to select the SLR 4.0 runtime. + +`Steam Linux Runtime 3.0 (sniper)` is an older runtime using a +[Steam Runtime 3 'sniper'][sniper] container. +To target this environment, +developers should compile their games in the +[sniper SDK][], +and use the Steamworks partner web interface to select the SLR 3.0 runtime. Older native Linux games normally run in an environment referred to as `Steam Linux Runtime 1.0 (scout)`, which is a @@ -49,13 +60,14 @@ To target either of these environments, developers should compile their games in the [scout SDK][]. For backwards compatibility, this is still the default when a developer publishes a native Linux game, -but we now recommend that developers should target sniper instead. +but we now recommend that developers should target steamrt4 instead. The Steam Runtime is also used by the [Proton][] Steam Play compatibility tools, which run Windows games on Linux systems. -Current versions of Proton (8.0 or newer) use the Steam Runtime 3 'sniper' +The most recent versions of Proton (11 or newer) use the Steam Runtime 4 container runtime. -Older versions of Proton (5.13, 6.3 and 7.0) use the +Proton 8, 9 and 10 use the Steam Runtime 3 'sniper' container runtime, +while Proton 5.13, 6.3 and 7.0 use the Steam Runtime 2 'soldier' container runtime. The oldest versions of Proton (5.0 or earlier) use the legacy Steam Runtime 1 'scout' `LD_LIBRARY_PATH` runtime. @@ -71,6 +83,8 @@ More information about the [scout SDK]: https://gitlab.steamos.cloud/steamrt/scout/sdk [sniper]: https://gitlab.steamos.cloud/steamrt/steamrt/-/blob/steamrt/sniper/README.md [sniper SDK]: https://gitlab.steamos.cloud/steamrt/sniper/sdk +[steamrt4]: https://gitlab.steamos.cloud/steamrt/steamrt/-/blob/steamrt/steamrt4/README.md +[steamrt4 SDK]: https://gitlab.steamos.cloud/steamrt/steamrt4/sdk [soldier]: https://gitlab.steamos.cloud/steamrt/steamrt/-/blob/steamrt/soldier/README.md [steam-runtime-tools documentation]: https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/tree/main/docs @@ -104,6 +118,7 @@ They can also be downloaded by opening `steam://` links with Steam: * Steam Linux Runtime 1.0 (scout): `steam steam://install/1070560` * Steam Linux Runtime 2.0 (soldier): `steam steam://install/1391110` * Steam Linux Runtime 3.0 (sniper): `steam steam://install/1628350` +* Steam Linux Runtime 4.0: `steam steam://install/4183110` All the software that makes up the Steam Runtime is available in both source and binary form in the Steam Runtime repository [https://repo.steampowered.com/steamrt](https://repo.steampowered.com/steamrt "") @@ -125,10 +140,15 @@ All of these environments are compatible with the official Steam Runtime SDK images, which we provide in OCI format. +If targeting Steam Linux Runtime 4.0, +please consult the +[Steam Runtime 4 SDK](https://gitlab.steamos.cloud/steamrt/steamrt4/sdk/-/blob/steamrt/steamrt4/README.md) +documentation for details. + If targeting Steam Linux Runtime 3.0 'sniper', please consult the [Steam Runtime 3 'sniper' SDK](https://gitlab.steamos.cloud/steamrt/sniper/sdk/-/blob/steamrt/sniper/README.md) -documentation for details. +documentation instead. If targeting the legacy 'scout' runtime, please consult the @@ -173,6 +193,7 @@ Steam Runtime apt repositories Each Steam Runtime suite has an associated apt repository: +* [`deb https://repo.steampowered.com/steamrt4/apt steamrt4 main contrib non-free`](https://repo.steampowered.com/steamrt4/apt) * [`deb https://repo.steampowered.com/steamrt3/apt sniper main contrib non-free`](https://repo.steampowered.com/steamrt3/apt) * [`deb https://repo.steampowered.com/steamrt2/apt soldier main contrib non-free`](https://repo.steampowered.com/steamrt2/apt) * [`deb https://repo.steampowered.com/steamrt1/apt scout main`](https://repo.steampowered.com/steamrt1/apt)