Инсталирайте 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