Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
however, if the offending mod is a large/overhaul mod then your save is probably doomed to have that crash.
once you have found the offending mod, you can disable that mod and try loading that save and do sieges and see if it's any better.
As I google, the problem with crashing during castle sieges is not new, and definitely not only my problem:/
also i don't play native at all so i can't comment on it
To use mods with this game is a Grind on top of the game grind.
So yes O.P. the castle seige CTD is a nightmare. But posting it here will not help, venting frustration here is a waste of time, this is more for cosy chats or somthing.
Well there you go.
Delete your mods completely. (Here's how to remove modification -- https://steamcommunity.com/app/261550/discussions/17/2968397584539744282/ )
Uninstall and reinstall your game.
Delete your save games because they are probably corrupted.
Then come back here and let us know if that worked.
Because sieges are the most taxing when it comes to resource load.
Have you tried if you can replicate the issue with lower battle size? The reason is because when you do a benchmark you can clearly see that there are more CPU spikes the higher battle size you go.
Try 600 or 800 and try a couple sieges.