Join the render farm
ChunkyCloud is made possible by all the people that contribute their computing power for others to render their scenes on.
Under the hood, scenes get split up and rendered on multiple nodes in parallel and the resulting images are merged back together.
This guide explains how to add a PC or server (called a render node) to ChunkyCloud.
1. Get an API key
In order to add your node, you need an API key. Currently, this process isn't automated, so ping leMaik on the Chunky Discord.
The API key is used to identify users and give us a way to exclude malicious users. In the future, it will also be used to give you credits for rendering that you can then use to create render jobs.
Until this is ready, you can render as much as you want (but please keep it fair).
2. Download the render node software
Once you have an API key, download the latest version from the releases page.
Make sure that you always use the latest version. If there are breaking changes, your node may not be able to connect anymore without being updated.
3. Launch the node
Open a command prompt in the directory that contains the .jar file and run the following command to start the node (change the filename accordingly):
java -Xmx8g -jar cc-rendernode-1.0.0.jar --api-keyAdjust -Xmx to the amount of memory you want to dedicate. In the example, it's 8 GB. Don’t assign too much memory – running out might destabilize your system.
Additional options:
-t: number of render threads (e.g.-t 2uses 2 threads). If omitted, all logical CPU cores are used.--name: give your node a name for the stats page, e.g.--name "leMaik's PC"
The node will create working directories, download Minecraft (for default textures), and connect to ChunkyCloud.
At this point, your node is ready and will be assigned tasks as soon as they arrive. Look back at the command prompt – it might already be rendering!
Frequently Asked Questions
Absolutely! There even is a Docker image you can use:
docker run --name cc-node lemaik/chunkycloud-renderer:latest --api-keyYou can also specify the API key with an environment variable: -e API_KEY=YOUR-API-KEY-HERE