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
There's a bunch of different ways this error can be created, but the most common way is making a recursive function, which just means to make a function re-execute itself.
There are valid reasons why one might make a recursive function, but if you're not careful, they can endlessly keep executing themselves and reach that stack limit quickly, since they never finish executing.
I'm going to take a wild guess and say that Reassembly maybe uses a recursive function for rendering blocks on a ship, and that 400000 block limit is the max stack limit.
Since you have a ship with 455522 blocks, It's exceeding that limit and causing the stack-overflow error.
That's strange. I don't think I've ever made or had a mod that includes ships that large. At the time of both crashes I was starting a new save with the factions, so there weren't any designs of mine that saved over. At the same time, if the error might be the amount of blocks in one ship being too high, how did it cause a crash of the same type that didn't exceed that limit? :<