安装 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 have never seen anything close to this happen before, so I'd hazard a guess and say it might be memory related, or overclocking related. Some bit flip somewhere surely!
---
S0L
---
I'll be sure to do that, though it was just a random thing that happened when trying to load in, nothing specific that I did to cause it. At least nothing that I'm aware of anyway.
This basically amounts to telling him to "push random buttons as much as you can until something explodes". Bonus points for not looking while you do it.
I wonder if it's related to minimizing the game, since I managed to crash the game by doing so during the bonus chance loading screen in an online match. I did mine for Teamspeak, but still, mine also resulted in the standard ASN stopped working crash, where as something just outright failed on your end.
I should explain :P
Whenever QA find a completely random bug that simply can't be replicated (and especially when it's reported once and there are no real details on how it happened...) then I generally tell them that.
Sometimes weird things happen. You spend days attempting to reproduce it, but never see it again...!
Hence 'When you do it again, let me know' :P
---
S0L
---