Chunky can be run headlessly to render scenes without using the GUI. This is useful when rendering on a server, for example, or when automating or scripting renders.
When using Chunky from the command line, you should know what the Chunky Launcher does. The Launcher is responsible for launching Chunky itself by starting a new Java process. It also verifies the file size and the MD5 checksum of the Chunky version that is being attempted to run
Command line arguments that begin with one hyphen, such as
-snapshot, are sent to Chunky, while arguments that begin with two hyphens, such as
--update, are sent to the Launcher.
Any JVM (Java Virtual Machine) arguments used when starting the Chunky Launcher apply to the Launcher and not to the Chunky process itself. Any JVM options that must be added to Chunky itself must be specified in the chunky-launcher.json file, under the
javaOptions variable. The chunky-launcher.json file is located in the root of the Chunky settings directory.
To view the Java arguments used to start Chunky, add the
--verbose argument to the Chunky Launcher startup command. The launcher will then print the command that it used to start Chunky.
Custom Settings Directory¶
A custom Chunky settings directory can be specified by adding the
-Dchunky.home Java option to the Chunky Launcher startup command. The launcher will also pass the option to Chunky itself.
Changing the settings directory can be useful if you must run multiple instances of Chunky on the same computer or if you need more control over the locations in which the scenes and settings are stored.
Below is an example on specifying a custom settings directory.
$ mkdir "~/chunky" $ java -Dchunky.home="~/chunky" -jar ChunkyLauncher.jar --update
Note that the
-Dchunky.home argument must be added before
-jar. If you are using Bash, it can be convenient to make an alias for the java command above. An example of this is below.
CHUNKY_HOME=~/chunky alias chunky java -Dchunky.home="$CHUNKY_HOME" -jar ChunkyLauncher.jar
The lines above could also be added to your
Setting things up¶
It may be necessary to perform some setup before rendering headlessly. The following steps should be done before you can render headlessly, and some may need to be repeated mater to update Chunky.
- Download the Chunky Launcher onto your computer. The latest version can be obtained by using the command:
- Download the latest version of Chunky by using the command:
java -jar ChunkyLauncher.jar --update
- Download a Minecraft version.jar for block textures, such as version 1.19.2, by using the command:
java -jar ChunkyLauncher.jar -download-mc 1.19.2
Rendering a scene via the command line is simple, assuming that the scene parameters have been set up and the scene files have been copied to the
The simplest way to render a scene is to use the command:
chunky -render SceneName
SceneName with the name of the scene to be rendered.
To print a list of available scenes, use the command
Chunky will continue to render until it reaches the target SPP specified in the scene.json file. Chunky can be stopped prematurely by using
[Ctrl]+[C], but any render progress since the scene was last saved will not be saved. Render progress is normally saved after intervals determined by the
dumpFrequency scene.json setting.
Snapshots of a scene with saved render progress can be created by using the command:
chunky -snapshot SceneName snapshot.png
SceneName with the name of the scene of which the snapshot should be created. The
snapshot.png is the filename of the PNG file to be created.
-help argument to the startup command to view a list of all available command line options. Currently, the options listed below are available.
-render <SCENE>: Render in headless mode. You may also need to add the
-fflag to force a scene to render.
-reload-chunks: Reload the selected chunks before rendering the scene (used in conjunction with
-texture <FILE>: Load the specified texture pack.
-snapshot <SCENE> <PNG>- create a snapshot from a scene.
-scene-dir <DIR>: Specify scene directory.
-threads <NUM>: Change number of render threads.
-tile-width <NUM>: Modifies the frame subdivision size per worker threads.
-spp-per-pass <NUM>: Modifies the samples to be completed per tile per pass.
-target <NUM>: Set the SPP target for the current headless render.
-set <NAME> <VALUE>: Modify a Chunky setting value.
-set <NAME> <VALUE> <SCENE>: Modify a scene setting.
-reset <NAME>: Reset a Chunky setting to its default value.
-reset <NAME> <SCENE>: Reset a scene setting to its default value.
-download-mc <VERSION>: Download a particular version of Minecraft.
-list-scenes: List available scenes in the scene directory.
-merge-dump <SCENE> <PATH>: Merge a render
.dumpfile into the specified scene combining the total SPP.1
-help: Print the command-line help and Copyright notice.
The launcher accepts these commands:
--update: Download the latest version of Chunky.
--setup: Interactive command-line Chunky setup.
--nolauncher: Should not be used in headless mode.
--launcher: Force the launcher UI to be shown.
--version: Display the launcher version.
--verbose: Enable verbose logging.
The value of the
Target SPPshould be greater than the sum of the current SPP of the currently-loaded scene and the current SPP of the render dump to be merged to prevent unexpected behavior. ↩