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
---