Setting up Minecraft Forge MDK doesn't work on 1.7.7

Submitted by HPositive on Sat, 02/03/2018 - 18:00
Issue description

I just downloaded MCreator 1.7.7

Everytime I try to download MCreator I always have some sort of issue but usually I can fix it with some work.  This problem however seems impossible to fix.  I am trying to install MCreator 1.7.7 and as it is 'Setting up Minecraft Forge MDK' and is downloading 'decompileMc' it will stop and tell me I need to allocate more RAM Java JMV that is not the problem, i've done that before.  The program does not let me access preferences since MCreator hadn't fully installed yet, even when they error screen comes up I try to click on preferences and since the error screen is up I can't and when I try to close the error screen to access the preferences it forces me to close MCreator.  The error message even tells me to go to Preferences!  The error code is JAVA_JVM_HEAP_SPACE [-14].  Please Help.

EDIT by developers:

From MCreator 1.7.8 on, there is not more such file as mcreator.properties. Now, you need to do the following. Go to your user home folder of the system you use. Here find the folder .mcreator. Go in it. You should find a file called preferences. If there is no such file, create one and give it no extension - the whole file name should be preferences.

If there is already a file, open it and look for the parameters "xms": and "xmx": and set them to the appropriate values. If there is no file, create one with the following contents:

{"gradle":{"xms":1024,"xmx":2048,"offline":false}}

Set the xms and xmx parameters to the desired values, but keep in mind that setting too high value may also cause issues on 32 bit systems.

Attachment Size
5657687.PNG69.2 KB 69.2 KB
75656745745.PNG67.39 KB 67.39 KB

Issue comments

Submitted by Klemen on Sun, 02/04/2018 - 11:38

You can create preferences.conf file in the user directory of MCreator and write:

xms=1024
xmx=2048

After you set this, run the setup again.

Please also note that we do not recommend using 32-bit version and that we will most likely drop support for 32-bit computers in the future as this technology is really obsolete nowadays.

Check System requirements page for more details.

May I ask you how much RAM do you usually allocate in order to make it work?

To be honest I am embarrassed to say that I don't know.  The last time I had to allocate RAM was a very early version of MCreator, ever since it has worked without need to allocate anymore.  Also after making this post I realized I was download the 32-Bit version, my PC runs on 64-Bit.  I don't know if that makes a difference with the RAM.

This makes a big difference and is also clearly stated on the download page. Please install 64-bit version which will work.

Submitted by Klemen on Mon, 04/09/2018 - 18:40

From MCreator 1.7.8 on, there is not more such file. Now, you need to do the following. Go to your user home folder of the system you use. Here find the folder .mcreator. Go in it. You should find a file called preferences. If there is no such file, create one and give it no extension - the whole file name should be preferences.

If there is already a file, open it and look for the parameters "xms": and "xmx": and set them to the appropriate values. If there is no file, create one with the following contents:

{"gradle":{"xms":1024,"xmx":2048,"offline":false}}

Set the xms and xmx parameters to the desired values, but keep in mind that setting too high value may also cause issues on 32 bit systems.

Submitted by Klemen on Sat, 07/21/2018 - 11:03

I have reopened this ticket as if one gets this error at the time of MCreator performing initial setup, preferences can't be edited from the UI. We will add an option to edit RAM settings even if MCreator is not set-up yet, until then, this ticket will be open.

Submitted by Klemen on Sat, 07/21/2018 - 20:22

From MCreator 1.8.0 on, users will be able to edit the Preferences at the time of setup to avoid such issues in the future. Closing as this feature will be added in next release.

Submitted by TDP on Fri, 10/19/2018 - 16:42

i'm on 1.8.0 and i have similar problem plz help me

Submitted by Klemen on Fri, 10/19/2018 - 19:44

The solution is on the top. You need to increase the RAM.