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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
I tried to find the cause of this and so far I've found that it starts when you open a game page in the new library and stops when you return to the "home" page of the new library. Closing the window or selecting other "tab" in the client (store, community...) won't stop it, as if the game page was still opened (loaded in the memory but not displayed) and Steam was still working on it.
They sacrificed a winning recipe for this noob design. Probably a pencil pusher that never played a video game in his life even less used Steam and told the guys responsible for programming this junk to make such a poor interface.
The webhelper processes initially took care of only Steam friends and the overlay but with the new library they expanded the amount of things it handles.
Also the new steam client beta has introduced some performance improvements