Starsector 0.97a is out! (02/02/24); New blog post: Simulator Enhancements (03/13/24)
Assuming a windows system, there's a file called "vmparams" in the starsector directory.Editing that with any text editor (notepad will do but notepad++ will be better, wordpad would probably be fine too) and replacing this: "-Xms512m -Xmx512m" with this: "-Xms1024m -Xmx1024m", then save and use the launcher as usual.You could go up to -Xms2048m -Xmx2048m if you have the ram, but in my experience this means the launcher won't start properly because Java fails to allocate all that memory. To fix that, you may need to replace the JRE with a 64 bit version. This basically involves downloading a recent 64bit JRE, and copying it over the one in the starsector/jre folder. If that's too complex, try numbers in between 1024 and 2048 until something works for you.Finally: Loading a save seems to take quite a bit more memory than actually playing the game, presumably because the game doesn't keep -everything- in memory all at the same time, but loading needs to do initial setup on everything at least once.
Hello,During 0.6.2, I used a .batch file to run Star Sector using parameters found online to increase the amount of memory the game could use, preventing crashes where the heap would overflow. But the .bat file no longer works with 0.6.5a, I suppose because certain file names were changed.After testing Darloth's solution, I'll leave it here for others to use. I'd like to add that 1024m should easily be enough to allow the game to run properly, unless a mod you are using as an unfortunate leak of some kind.Quote from: Darloth on November 02, 2014, 11:34:48 PMAssuming a windows system, there's a file called "vmparams" in the starsector directory.Editing that with any text editor (notepad will do but notepad++ will be better, wordpad would probably be fine too) and replacing this: "-Xms512m -Xmx512m" with this: "-Xms1024m -Xmx1024m", then save and use the launcher as usual.You could go up to -Xms2048m -Xmx2048m if you have the ram, but in my experience this means the launcher won't start properly because Java fails to allocate all that memory. To fix that, you may need to replace the JRE with a 64 bit version. This basically involves downloading a recent 64bit JRE, and copying it over the one in the starsector/jre folder. If that's too complex, try numbers in between 1024 and 2048 until something works for you.Finally: Loading a save seems to take quite a bit more memory than actually playing the game, presumably because the game doesn't keep -everything- in memory all at the same time, but loading needs to do initial setup on everything at least once
Assuming a windows system, there's a file called "vmparams" in the starsector directory.Editing that with any text editor (notepad will do but notepad++ will be better, wordpad would probably be fine too) and replacing this: "-Xms512m -Xmx512m" with this: "-Xms1024m -Xmx1024m", then save and use the launcher as usual.You could go up to -Xms2048m -Xmx2048m if you have the ram, but in my experience this means the launcher won't start properly because Java fails to allocate all that memory. To fix that, you may need to replace the JRE with a 64 bit version. This basically involves downloading a recent 64bit JRE, and copying it over the one in the starsector/jre folder. If that's too complex, try numbers in between 1024 and 2048 until something works for you.Finally: Loading a save seems to take quite a bit more memory than actually playing the game, presumably because the game doesn't keep -everything- in memory all at the same time, but loading needs to do initial setup on everything at least once