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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
1) I've put up a beta build on Steam with some potential fixes and additional logging. To access that go to the game in your library, right click on it and go to Properties. Then in the Betas tab select "Beta" from the dropdown menu. Use "Verify Game File Ingregity" in the Local Files tab to force the update.
2) If you're having problems still, please do not post to this thread, follow the instructions here http://subsetgames.com/contact.html, sending both the log file and the dxdiag report, and we can try to help more effectively!
This is the first time it happened to me. Not other game on Steam has had the AV reacting this way. If I had to guess, taking into account the .exe file is called "breach", I can see why an AV can get all nervous when an executable file that is called that way is getting any sort of attention in hte background.
Anyhow, just check your AVs lists to check it is not blocked and it is dutifully excepted.
Great game by the way, lol
Thanks for the update Matthew, love the game and managed to fix my problem with a couple of reboots. No idea what was causing it but no recurrences.
https://imgur.com/a/omhn2