[SOLVED] How can I change JDK in Preferences/Gradle in MCreator 2020.3 (because CRASH)

Started by AtomiX7_NG34 on Wed, 05/27/2020 - 09:58

Topic category: Help with MCreator software

Hello guys!

Everytime, I load a world with MCreator 2020.3, it crashes.

In 2020.2, I solved that problem, because I changed JDK to JRE in Gradle Settings.

But in 2020.3, this option is gone. :(

My PC is bad and JDK is crashing, please add this option again, so I can test my mod I worked hard for. D:

I did it like this to solve this problem:

Step 1: I change JDK to JRE.

Step 2: I copy tools.jar from JDK to JRE.

Step 3: I can test my mod now.

BTW, SOLVED!

Jump to top

Edited by AtomiX7_NG34 on Tue, 03/16/2021 - 11:59

Or I think it's because of the JRE inside of the JDK, so I'm gonna swap it with my.

Jump to top Permalink

No it doesn't work. It crashes, even when I press "Run Client" Button

Jump to top Permalink

My small crash message when everything is normal:

v36:14.21 [Server thread/DEBUG] [FMLWorldPersistenceHook/WP]: Gathering id map for writing to world save Superflat Test
[m#
] # A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffcbae5d88f, pid=7840, tid=0x0000000000001844
#
# JRE version: OpenJDK Runtime Environment (8.0_252-b09) (build 1.8.0_252-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.252-b09 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ig8icd64.dll+0x54d88f]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Lara\MCreatorWorkspaces\between_worlds\run\hs_err_pid7840.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
AL lib: (EE) alc_cleanup: 1 device not closed
> Task :runClient FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':runClient'.
> Process 'command 'C:\Program Files\Pylo\MCreator20203\jdk\bin\java.exe'' finished with non-zero exit value 1
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/4.9/userguide/command_line_interface.html#sec:c…
BUILD FAILED in 4m 44s
10 actionable tasks: 4 executed, 6 up-to-date
BUILD FAILED
Task completed in 301941 milliseconds

Jump to top Permalink

This is usually due to bad GPU driver.

Google "Minecraft ig8icd64.dll"

Could be your AV too

Jump to top Permalink

I think that's because Intel HD Graphics driver.

Jump to top Permalink

Thanks, you helped me a lot :D

Now I can test my mod.

I just turned on View Bobbing and VSync.

Thank you very much!

Jump to top Permalink

Np :)

Jump to top Permalink

It doesn't work anymore.

I already have the latest version of my GPU driver.

Jump to top Permalink

You need to set vsync for each workspace

You can still set java_home by editing <user home>/.mcreator/preferences too, but do this on own risk as this is unsupported feature.

Jump to top Permalink

"gradle": {
"compileOnSave": true,
"xms": 325,
"xmx": 824,
"offline": false
"java_home": "C:\Program Files\Java\jre1.8.0_241\bin\java.exe"

Like this?

What bin file does MCreator need?

Jump to top Permalink

No, it is now in the hidden section now:

    "notifyForPatches": true
  },
  "hidden": {
    "workspaceLargeIcons": true,
    "fullScreen": false,
...

    "java_home": "<YOUR PATH HERE>"
  }
}

Jump to top Permalink

Oh that makes sense, because when I started MCreator, it disappeared from the gradle section.