安装 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.