Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский)
Español - Latinoamérica (латиноам. испанский)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский)
Português-Brasil (бразильский португальский)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
Luckly this will be a heads-up for AMD to improve their Linux support and realize that we are a lot more relevant then they think.
Cheers.
Perhaps Steam linux users not rushing in droves to AMd is symbolic of their future :o)
If that's doesn't create an impression...wish them luck ;)
well, that's another point of view.
After checking today I've seen that only a handfull of posts have been made, I would expect it to be a lot higher.
I folowed your suggestion and posted my opinion there, let's just hope that AMD upgrades the drivers a bit further.
Well it's obvious that the driver doesn't support the hd4xxx cards.
It's obvious too, at least to me, that the performance of TF2 and Killing floor is pants on AMD cards like the HD6xxx
What is not obvious is why. But I can't really see how posting there will help discover that.
It could be that the port of killing floor is just "get it to work", in which case, we're SoL. I don't know. Maybe Ryan would say "No, my port is sound, it's the driver" maybe the driver author would say "No, it's the port".
Rinse and repeat for TF2. Is the 100% cpu usage of the non-game steam process the reason the performance sucks? If so, what can AMD do about that? Or is it their driver?
Or should we even care yet? There's a certain "it's a beta" aspect to things too.
Surely the only people who can get together and have the bun fight to answer these questions are Valve, Ryan and AMD? What are we supposed to do? Fetch the coffee? Pick a side? :)
But if AMD need me to tell them what's wrong now, don't give me the forum, give me the job - because, it's obvious what's wrong from where I'm sat. The only real puzzle is why and whose bit of code is broken. Send me the source to both and I might figure it out.
But, the only other thing I can do is run the code you all release and say "it sucks" - I'm not even great at putting it nicely.
What does cloud the issue is, for example Michael Larabel writing things like this " (Note: For those who play Team Fortress 2, Valve recently released an update to the game that dramatically improves the performance when using AMD Radeon hardware with the Catalyst driver.) " which, ok, Michael's not a gamer, perhaps he reporting that on faith. But who told him they'd improved the performance?
Have Valve got the game running fast on AMD? Are they puzzled why some of us haven't?
Because everything I've seen from valve about source engine game performance on linux (whether directly from them, on the blog, or via news reports like the above) suggests that either someone at valve lives in a fantasy world, or they have a very different set up or drivers or some aspect of their system that's different from what we appear to have)
All of which leads me to the conclusion that Valve have as much information to give us as AMD do. I haven't seen a single "It's amd's fault their drivers suck" (even couched in more diplomatic terms - which I can't do. Which is another reason I'm reluctant to post on their forum because I won't help the situation by posting) response to any of the myriad "TF2 performance" threads in here.
Bottom line, it's £100-200 to get rid of a performance problem iff it's caused by AMD. Less if you sell the old card on Ebay - and it works in windows in the meantime so there's not a lot of reasons to lose sleep over it from our side.
They aren't asking you to tell them how to fix it. They want to know what problems are affecting users and what the approximate proportions are so they can do a sort of triage and handle the big issues first. Mentioning that you experience problem X is useful to the whole process. Not mentioning it and waiting to see whether or not things get fixed is also just fine.
It's all about the data. this is your chance to provide that data and voice your concerns in their forum.
Thanks.