Skip to content

Troubleshooting Chunky


This page lists some common problems and their solutions.


Chunky / Chunky Launcher opens as a blank window on Windows

This problem is caused by a problem with the JavaFX hardware renderer for Windows. The only known solution to the problem is to add -Dprism.order=sw to the startup command before -jar. The startup command then becomes of the form: java -Dprism.order=sw -jar ChunkyLauncher.jar --launcher. The -Dprism.order=sw argument must also be added to the Java options input field in the Chunky Launcher.

Double-clicking ChunkyLauncher.jar doesn't work

This is a common problem on Windows wherein JAR files are not properly associated with Java. Solutions to the problem include reinstalling Java, using an application such as Jarfix, or starting the Chunky Launcher via the command line or via a batch script, which can be double-clicked to start Chunky. Instructions to create one are located here.

Exception in thread "main" java.lang.NoClassDefFoundError: javafx/stage/Stage

This problem is caused by the Chunky Launcher being unable to detect OpenJFX on the computer, which happens when JavaFX is not bundled with the JRE used to start the Chunky Launcher and either OpenJFX is not installed, or OpenJFX is neither installed to a detectable location nor added to the startup command manually.

The solution to the problem is to either install OpenJFX to an automatically-detectable location or to add it to the startup command for the Chunky Launcher manually. The solution is covered here.

Chunky crashes if Memory limit is set above 2 GB, despite more than 2 GB of RAM being present in the computer

This problem is caused by the usage of a 32-bit JRE to launch Chunky. The solution to the problem is to use a 64-bit JRE to launch Chunky. The simplest way to do this is to uninstall the 32-bit JRE and then install a 64-bit JRE according to the instructions located in the Installing Chunky article. Set the path to the 64-bit JRE using the Java Runtime control in the Chunky Launcher.

Figure 2.2.1: 32-bit JRE memory limit error

The map view displays an array of red X's when zoomed in and an ocean biome when zoomed out.

This problem is caused by a world with unsupported chunks being loaded. A world from a Minecraft that is not supported by the version of Chunky that is being used can cause this problem. A potential solution is to load the world using a newer version of Chunky, such as Stable Snapshot or Snapshot, which might have support for that world version. For a list of what world versions are supported by Chunky, please read the Minecraft Compatibility article.

Figure 2.2.2: Unsupported chunks in the `Map` tab

Blocks rendered in Chunky use incorrect textures or render as black with a red X

This problem is caused by Chunky being unable to automatically detect and load a Minecraft version.jar for block textures, and, thus, reverting to its internal textures. Solutions to this problem include updating the path to your Minecraft installation by using the Minecraft directory control in the Chunky Launcher, and manually loading as a resource pack a Minecraft version.jar or a resource pack that contains the missing textures.

I try to create a new scene but it is empty

This problem could be caused by either no chunks in the Map tab being selected before New scene from selection or Load selected chunks is used or all blocks in the selected chunks having a Y-coordinate that is beyond the range specified by the Y min clip and Y max clip controls in the Scene tab. If the cause of the problem were the former, then the solution to the problem is to select chunks in the Map tab before using either New scene from selection or Load selected chunks. If the cause of the problem were the latter, then the solution to the problem is to set the Y min clip and Y max clip controls in the Scene tab to the minimum and maximum Y-coordinates of the blocks to be loaded, respectively, and then clicking Reload chunks.

Failed to build render control tabs. java.lang.NoSuchMethodError: javafx.scene.control.ChoiceBox.setOnAction(Ljavafx/event/EventHandler;)V

This problem is caused by the usage of an outdated JRE to launch Chunky. The solution to the problem is to use at least Java 8u60 or newer to launch Chunky; however, Java 17 with OpenJFX is recommended. Installation instructions for Chunky are located in the Installing Chunky article.

Error initializing QuantumRenderer: no suitable pipeline found

This problem is often caused by a mismatch between the architectures of Java and OpenJFX. In that case, the solution to the problem is to use Java and OpenJFX with matching architectures. Another potential cause of the problem is that the module path specified in the startup command does not point to a valid OpenJFX SDK. In that case, the solution to the problem is to download and use an OpenJFX SDK, as stated in the Installing Chunky article. On Linux, a potential cause of the problem is GTK2 being missing from the system. In that case, the solution to the problem is to install GTK2. Another potential solution is to add -Dprism.order=sw to the startup command before -jar. The startup command then becomes of the form: java -Dprism.order=sw -jar ChunkyLauncher.jar --launcher. The -Dprism.order=sw argument should also be added to the Java options input field in the Chunky Launcher.

To view a list of valid pipelines, add -Dprism.verbose=true to the startup command before -jar. The startup command then becomes of the form: java -Dprism.verbose=true -jar ChunkyLauncher.jar The terminal will display a list of valid pipelines with the text, "Prism pipeline init order:". The -Dprism.verbose=true can also be added to the Java options input field in the Chunky Launcher. Then enable the Debug console, and then click Launch. The debug console will display a list of valid pipelines with the text, "Prism pipeline init order:".

java.lang.NullPointerException: Cannot invoke "com.sun.prism.RTTexture.
createGraphics()" because "<local9>" is null

This problem is often caused by the render canvas size being increased beyond the maximum texture size supported by JavaFX, the GPU, or the GPU driver. A potential solution to the problem is to add -Dprism.order=sw to the Java options input field in the Chunky Launcher.

To determine the maximum texture size supported by JavaFX, the GPU, or the GPU driver, add -Dprism.verbose=true to the Java options input field, enable the Debug console, and then click Launch. The debug console will display the maximum supported texture size with the text, "Maximum supported texture size:". Note that the GUI is also factored into the texture size, so the actual maximum canvas size is also dependent on the GUI resolution.

Rare bugs

This section documents rarer problems that are typically caused not by Chunky itself, but rather by other problems on your system. Due to the rarity of these problems, few solutions to them are known.

Text garbled / broken

This problem is often caused by broken fonts on your system, and results in what is shown in Figure 2.2.3. The most likely solution to the problem is to reinstall the Segoe UI font. Other potential solutions include updating the GPU drivers, setting Java to use the GPU through the GPU configuration utility, and disabling Cleartype, which makes text look ugly, and is not recommended.

Figure 2.2.3: Corrupted text in Chunky

Problematic frame...

Problematic frame:
v  ~StubRoutines::SafeFetchN

This problem is caused by a bug in Java, which was fixed in Java 17.0.2. The solution is to use a newer JRE, such as Java 17.0.2 or newer.

Module jrt.fs conflict

The following error, java.lang.LayerInstantiationException: Package jdk.internal.jimage in both module java.base and module jrt.fs, is usually caused when the lib folder of OpenJFX is merged into the lib folder of Java. In that case, the solution to the problem is to install Java 17 and OpenJFX properly, according to the instructions located in the Installing Chunky article. If that is not the case, then the solution is to delete jrt-fs.jar from the lib folder of OpenJFX.