I tried this version for a bit, and smuggling seems a lot less profitable. Make sure you save the vmparams file, close you notepad window, and then run Starsector. In vmparams, there is a segment that says something like -Xms1024m -Xmx1024m. In the same folder as the two jre files, there is a file called vmparams. jre7, which you just copied here, and just named jre. Now, there should be two folders called jre* in this directory. Navigate to your Softworks/Starsector/ directory. Navigate to the java7 directory (probably something like C:\Program Files\Java) and copy the folder named jre7.ħ.
#STARSECTOR PLUS INSTALL#
Install and unpack the java you just installed.Ħ. Assuming you have an out of memory error, go here and download the JRE 64bit that is appropriate for your machine.ĥ. If not, please spoiler post the contents of your. If there's any form of out of memory error, then the problem is easily fixable, and you should proceed to step four. Open starsector.log and scroll to the bottom.ģ. Go to Fractal Softworks/Starsector/starsector-coreĢ. Okay, first things first, let's make sure we're diagnosing the right problem.ġ. Can't remember if the dev comes by here occasionally or not, but they're almost certainly your best bet for figuring out what to do. lastly, asking on the main starsector forum is probably a good idea, heh. Pretty sure it would tell you (more or less) what the program was trying to do before erroring out, which can help narrow down exactly what's going wrong and what potential fixes are. log file inside that folder you might look at for more information. bat inside the starsector-core folder instead of the launcher/.exe, maybe.Į2: There's also a.
#STARSECTOR PLUS CODE#
Other than checking to see what the specific code of the error points is and giving a go at fixing it from that end, a clean install with the latest version is probably your best bet.Į: Could also try running from the.
#STARSECTOR PLUS FULL#
Try a full delete/uninstall and reinstall? Quick pokearound suggests the problem is caused by something in the program's code, rather than something on your end (such as it were), which would imply something screwy happened to your instance of the program - corruption, unintentional file overwrite or lack of intended one, stuff like that.
0 kommentar(er)
