FTL: Faster than Light

Dependencies

Compatibility

The Steam overlay in FTL does not function as it is not a 3D accelerated game. Because of this the desktop notifications will be visible. If playing in fullscreen, therefore, these notifications in some systems may steal focus and revert you back to windowed mode with no way of going back to fullscreen without relaunching. The binaries for FTL on Steam have no DRM and it is possible to run the game without Steam running, so in some cases that may be optimum - just ensure that you launch FTL via the launcher script in ~/.steam/root/SteamApps/common/FTL Faster than Light/data/ rather than the FTL binary in the $arch directory.

Killing Floor

トラブルシューティング

画面解像度

Killing Floor runs pretty much from scratch, although you might have to change in-game resolution screen as the default one is 800x600 and a 4:3 screen format.
If you try to modify screen resolution in-game, it might crash your desktop enviroment.
To fix this, please set the desired resolution screen size by modifing your ~/.killingfloor/System/KillingFloor.ini with your prefered editor.

Note: Replace all the ???? with the corresponding numbers according the desired resolution. If you have an 1366x768 screen and want to use it at it's fullest, change all the Viewport fields to something like ViewportX=1366 and ViewportY=768 in the corresponding areas.

Note: The dots in the middle indicate that there are more fields in that .ini file. But for screen resolution troubleshooting, you don't need to modify anything else.

Save the file and restart the game, it should work now.

ウィンドウモード

Uncheck fullscreen in the options menu, and use Ctrl-G to stop mouse capturing (that was non obvious to discover..). This way you can easily minimize it and do other other things..and let your WM handle things.

すでにインストール済みの Steam を利用する

Windows とドライブを共有していて、どこかに Steam をインストールしている場合、Steam ディレクトリから ~/.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:

Note: If you have trouble starting Steam after symlinking the entire Steam folder, try linking only the steamapps subdirectory in your existing wine steam folder instead.

Note: If you still have trouble starting games, use sudo mount --bind /path/to/SteamApps ~/.local/share/Steam/SteamApps -ouser=your-user-name , this is the only thing that worked for me with TF2

Running Steam in a second X Server

Assuming you are using the script above to start Steam, make a new script, called x.steam.sh. You should run this when you want to start Steam in a new X server, and steam.sh if you want Steam to start in the current X server.

Because the second X server is only running the game and the first X server with all your programs is backgrounded, performance should increase. In addition, it is much more convenient to switch X servers while in game to access other resources, rather than having to exit the game completely or Template:Keypress-Template:Keypress out. Finally, it is useful for when Steam or WINE goes haywire and leaves a bunch of processes in memory after Steam crashes. Simply Template:Keypress + Template:Keypress + Template:Keypress on the second X server to kill that X and all processes on that desktop will terminate as well.

If you get errors that look like "Xlib: connection to ":1.0" refused by server" when starting the second X: You will need to adjust your X permissions.

If you lose the ability to use the keyboard while using Steam: This is an odd bug that does not happen with other games. A solution is to use a WM in the second X as well. Thankfully, you do not need to run a large WM. Openbox and icewm have been confirmed to fix this bug (evilwm, pekwm, lwm do not work), but the icewm taskbar shows up on the bottom of the game, thus it's recommended to use Openbox. Install openbox from the official repositories, then add openbox & to the top of your steam.sh file. Note you can run other programs (ex. Teamspeak &) or set X settings (ex. xset, xmodmap) before the WINE call as well.

Steam Links in Firefox, Chrome, Etc

To make 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 here .

Restart the browser and you should be good to go. In chromium, you cannot enter a steam:// link in the url box like you can with firefox. The forum link above has a 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 /usr/bin/xdg-open.

Note: 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.