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