I lol'd.Cozur said:Bump.
Cozur said:I've never been able to duplicate the whole crashing thing on either of my machines, so I'd be very interested if someone had a solution, as it does seem to happen on too large a segment of the users.
Cozur said:4k on one, 2k on the other.
Doesn't accumulate on my PC.
Stravask said:Cozur said:4k on one, 2k on the other.
Doesn't accumulate on my PC.
Odd. I've got 8k and still crashing.
Sucks to be us I guess. *shrug*
Cozur said:Stravask said:Cozur said:4k on one, 2k on the other.
Doesn't accumulate on my PC.
Odd. I've got 8k and still crashing.
Sucks to be us I guess. *shrug*
Have you tried the non-steam version? No idea why it should matter, but that's the one I play.
Stravask said:It seems the mod doesn't dump any unused information or something, as the process seems to just accumulate usage until the whole thing goes kablooey.
Anyone got any programs or tweaks they've found that'll hopefully make the game run slightly longer?
SilverFaith said:Stravask said:It seems the mod doesn't dump any unused information or something, as the process seems to just accumulate usage until the whole thing goes kablooey.
Anyone got any programs or tweaks they've found that'll hopefully make the game run slightly longer?
you need a 64 bit system and over 6GB, without it
you will crash all the time
other then that I don't know , are you using battle sizer ? you could try dropping the amount of soldiers per battle
Dusk Voyager said:With due respect to Cozur's work, there are a lot of more stable mods despite their resources and complex coding, so he should try optimizing his codes.
Cozur said:Dusk Voyager said:With due respect to Cozur's work, there are a lot of more stable mods despite their resources and complex coding, so he should try optimizing his codes.
What.
Swyter said:Cozur said:Dusk Voyager said:With due respect to Cozur's work, there are a lot of more stable mods despite their resources and complex coding, so he should try optimizing his codes.
What.
Try doing a bit of housekeeping. Don't worry about where to start, there is always stuff which shouldn't be there.
Try to remove as much crap as possible without removing features.
Less is more, specially talking about unused assets.
As a bit of an experience I removed more than 280MB of stuff from The Last Days in a pair of days. Apart from dedicating some time to fix their assets reducing polycount where necessary, converting DXT5/DXT3 textures with blank alpha channels to DXT1, adding LODs, turning polygonal collision meshes into something cheaper performance-wise, like decomposing them manually into basic shapes like cylinders/pills, boxes, spheres, and all that jazz.
It isn't a very flashy or gratifying task, but is necessary. Even more in bigger projects. Performance is more important than graphics.
And people with not-so-good machines, which is a very important demographic, can tell the difference.
--
As a rule of thumb, if your latest release, compressed, is bigger than 600-700MB, you've got a problem.
I often say that for each megabyte you add there's a person less willing to download it.