Constantly updated Steam version. All languages.
Please specify video card and video driver version when submitting test results.
There is a native Linux version of this game.
fullscreen and window mode
Setting direct x level to 8.1 to improve fps
I haven't been able to play for about a year because of the massive lag spikes down to 0 fps. I was finally able to solve this by setting tf2 to use only a single core because it would spike when the cpu utilisation would go over 100% making the game unplayable.
taskset -pc 0 tf2pid
where tf2pid is the process id of the running tf2 which can be found using:
ps ax | grep hl2
I have to use this on my Core 2 quad most people who seem to have newer cpus don't have this problem ie amd phenoms and i7/i5's which is why I found it weird that the game couldn't be run at all but everyone else was giving it a platinum rating.
What does not
Cannot run without using taskset like in what works section because once cpu utilisatin goes over 100% and it gets spread over cores it gets ugly and lags down to 0-5 fps making the game unplayable once you leave the spawn area.
What was not tested
Playing longer then 30mins
Run on 3.4.2-2 Intel Core 2 Quad Q6600 @ 3.00ghz Nvidia 480 gtx @ 295.53 Virtual Desktop 1680x1050 tf2 details: everything on high 1680x1050 resoultion fullscreen Getting 60-120fps
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)||Nov 08 2016||1.8.5||Yes||Yes||Platinum||an anonymous user|
|Show||Ubuntu 15.04 "Vivid" amd64 (+ variants like Kubuntu)||Jul 28 2015||1.7.44||Yes||Yes||Platinum||an anonymous user|
|Show||Linux Mint 14 "Nadia" x86_64||Jan 03 2013||1.5.20||Yes||Yes||Gold||an anonymous user|
|Show||Arch Linux x86_64||Nov 25 2012||1.5.18||Yes||Yes||Bronze||an anonymous user|
|Show||openSUSE 12.2 x86_64||Nov 03 2012||1.5.14||Yes||Yes||Gold||Tarik|
|Bug #||Description||Status||Resolution||Other apps affected|
|5159||Microphone xmit in Half Life and HL:S games very harsh and goes in and out of "focus"||REOPENED||View|
|24684||Multiple Source engine based games (Steam): out-of-order rendering, bloom effect and lights are visible through walls when multicore rendering is enabled||NEW||View|
|27453||Lag when loading new sound in source games||NEW||View|
This section is Optional how ever it may greatly improve the stability and frame rate you achieve with TF2.
Team Fortress 2 can be run from Steam or from the command line.
To start TF2 using the command line:
WINEDEBUG=-all wine ~/.wine/drive_c/Program\ Files/Steam/steam.exe -applaunch 440 -nointro
This bug was introduced in a TF2 update at the start of 2010. Another update ~May 2010 is believed to have fixed it. If you are still experiencing this bug, please comment on bug #21534. There are two potential solutions.
1) The bug can be worked around by playing TF2 at a resolution with less than 1024 pixels of height.
2) A minor edit to the theme of TF2 fixes the crash consistently.
Thanks to rasmus.ry for posting this. More information is available in bug #21534.
In the most cases, this bug is caused by the Steam In-Game Overlay, to solve Open your winecfg, go to Libraries, add a new Library called gameoverlayrender and set to disabled, the Steam In-Game Overlay and screenshot will not work.
Note: Also solved by properly compiled Wine with supported gcc versions.
If you can connect to some servers and not others consistently it is most likely caused by the MOTD displayed at the start of any match. This can disabled for all servers via the in-game options.
Options -> Multiplayer -> Advanced -> Disable MOTD (checkbox).
This also happens with some languages has some symbols that Wine can't handle and Team Fortress 2 is a game that is full translated, so, when you connect some servers the engine load this fonts and crash TF2, to solve-it just set language of Steam to english, all the games will be english. This bug happens with portuguese, but, can happen with other languages as well.
Unfortunately there are many reasons for these crashes. Try reducing screen resolution, lover video settings (shadow, textures quality, etc). If the bug is consistent please consider reporting it or filing a bug report if one doesn't already exist.
See bug #23578. Valve updated their anti-cheat code with the Engineer update and WINE did not handle this well. This bug also affected at least some other games launched from Steam. There is a fix for this in git after 21 July 2010. All 1.3.x versions should contain this fix. 1.2 does NOT contain this fix, but the patch applies cleanly to the 1.2 source. 1.2.1 does contain this fix, so the most recent stable or the most recent development versions should just both work fine now.
This is caused by the new implementation of mouse input in wine, to solve-it, you need to run the game in Windowed mode or into a Virtual Desktop.
Thanks to Frozen Fox and others, this bug has another solution that is download and install a Wine version to before than 1.3.20 (because this is the version that was set the new mouse implementation).
Download here the Source for Wine 1.3.19.
Note: This bug was solved in the newset versions of wine.
This bug is related with the last Team Fortress update and some nvidia video cards, you can solve it by adding -nod3d9ex at the launch option into the game, to do that, right click at the game on steam, go to Proprieties and click into Set Launch Options.
If Team Fortress 2 crash and you can't solve, you can try these steps:
Right on-time for holidays Valve delivers!
Valve's post on Steam for Linux forum.
The Steam for Linux beta program is now open to the public! In order to participate in the beta, you must download the latest Steam Linux client (found here) or upgrade your existing Steam for Linux client to the latest version.
In addition, we will now track Steam for Linux client bugs using GitHub. This provides a better interface for tracking bugs than the forums used in the closed beta. The Steam for Linux repository (currently empty) is public, allowing anyone with a free GitHub account to create a new issue and edit or track it and search the existing bug database. The repository contains a readme file (README.md) detailing how to create a new issue (it describes the same format used in the closed beta).
The team will continue working through existing issues in the forum but it is strongly recommended that any new issues be entered using GitHub's issue tracking interface. The sub forums will remain open so that people can join/continue existing discussions about the Steam for Linux client.
And last but not least, we now have a steam installer package repository. There is a mailing list for announcing updates to the steam installer package. To subscribe, use the public mailman page located here: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/steamrepo.
dpkg-deb -xv steam_latest.deb /tmp/steam
tar xJf /tmp/steam/usr/lib/steam/bootstraplinux_ubuntu12_32.tar.xz -C ~/Steam