Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuậ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.