Установить 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