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've tried making exceptions via Windows Defender/AV settings. Doesn't work.
I don't use Galaxy to launch, I use Playnite. I've tried launching through that, and direct from exe. Doesn't work.
i'm asking you, if you're attempting to launch it direct from the x64 folder? - because as far as i remember, "you're not supposed to"
so if that's what you're doing, then it makes sense
i've no idea what playnite does, or if it too is attempting to launch the "wrong way"
in you grim dawn install folder you should find a shortcut called "launch grim dawn"
that's teh one you're supposed to use
otherwise use the 32bit exe with a /64 command, as far as i remember i've "never" been able to use the exe directly in/from the x64 folder on my GoG install
^might totally remember wrong, but i'm pretty sure i've had to use the shortcut or /64 command for a while
Seems you cracked the problem for me, as testing the launch shortcut by itself worked. Normally Playnite will pick up the correct way to launch the games automatically via importing game installs, but in this case, I had to manually point it to the launch shortcut, which fixed it. Much thanks for the solution.