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.