Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem








If you have met one of those overflows, it will be likely this mod is the source of crash, but that is because this mod has many complex mechanisms and it might just cross the critical point to cause the overflows.
For the overflow of trinkets, you might solve the crash after uninstalling certain numbers of trinkets.
For the overflow of heroes, you might solve the crash after uninstalling certain numbers of heroes.
The above two overflows are only concerned with numbers, not with specified mods.
For the overflow of save files, if yours is larger than 15MB, it might crash at any time...If you still can load the save, try dismissing heroes. If you can't, only the DDSaveEditor might be able to help you...
For the overflow of memory allocation, or known as MOD LIMIT, can be solved partially by using the official commandline " -disable_monster_pre_loading" and the 4GB expanded memory allocation main program.