Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
So far no official announcement mentioning the bug, recommending hold off updating, nor providing a path for those affected to return to 3.4.11, not only they rushed the release of 3.5, they seems reluctant admitting the mistake or letting folks to back to the stable build they once were, I am unable to play some of the demanding games for nearly a week with no remedy / temporary solution, that is not good I'd say...
They didn't downplay the severity of it.... They did say the bug exist. The overlay might be a symptom of a larger issue. The switching itself isn't the bug but a symptom. They are asking whether their fix works and the scope.
To your credit and Alecslee, you guys did contribute interesting enough data point where I will probably hate this bug and Linus T might rant a bit. I do not want to be right at all. I hope Valve believe this bug is different from what I am thinking.
This comment is a thank you for your efforts.
I am sympathetic with Valve because I have a faint idea about the bug itself. This bug will make operating system engineers rant a ton. I believe Microsoft probably deal with this bug every new Windows release.
Tried everything as well, sometimes mine even reboot right after the game launches lol. Totally unplayble atm