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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
The mod is already updated for 2.4, has no visible internal file errors, and I also just launched a campaign with only this mod enabled and another one with other mods enabled: no crashes.
You might want to investigate other mods that are actually outdated that might be the cause of your issue or check the comment sections of the mods your are subbed to to see if someone else is experiencing any crashes after a recent update.
There is a minor chance that Steam didn't download properly a mod update, in that case it is best to unsub a re-sub to that mod to fix the issue.
I can't possibly know what's going on with you but try the following:
-Verify integrity of game files
-Try to launch the game with only my mod enabled
-If you get another CTD then try to unsub and re-sub to this mod and launch the game.
You should now be able to launch the game without issues, but if you get another CTD upon re-enabling the other mods you are currently subbed to, then you'll have to investigate and find the mod that is causing your crash in the first place.