Skip to content
Ryan G edited this page Sep 20, 2013 · 1 revision

This guide will help to install the requirements needed to get Steam-based games working with your GamePanelX installation.

Table of Contents

Requirements

Packages: glibc 32-bit, libstdc++ 32-bit

The "uncompress" command also needs to be available.

 sudo ln -s /usr/bin/gunzip /usr/bin/uncompress
 sudo yum install glibc.i686 libstdc++.i686 libgcc_s.so.1 libgcc.i686

More info here: https://developer.valvesoftware.com/wiki/SteamCMD#32-bit_libraries_on_64-bit_Linux_systems

You also may need to make sure SELinux is disabled.

Installing a Steam Game

Go to create a new template, select your Steam-based game from the games list, and make sure to leave the File Path blank. Then Press Save to create the template automatically.

Local Servers

If running a Local server (which is default) instead of Remote, make sure Steam has a .steam directory in the webserver user's home directory. If steam can't create this, it will fail. You can see this error in your /var/www/html/games/_SERVERS/logs/steam.log:

 SteamInstall: (Fri Jun 28 18:50:22 PDT 2013) Finished hldsupdatetool.bin.  Running ./steam ...
 SteamInstall: (Fri Jun 28 18:50:22 PDT 2013) Steam client update failed: Checking bootstrapper version ...
 Failed to create directory /var/www/.steam

Solution:

 sudo mkdir /var/www/{.steam,Steam}
 sudo chown apache: /var/www/{.steam,Steam} -R

This will work on CentOS and Ubuntu. On other distros just figure out the homedir of Apache and create .steam in there with proper permissions.

Steam Logs

There are several logs available for Steam. General Steam info, for the initial connections to Steam, can be found in:

hldsupdatetool: /usr/local/gpx/logs/steam.log

SteamCMD: /usr/local/gpx/logs/steamcmd.log

When creating a new Template, the steam log for the actual game installation has it's own file. It is based on the template ID, and is in tmp/steam_X.log. Where X is the template id; for example:

Remote:

 /usr/local/gpx/tmp/steam_3.log

Master:

 <path to webroot/gpx>/_SERVERS/tmp/steam_3.log

If your template ID was 3, this would be the location.

Troubleshooting

steam_appid.txt issue

The "steam_appid.txt" file that resides in the steam working directory for SteamCMD games comes with an invalid character in it by default. To fix this, edit the <working></working>/steam_appid.txt file, and make sure only the app ID and an empty line below it are present.