Damocles
New member
I was mostly asking if you run the 64 bit or 32 bit version of Java.
The 32 bit might have problems increasing the heap space large enough.
With 64 bit, java -version will state something like "64-bit server VM"
With 32 bit build it will state something like win-32
Usually the java being used is the one found by its installation folder in your path environment variable.
echo %PATH%
will show a list of the system folders. You might point to a 32 bit installation here.
I have a similar behavior when using a 32 bit version.
But on this with the parameters
java -Xmx1400m -jar nitrogen.jar
(reserving 1.4 GB heap)
I could at least build a 4k map.
Now, I can only recommend you to open the console, "cd" to your installation directory, and run the program directly from the console, using the -Xmx1400m heap-extension parameter.
The 32 bit might have problems increasing the heap space large enough.
With 64 bit, java -version will state something like "64-bit server VM"
With 32 bit build it will state something like win-32
Usually the java being used is the one found by its installation folder in your path environment variable.
echo %PATH%
will show a list of the system folders. You might point to a 32 bit installation here.
I have a similar behavior when using a 32 bit version.
But on this with the parameters
java -Xmx1400m -jar nitrogen.jar
(reserving 1.4 GB heap)
I could at least build a 4k map.
Now, I can only recommend you to open the console, "cd" to your installation directory, and run the program directly from the console, using the -Xmx1400m heap-extension parameter.
Last edited by a moderator: