Difference between revisions of "Steam"

From ArchWiki
Jump to: navigation, search
(Native Steam on Linux)
(Alternative Flatpak installation: Should now work (copy-paste and don't ask questions))
 
(426 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
 
[[Category:Gaming]]
 
[[Category:Gaming]]
[[Category:Wine]]
 
 
[[ja:Steam]]
 
[[ja:Steam]]
[[zh-CN:Steam]]
+
[[ru:Steam]]
{{Article summary start}}
+
[[zh-hans:Steam]]
{{Article summary text|[http://store.steampowered.com/about/ Steam] is a content delivery system made by Valve Software. It is best known as the platform needed to play Source Engine games (e.g. Half-Life 2, Counter-Strike). Today it offers many games from many other developers.}}
+
{{Related articles start}}
 +
{{Related|Steam/Troubleshooting}}
 +
{{Related|Steam/Game-specific troubleshooting}}
 +
{{Related|Gaming}}
 +
{{Related|Gamepad}}
 +
{{Related|List of games}}
 +
{{Related articles end}}
 +
[http://store.steampowered.com/about/ Steam] is a popular game distribution platform by Valve.
  
{{Article summary heading|Related}}
+
Steam for Linux only supports Ubuntu 12.04 LTS and newer [https://support.steampowered.com/kb_article.php?ref=1504-QHXN-8366].
{{Article summary wiki|Wine}}
+
Valve does not offer any support when running into issues with Steam on Arch Linux.
{{Article summary wiki|Steam/Game-specific troubleshooting}}
 
{{Article summary end}}
 
  
From [[Wikipedia:Steam (software)|Wikipedia]]:
+
== Installation ==
: ''Steam is a digital distribution, digital rights management, multiplayer and communications platform developed by Valve Corporation. It is used to distribute games and related media online, from small independent developers to larger software houses.''
 
  
== Native Steam on Linux ==
+
Enable the [[Multilib]] repository and [[install]] the {{Pkg|steam}} package.
  
{{Note|
+
The following requirements must be fulfilled in order to run Steam on Arch Linux:
* Arch Linux is '''not''' [https://support.steampowered.com/kb_article.php?ref=1504-QHXN-8366 officially supported].
 
* Because the Steam client is a 32-bit application, you will need to enable the [[multilib]] repository if you have a 64-bit system. It may also make sense to install {{Grp|multilib-devel}} to provide some important multilib libraries. You also most likely need to install the 32-bit version of your graphics driver to run Steam.
 
}}
 
 
 
Steam can be installed with the package {{Pkg|steam}}, available in the [[official repositories]]. If you have a 64-bit system, enable the [[multilib]] repository first.
 
 
 
Steam is not supported on this distribution. As such some fixes are needed on the users part to get things functioning properly:
 
 
 
*Steam makes heavy usage of the Arial font. A decent Arial font to use is {{Pkg|ttf-liberation}} or one of the official Microsoft fonts packages containing Arial: {{AUR|ttf-microsoft-arial}}, {{AUR|ttf-ms-win8}},{{AUR|ttf-office-2007-fonts}}, {{AUR|ttf-win7-fonts}} or {{AUR|ttf-ms-fonts}}. See [[MS Fonts]] for more details. Asian languages require {{Pkg|wqy-zenhei}} to display properly.
 
 
 
*Most games require {{Pkg|libtxc_dxtn}} and {{Pkg|lib32-libtxc_dxtn}} when using mesa drivers, so it is recommended to install these packages.
 
 
 
*Several games have dependencies which may be missing from your system. If a game fails to launch (often without error messages) then make sure all of the libraries listed in [[Steam/Game-specific troubleshooting]] are installed.
 
 
 
=== Troubleshooting ===
 
 
 
{{Note|
 
* In addition to being documented here, any bug/fix/error should be, if not already, reported on Valve's bug tracker on their [https://github.com/ValveSoftware/steam-for-linux GitHub page].
 
* Connection problems may occur when using DD-WRT with peer-to-peer traffic filtering.
 
}}
 
 
 
==== GUI problems with KDE ====
 
 
 
: Valve GitHub [https://github.com/ValveSoftware/steam-for-linux/issues/594 issue 594]
 
 
 
If you are using KDE and you have problems with the GUI (such as lag or random crashes), in KDE system settings, go to ''Workspace Appearance and Behaviour > Desktop Effects > Advanced''. Change "Compositing type" from "XRender" to "OpenGL".
 
 
 
==== The close button only minimizes the window ====
 
 
 
: Valve GitHub [https://github.com/ValveSoftware/steam-for-linux/issues/1025 issue 1025]
 
 
 
To close the Steam window (and remove it from the taskbar) when you press '''x''', but keep Steam running in the tray, set the environment variable {{ic|STEAM_FRAME_FORCE_CLOSE}} to {{ic|1}}. You can do this by launching Steam using the following command.
 
$ STEAM_FRAME_FORCE_CLOSE=1 steam
 
 
 
==== Flash not working on 64-bit systems ====
 
 
 
: Steam Support [https://support.steampowered.com/kb_article.php?ref=1493-GHZB-7612 article]
 
 
 
First ensure {{Pkg|lib32-flashplugin}} is installed. It should be working at this point, if not create a local Steam Flash plugin folder:
 
$ mkdir ~/.steam/bin32/plugins/
 
and set a symbolic link to the global lib32 flash plugin file in your upper new folder
 
$ ln -s /usr/lib32/mozilla/plugins/libflashplayer.so ~/.steam/bin32/plugins/
 
 
 
==== Text is corrupt or missing ====
 
 
 
The Steam Support [https://support.steampowered.com/kb_article.php?ref=1974-YFKL-4947 instructions] for Windows seem to work on Linux also: Simply download [https://support.steampowered.com/downloads/1974-YFKL-4947/SteamFonts.zip SteamFonts.zip] and install them (copying to {{ic|~/.fonts/}} works at least).
 
 
 
==== Error on some games: black textures/S3TC support is missing ====
 
 
 
Install the following dependencies:
 
* {{Pkg|libtxc_dxtn}}
 
* {{Pkg|lib32-libtxc_dxtn}}
 
 
 
====Black screen on (Valve?) games (but audio works)====
 
 
 
Check the Steam stdout/stderr for Error lines, some quick dependencies for reference:
 
* {{Pkg|lib32-intel-dri}} (not confirmed as absolutely necessary)
 
 
 
Run Steam from console via primusrun steam
 
  
If using KDE, disable all desktop effects ({{ic|Alt+Shift+F12}}) before starting Steam.
+
* Installed 32-bit version [[Xorg#Driver installation|OpenGL graphics driver]].
 +
* Generated [[Locale#Generating locales|en_US.UTF-8]] locale, preventing invalid pointer error.
 +
* The GUI heavily uses the Arial font. See [[Microsoft fonts]]. An alternative is to use {{Pkg|ttf-liberation}} or [[Steam/Troubleshooting#Text is corrupt or missing|fonts provided by Steam]] instead.
 +
* [[Install]] {{Pkg|wqy-zenhei}} to add support for Asian languages.
  
==== SetLocale('en_US.UTF-8') fails at game startup ====
+
=== SteamCMD ===
  
Edit {{ic|/etc/locale.gen}} in your favourite editor and uncomment the line {{ic|en_US.UTF-8 UTF-8}}. Then run {{ic|# locale-gen}}.
+
[[Install]] {{AUR|steamcmd}} for the command-line version of the [https://developer.valvesoftware.com/wiki/SteamCMD Steam].
  
==== Steam complains about direct rendering not available on 64bit systems with NVIDIA driver ====
+
{{Note|This package installs files under ''root'', so you must run SteamCMD as ''root''.}}
  
Make sure you have [multilib] enabled in {{ic|/etc/pacman.conf}}.
+
=== Alternative Flatpak installation ===
  
Install the following dependencies:
+
Steam can also be installed with [[Flatpak]] as {{ic|com.valvesoftware.Steam}} from [https://flathub.org/ Flathub]. The easiest way to install it for the current user is by using the Flathub repo and flatpak command:
* {{Pkg|lib32-nvidia-utils}}
 
* {{Pkg|lib32-nvidia-libgl}}
 
  
Steam, being a 32-bit application, requires 32-bit nvidia GL libraries to run. This packages will install the proper 32-bit libGl libraries and symlinks in {{ic|/usr/lib32}} and will replace any existing mesa equivalent symlinks.
+
  flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
 +
  flatpak --user install flathub com.valvesoftware.Steam
 +
  flatpak run com.valvesoftware.Steam
  
=== Launching games with custom commands, such as Bumblebee/Primus ===
+
The Flatpak application currently does not support themes. Also you currently can't run games via {{ic|optirun}}/{{ic|primusrun}}, see [https://github.com/flatpak/flatpak/issues/869 Issue#869] for more details.
  
Steam has fortunately added support for launching games using your own custom command. To do so, navigate to the Library page, right click on the selected game, click Properties, and Set Launch Options. Steam replaces the tag {{ic|%command%}} with the command it actually wishes to run. For example, to launch Team Fortress 2 with primusrun and at resolution 1920x1080, you would enter:
+
The Flatpak application has some [https://www.ctrl.blog/entry/flatpak-steamcloud-xdg known issues with Steam Auto-Cloud] so game progress may not be synced unless you create some symlinks by hand for affected games.
  
primusrun %command% -w 1920 -h 1080
+
By default Steam won't be able to access your home directory, you can run the following command to allow it, so that it behaves like on Ubuntu or SteamOS:
  
If you are running the [[Linux-ck]] kernel, you may have some success in reducing overall latencies and improving performance by launching the game in SCHED_ISO (low latency, avoid choking CPU) via {{Pkg|schedtool}}
+
flatpak override com.valvesoftware.Steam --filesystem=$HOME
  
# schedtool -I -e %command% ''other arguments''
+
== Directory structure ==
  
==== Killing standalone compositors when launching games ====
+
The default Steam install location is {{ic|~/.local/share/Steam}}. If Steam cannot find it, it will prompt you to reinstall it or select the new location. This article uses the {{ic|~/.steam/root}} symlink to refer to the install location.
  
Further to this, utilising the {{ic|%command%}} switch, you can kill standalone compositors (such as Xcompmgr or [[Compton]]) - which can cause lag and tearing in some games on some systems - and relaunch them after the game ends by adding the following to your game's launch options.
+
=== Library folders ===
  
  killall compton && %command%; nohup compton &
+
Every Steam application has a unique AppID, which you can find out by looking at its [http://store.steampowered.com/ Steam Store] page path.
  
Replace {{ic|compton}} in the above command with whatever your compositor is. You can also add -options to {{ic|%command%}} or {{ic|compton}}, of course.
+
Steam installs games into a directory under {{ic|''LIBRARY''/steamapps/common/}}. {{ic|''LIBRARY''}} normally is
 +
{{ic|~/.steam/root}} but you can also have multiple library folders (''Steam > Settings > Downloads > Steam Library Folders'').
  
Steam will latch on to any processes launched after {{ic|%command%}} and your Steam status will show as in game. So in this example, we run the compositor through {{ic|nohup}} so it is not attached to Steam (it will keep running if you close Steam) and follow it with an ampersand so that the line of commands ends, clearing your Steam status.
+
In order for Steam to recognize a game it needs to have an
 +
{{ic|appmanifest_''AppId''.acf}} file in {{ic|''LIBRARY''/steamapps/}}. The appmanifest file uses the  
 +
[https://developer.valvesoftware.com/wiki/KeyValues KeyValues] format and its {{ic|installdir}} property
 +
determines the game directory name.
  
=== Using native runtime ====
+
== Usage ==
 +
 +
steam [ -options ] [ steam:// URL ]
  
Steam, by default, ships with a copy of every library it uses, packaged within itself, so that games can launch without issue. This can be a resource hog, and the slightly out-of-date libraries they package may be missing important features (Notably, the OpenAL version they ship lacks HRTF support). To use your own system libraries, you can run Steam with:
+
For the available command-line options see the [https://developer.valvesoftware.com/wiki/Command_Line_Options#Steam_.28Windows.29 Command Line Options article on the Valve Developer Wiki].
  
  STEAM_RUNTIME=0 steam
+
Steam also accepts an optional Steam URL, see the [https://developer.valvesoftware.com/wiki/Steam_browser_protocol Steam browser procotol].
  
However, if you're missing any libraries Steam makes use of, this will fail to launch properly. An easy way to find the missing libraries is to run the following commands:
+
== Launch options ==
  
  cd ~/.local/share/Steam/ubuntu12_32
+
When you launch a Steam game, Steam executes its '''launch command''' in a [[Bash]] shell.
  LD_LIBRARY_PATH=".:${LD_LIBRARY_PATH}" ldd $(file *|sed '/ELF/!d;s/:.*//g')|grep 'not found'|sort|uniq
+
To let you alter the launch command Steam provides '''launch options''',
 +
which can be set for a game by right-clicking on it in your library, selecting Properties and clicking on ''Set Launch Options''.
  
Note that the libraries will have to be 32-bit, which means you may have to download some from the AUR if on x86_64, such as NetworkManager.
+
By default Steam simply appends your option string to the launch command. To set environment variables or
 +
pass the launch command as an argument to another command you can use the {{ic|%command%}} substitute.
  
Once you've done this, run steam again with STEAM_RUNTIME=0 steam and verify it's not loading anything outside of the handful of steam support libraries:
+
=== Examples ===
  
  cat /proc/`pidof steam`/maps|sed '/\.local/!d;s/.* //g'|sort|uniq
+
* only arguments: {{ic|-foo}}
 +
* environment variables: {{ic|1=FOO=bar BAZ=bar %command% -baz}}
 +
* completely different command: {{ic|othercommand # %command%}}
  
=== Skins for Steam ===
+
== Tips and tricks ==
  
The Steam interface can be fully customized by copying its various interface files in its skins directory and modifying them.
+
=== Big Picture Mode without a window manager ===
  
==== Steam skin manager ====
+
To start Steam in Big Picture Mode from a [[Display manager]], create a {{ic|/usr/share/xsessions/steam-big-picture.desktop}} file with the following contents:
  
The process of applying a skin to Steam can be greatly simplified using {{AUR|steam-skin-manager}} from the AUR. The package also comes with a hacked version of the Steam launcher which allows the window manager to draw its borders on the Steam window.
+
{{hc|/usr/share/xsessions/steam-big-picture.desktop|<nowiki>
 +
[Desktop Entry]
 +
Name=Steam Big Picture Mode
 +
Comment=Start Steam in Big Picture Mode
 +
Exec=/usr/bin/steam -bigpicture
 +
TryExec=/usr/bin/steam
 +
Icon=
 +
Type=Application</nowiki>}}
  
As a result, skins for Steam will come in two flavors, one with and one without window buttons. The skin manager will prompt you whether you use the hacked version or not, and will automatically apply the theme corresponding to your GTK+ theme if it is found. You can of course still apply another skin if you want.
+
=== Steam skins ===
  
The package ships with two themes for the default Ubuntu themes, Ambiance and Radiance. A Faience theme is under development and already has its own package on the AUR {{AUR|steam-skin-faience-git}}.
+
The Steam interface can be customized using skins. Skins can overwrite interface-specific files in {{ic|~/.steam/root}}.
  
== Steam on Wine ==
+
To install a skin:
  
Install {{Pkg|wine}} from the [[multilib]] and follow the instructions provided in the [[Wine|article]].
+
# Place its directory in {{ic|~/.steam/root/skins}}.
 +
# Open ''Steam > Settings > Interface'' and select it.
 +
# Restart Steam.
  
Install the required Microsoft fonts {{AUR|ttf-microsoft-tahoma}} and {{AUR|ttf-ms-fonts}} from the [[AUR]] or through {{AUR|winetricks-svn}}.
+
An extensive list of skins can be found in [http://forums.steampowered.com/forums/showthread.php?t=1161035 this Steam forums post].
{{Note|If you have access to Windows discs, you may want to install {{AUR|ttf-ms-win8}} or {{AUR|ttf-win7-fonts}} instead.}}
 
  
If you have an old Wine prefix ({{ic|~/.wine}}), you should remove it and let Wine create a new one to avoid problems (you can transfer over anything you want to keep to the new Wine prefix).
+
{{Note|Using an outdated skin may cause visual errors.}}
  
=== Installation ===
+
==== Creating skins ====
  
Download and run the Steam installer from [http://store.steampowered.com/about/ steampowered.com]. It is no longer an {{ic|.exe}} file so you have to start it with {{ic|msiexec}}:
+
Nearly all Steam styles are defined in {{ic|~/.steam/root/resource/styles/steam.styles}} (the file is over 3,500 lines long). For a skin to be recognized it needs its own {{ic|resource/styles/steam.styles}}.
$ msiexec /i SteamInstall.msi
+
When a Steam update changes the official {{ic|steam.styles}} your skin may become outdated, potentially resulting in visual errors.
  
=== Starting Steam ===
+
See {{ic|~/.steam/root/skins/skins_readme.txt}} for a primer on how to create skins.
  
On x86:
+
=== Changing the Steam notification position ===
$ wine ~/.wine/drive_c/Program\ Files/Steam/Steam.exe
 
  
On x86_64 (with steam installed to a clean wine prefix):
+
The default Steam notification position is bottom right.
$ wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe
 
  
Alternatively, you may use this method:
+
You can change the Steam notification position by altering {{ic|Notifications.PanelPosition}} in
$ wine "C:\\Program Files\\Steam\\steam.exe"
 
  
You should consider making an alias to easily start steam (and put it in your shell's rc file), example:
+
* {{ic|resource/styles/steam.styles}} for desktop notifications, and
alias steam='wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe >/dev/null 2>&1 &'
+
* {{ic|resource/styles/gameoverlay.styles}} for in-game notifications
  
{{Note|If you are using an nvidia card through Bumblebee, you should prefix those commands with {{ic|optirun}}.}}
+
Both files are overwritten by Steam on startup and {{ic|steam.styles}} is only read on startup.
  
=== Tips ===
+
{{Note|Some games do not respect the setting in {{ic|gameoverlay.styles}} e.g. XCOM: Enemy Unknown.}}
  
==== Performance ====
+
==== Use a skin ====
  
Consider disabling wine debugging output by adding this to your shell rc file:
+
You can create a skin to change the notification position to your liking. For example to change the position to top right:
export WINEDEBUG=-all
 
or, just add it to your steam alias to only disable it for steam:
 
alias steam='WINEDEBUG=-all wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe >/dev/null 2>&1 &'
 
Additionally, Source games rely on a paged pool memory size specification for audio, and WINE by default does not have this set. To set it:
 
$ wine reg add "HKLM\\System\\CurrentControlSet\\Control\\Session Manager\\Memory Management\\" /v PagedPoolSize /t REG_DWORD /d 402653184 /f
 
  
==== Application launch options ====
+
$ cd ~/.steam/root/skins
 +
$ mkdir -p Top-Right/resource
 +
$ cp -r ~/.steam/root/resource/styles Top-Right/resource
 +
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*
  
Go to ''Properties > Set Launch Options'', e.g.:
+
==== Live patching ====
-console -dxlevel 90 -width 1280 -height 1024
 
* {{ic|console}}
 
: Activate the console in the application to change detailed applications settings.
 
* {{ic|dxlevel}}
 
: Set the application's DirectX level, e.g. 90 for DirectX Version 9.0. It is recommended to use the video card's DirectX version to prevent crashes. See the official Valve Software wiki http://developer.valvesoftware.com/wiki/DirectX_Versions for details.
 
* {{ic|width}} and {{ic|height}}
 
: Set the screen resolution. In some cases the graphic settings are not saved in the application and the applications always starts in the default resolution.
 
Please refer to http://developer.valvesoftware.com/wiki/Launch_options for a complete list of launch options.
 
  
==== Using a pre-existing Steam install ====
+
{{ic|gameoverlay.styles}} can be overwritten while Steam is running, allowing you to have game-specific notification positions.
  
If you have a shared drive with Windows, or already have a Steam installation somewhere else, you can simply symlink the Steam directory to {{ic|~/.wine/drive_c/Program Files/Steam/}} . However, be sure to do '''all''' the previous steps in this wiki. Confirm Steam launches and logs into your account, ''then'' do this:
+
{{hc|~/.steam/notifpos.sh|
 
+
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles
$ cd ~/.wine/drive_c/Program\ Files/
 
$ mv Steam/ Steam.backup/   (or you can just delete the directory)
 
$ ln -s /mnt/windows_partition/Program\ Files/Steam/
 
 
 
{{Note|
 
* If you have trouble starting Steam after symlinking the entire Steam folder, try linking only the {{ic|steamapps}} subdirectory in your existing wine steam folder instead.
 
* If you still have trouble starting games, use {{ic|# mount --bind /path/to/SteamApps ~/.local/share/Steam/SteamApps -ouser&#61;your-user-name }}, this is the only thing that worked for me with {{ic|TF2}}.
 
 
}}
 
}}
  
==== Steam links in Firefox, Chrome, etc ====
+
And the [[#Launch options]] should be something like:
  
To make {{ic|steam://}} urls in your browser connect with Steam in Wine, there are several things you can do. One involves making steam url-handler keys in gconf, another involves making protocol files for KDE, others involve tinkering with desktop files or the Local State file for chromium. These seem to only work in firefox or under certain desktop configurations. One way to do it that works more globally is using mimeo, a tool made by Xyne (an Arch TU) which follows. For another working and less invasive (but firefox-only) way, see the first post [http://ubuntuforums.org/showthread.php?t=433548 here] .
+
~/.steam/notifpos.sh TopLeft && %command%
  
* Make {{ic| /usr/bin/steam}} with your favorite editor and paste:
+
=== In-home streaming ===
  
{{bc|
+
Steam has built-in support for [http://store.steampowered.com/streaming/ in-home streaming].
#!/bin/sh
 
#
 
# Steam wrapper script
 
#
 
exec wine "c:\\program files\\steam\\steam.exe" "$@"
 
}}
 
  
* Make it executable:
+
See [https://steamcommunity.com/sharedfiles/filedetails/?id=680514371 this Steam Community guide] on how to setup a headless in-home streaming server on Linux.
 
 
# chmod +x /usr/bin/steam
 
 
 
* Install {{AUR|mimeo}} and {{AUR|xdg-utils-mimeo}} from AUR. You will need to replace the existing {{Pkg|xdg-utils}} if installed. In XFCE, you will also need {{Pkg|xorg-utils}}.
 
 
 
* Create {{ic|~/.config/mimeo.conf}} with your favorite editor and paste:
 
 
 
{{bc|
 
/usr/bin/steam %u
 
  ^steam://
 
}}
 
 
 
* Lastly, open {{ic|/usr/bin/xdg-open}} in your favorite editor. Go to the {{ic|detectDE()}} section and change it to look as follows:
 
 
 
{{bc|<nowiki>
 
detectDE()
 
{
 
    #if [ x"$KDE_FULL_SESSION" = x"true" ]; then DE=kde;
 
    #elif [ x"$GNOME_DESKTOP_SESSION_ID" != x"" ]; then DE=gnome;
 
    #elif $(dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetNameOwner string:org.gnome.SessionManager > /dev/null 2>&1) ; then DE=gnome;
 
    #elif xprop -root _DT_SAVE_MODE 2> /dev/null | grep ' = \"xfce4\"$' >/dev/null 2>&1; then DE=xfce;
 
    #elif [ x"$DESKTOP_SESSION" == x"LXDE" ]; then DE=lxde;
 
    #else DE=""
 
    #fi
 
    DE=""
 
}
 
</nowiki>}}
 
 
 
* Restart the browser and you should be good to go. In Chromium, you cannot enter a {{ic|steam://}} link in the url box like you can with Firefox. The forum link above has a {{ic|steam://open/friends}} link to try if needed.
 
 
 
{{Note|
 
* If you have any problems with file associations after doing this, simply revert to regular xdg-utils and undo your changes to {{ic|/usr/bin/xdg-open}}.
 
* Those on other distributions that stumble upon this page, see the link above for firefox specific instructions. No easy way to get it working on Chromium on other distros exists.
 
}}
 
  
==== No text rendered problem ====
+
== Troubleshooting ==
  
If there is no text/font rendered when starting steam you should try to start steam with the parameter {{ic|-no-dwrite}}. Read more in [https://bbs.archlinux.org/viewtopic.php?id=146223 the forum thread about it.]
+
See [[Steam/Troubleshooting]].
{{bc|wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Steam/Steam.exe -no-dwrite}}
 
  
 
== See also ==
 
== See also ==
  
* https://wiki.gentoo.org/wiki/Steam
+
* [https://wiki.gentoo.org/wiki/Steam Gentoo Wiki article]
* [http://appdb.winehq.org/objectManager.php?sClass=version&iId=19444 Wine Application Database]
+
* [https://pcgamingwiki.com/wiki/The_Big_List_of_DRM-Free_Games_on_Steam The Big List of DRM-Free Games on Steam] at PCGamingWiki
 +
* [http://steam.wikia.com/wiki/List_of_DRM-free_games List of DRM-free games] at Wikia
 +
* [http://store.steampowered.com/browse/linux Steam Linux store]

Latest revision as of 16:54, 4 April 2018

Steam is a popular game distribution platform by Valve.

Steam for Linux only supports Ubuntu 12.04 LTS and newer [1]. Valve does not offer any support when running into issues with Steam on Arch Linux.

Installation

Enable the Multilib repository and install the steam package.

The following requirements must be fulfilled in order to run Steam on Arch Linux:

SteamCMD

Install steamcmdAUR for the command-line version of the Steam.

Note: This package installs files under root, so you must run SteamCMD as root.

Alternative Flatpak installation

Steam can also be installed with Flatpak as com.valvesoftware.Steam from Flathub. The easiest way to install it for the current user is by using the Flathub repo and flatpak command:

 flatpak --user remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
 flatpak --user install flathub com.valvesoftware.Steam
 flatpak run com.valvesoftware.Steam

The Flatpak application currently does not support themes. Also you currently can't run games via optirun/primusrun, see Issue#869 for more details.

The Flatpak application has some known issues with Steam Auto-Cloud so game progress may not be synced unless you create some symlinks by hand for affected games.

By default Steam won't be able to access your home directory, you can run the following command to allow it, so that it behaves like on Ubuntu or SteamOS:

flatpak override com.valvesoftware.Steam --filesystem=$HOME

Directory structure

The default Steam install location is ~/.local/share/Steam. If Steam cannot find it, it will prompt you to reinstall it or select the new location. This article uses the ~/.steam/root symlink to refer to the install location.

Library folders

Every Steam application has a unique AppID, which you can find out by looking at its Steam Store page path.

Steam installs games into a directory under LIBRARY/steamapps/common/. LIBRARY normally is ~/.steam/root but you can also have multiple library folders (Steam > Settings > Downloads > Steam Library Folders).

In order for Steam to recognize a game it needs to have an appmanifest_AppId.acf file in LIBRARY/steamapps/. The appmanifest file uses the KeyValues format and its installdir property determines the game directory name.

Usage

steam [ -options ] [ steam:// URL ]

For the available command-line options see the Command Line Options article on the Valve Developer Wiki.

Steam also accepts an optional Steam URL, see the Steam browser procotol.

Launch options

When you launch a Steam game, Steam executes its launch command in a Bash shell. To let you alter the launch command Steam provides launch options, which can be set for a game by right-clicking on it in your library, selecting Properties and clicking on Set Launch Options.

By default Steam simply appends your option string to the launch command. To set environment variables or pass the launch command as an argument to another command you can use the %command% substitute.

Examples

  • only arguments: -foo
  • environment variables: FOO=bar BAZ=bar %command% -baz
  • completely different command: othercommand # %command%

Tips and tricks

Big Picture Mode without a window manager

To start Steam in Big Picture Mode from a Display manager, create a /usr/share/xsessions/steam-big-picture.desktop file with the following contents:

/usr/share/xsessions/steam-big-picture.desktop
[Desktop Entry]
Name=Steam Big Picture Mode
Comment=Start Steam in Big Picture Mode
Exec=/usr/bin/steam -bigpicture
TryExec=/usr/bin/steam
Icon=
Type=Application

Steam skins

The Steam interface can be customized using skins. Skins can overwrite interface-specific files in ~/.steam/root.

To install a skin:

  1. Place its directory in ~/.steam/root/skins.
  2. Open Steam > Settings > Interface and select it.
  3. Restart Steam.

An extensive list of skins can be found in this Steam forums post.

Note: Using an outdated skin may cause visual errors.

Creating skins

Nearly all Steam styles are defined in ~/.steam/root/resource/styles/steam.styles (the file is over 3,500 lines long). For a skin to be recognized it needs its own resource/styles/steam.styles. When a Steam update changes the official steam.styles your skin may become outdated, potentially resulting in visual errors.

See ~/.steam/root/skins/skins_readme.txt for a primer on how to create skins.

Changing the Steam notification position

The default Steam notification position is bottom right.

You can change the Steam notification position by altering Notifications.PanelPosition in

  • resource/styles/steam.styles for desktop notifications, and
  • resource/styles/gameoverlay.styles for in-game notifications

Both files are overwritten by Steam on startup and steam.styles is only read on startup.

Note: Some games do not respect the setting in gameoverlay.styles e.g. XCOM: Enemy Unknown.

Use a skin

You can create a skin to change the notification position to your liking. For example to change the position to top right:

$ cd ~/.steam/root/skins
$ mkdir -p Top-Right/resource
$ cp -r ~/.steam/root/resource/styles Top-Right/resource
$ sed -i '/Notifications.PanelPosition/ s/"[A-Za-z]*"/"TopRight"/' Top-Right/resource/styles/*

Live patching

gameoverlay.styles can be overwritten while Steam is running, allowing you to have game-specific notification positions.

~/.steam/notifpos.sh
sed -i "/Notifications.PanelPosition/ s/\"[A-Za-z]*\"/\"$1\"/" ~/.steam/root/resource/styles/gameoverlay.styles

And the #Launch options should be something like:

~/.steam/notifpos.sh TopLeft && %command%

In-home streaming

Steam has built-in support for in-home streaming.

See this Steam Community guide on how to setup a headless in-home streaming server on Linux.

Troubleshooting

See Steam/Troubleshooting.

See also