Login
|
language
Български (Bulgarian)
čeština (Czech)
Dansk (Danish)
Nederlands (Dutch)
Suomi (Finnish)
Français (French)
Deutsch (German)
Ελληνικά (Greek)
Magyar (Hungarian)
Italiano (Italian)
日本語 (Japanese)
한국어 (Korean)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
Português-Brasil (Portuguese-Brazil)
Română (Romanian)
Русский (Russian)
简体中文 (Simplified Chinese)
Español (Spanish)
Svenska (Swedish)
繁體中文 (Traditional Chinese)
ไทย (Thai)
Türkçe (Turkish)
Українська (Ukrainian)
Help us translate Steam


Known problems include tearing and poor overlay performance in-game; please install them and post your feedback!
The only problem I'm currently having is the HDMI audio isn't working in game. I hear audio when in the steam menus but never in game.
If you have an AMD card <5000 it probably isn't supported anymore. My notebook has a 4270 and the latest supported catalyst is 13.1. So I just use the open source drivers on that one, and propietary on my desktop
1- My xbox360 controller now shows a steady light (Sometimes)
2- Performance in L4D2 , Trine 2 , Awesomenauts is much better . Also the games load without hanging on the spinning loading screen .
3- swapping between ingame and steam (xbox360 button) is A LOT faster now . Very smooth .
Negative :
1- Assault android cactus demo hung on the spinning loading screen when loading . This is not always the case , but happens sometimes . Also performance in this game is really poor .
2- After rebooting the xbox 360 controller starts to flicker again . Shutting down the machine completely and booting up shows again a steady light . But this also doesn't always work .
3- When being signed in elsewhere , eventough i have remember my password ticked , it still prompts for my password .
Awesome work with the updates ! Keep them coming .
I just tried L4D2. The performance is good. But if I activate VSync, it makes still problems for me. Then I have an input lag or something and looking around with the mouse doesnt feel smooth.
And adjusting the gamma value in the game options has still no effect.
I know that is not SteamOS related. But maybe someone can confirm these problems also on SteamOS.
No it doesn't afaict. The performance is dire. Have you tested it?
Please. Get a machine with something like i5 2500k/ 8gb ram/HD5850 and 120hz monitor and tf2 config and then play TF2. You know TF2? It's a great game made by Valve.
Load ctf_2fort and join a server.
Play it in windows - enjoy the silkly smooth 120fps/120hz gameplay (except when pvhud updates charge bars - but that's another issue)
Now do the same in linux with any AMD driver from the steam linux beta forwards.
They all suck. Try jumping in the water and experience the lag and stutter.
It plays worse than when I used to own a 7600gt card.
Sit anyone down at Valve that thinks linux performance is good at this machine - throw his GTX780 out the window and hit him with a cluebat until he acknowledges the problem. Sit someone from AMD down and do the same.
I had a bit of hope when you shipped SteamOS without AMD support you were going to do it right this time. But no, they've justed taken what already doesn't work on linux and changed it to not work in this new distro. The same useless drivers not working in your new OS.
Worse, they get you to say performance has improved. Where exactly?
Think of all those people who might buy a Steam machine that has AMD in it - they need someone speaking honestly about it.
And please stop typing stuff like "This build should fix the poor in-game performance" until you've actually tested it. You make yourselves sound like muppets especially as and when numerous media sites pick up on this and make a story of it.
I see how AMD are successful, they get various people to lie, perhaps unwittingly, about their drivers. A fabricated line in a driver changelog becomes a fact that's parroted without testing by Valve, by the buffoon that posts catalyst updates to twitter and by a heap of tech journalists.
I'm not sure how this affects SteamOS, but these drivers crash X if you use youtube from google chrome (and numerous other things) with asserts in hal_evergreen.c line 69 - and they are a complete abortion if you enable 2 screens, one at 120hz and one at 60hz and try to play a game (Although this latter may be just an issue with the way X works - although the same set up works fine in windows 7)
Better for what or whom? The problem won't be fixed if you and others decide it's someone else's problem.
It's not exactly Valve's problem to write drivers for AMD's graphics hardware, it's AMD themselves who will need put more effort in to ensure their users have good performance under Linux and not just Windows, especially if enough people complain to them.
It is exactly the result of what Valve have said that all these media reports, threads here and reddit threads have appeared saying "Now SteamOS supports AMD" - it doesn't. The drivers suck.
There's nothing stopping Valve being honest about the drivers in their OS though - or is there?
They've not been honest AFIAA once in the entire process from Steam Linux Beta launch until this thread appeared.
They've dodged the issue. They've reported nvidia performance as "linux performance" in blogs and in talks they've done with nvidia alongside them. They've basically told anyone who pointed out the AMD drivers suck to go and post to AMD's forums (that I pointed out at the time would be a waste of time - and it was)
Plus, it could be TF2 that's at fault - I doubt it - but it could be. Valve pontificate at length about how great their hires are at managing themselves and they could all be running the company owning problems etc.
Sheesh, what do we have so far - an OS that you can't even install because they've hamfistedly butchered debian and reduced the number of install options it has. That won't even install a dual boot alongside windows and that doesnt have 3d drivers that work well enough to play games unless you own a nvidia card.
Well here I am looking for 1 Valve employee with a clue to take the problem on and sort it. And if Valve can't get AMD to deliver good drivers - which let's face it, we all know is highly probable - they certainly can state that fact rather than standing at CES saying "look at all these great Steam machines you should buy" - many of which will suck because they'll have crappy driver support.
The point at which they can say "It's somebody else's problem if the OS sucks" is over - it's called SteamOS now.
Besides which they are in the best position to tell AMD exactly what the problem is - they have the source code to TF2 and can therefore do more analysis than simply posting to an AMD forum "your linux drivers make TF2 suck" - Valve should know exactly why they suck and they've had months to have done this (and they've done it with nvidia drivers and then have done talks describing all these tools they used)