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
I don't know about you, but I find it more fun to work with 24000 points with ships. If you also find yourself liking that high limit, then I'd love for that to be a part of 1.04. If you don't like that, I'll just continue using the sandbox to set it.
Perhaps that website can quicken your pace, in which case I'll leave you a link for you to decide for yourself. "Reassembly Web Development Kit" http://atg.lychnobi.com/ttftcuts/rwdk/
I would suggest oppening up all of the .lua files and looking at the comments, shaps.lua, factions.lua, regions.lua, and blocks.lua.
A few things you can do.
1 Try increasing these two CVARs
kMempoolMaxChain = 20
kBlockMemoryPoolSize = 8000
2 Try running with smaller live radius (try 8000)
kLiveRadius = 8000
3 if you can load your save, try going to a different part of the map, the overcrowded sectosr will get cached away and you should be OK.
4 If you can't load your save, if you do a regenerate world this should clear up. On my system I only see this error very seldom (I've done 2 play-thrus myself).
I will play with the max chain doubled for a bit, if that doesn't crash anything I'll push that into the public mod for everyone to, I hope, reduce the occurance of this.
I had figured I'd get more complaints about lag than memory issues.....
I was afraid people would run into this. This happens becasue I made a trade-off between having more stuff in the mod vs stability. The game base code only asks for so much OS memory (I think), and when you have a lot of stuff going on with a large live radius, it runs out.
The alternative would have been a smaller live radius (not as much fun), or less ships/buildings (not as much fun). The buggest offenders are faction 2 and faction 3 for memory crashes, tho sometimes faction 11 and 15 do this.
core\stl_ext.cpp:308:MemoryPool::allocate ASSERT(Memory Pool): 10/10 pools allocated! No memory available
terminate handler called
core\stl_ext.cpp:125:myTerminateHandler ASSERT(Terminate Handler): Exception: bad allocation
I tried upping the memory and it made the same error?