Before rendering make sure that all of your computers involved in the job (whether it's a MANAGER or a WORKER) have been set up to not automatically hibernate. Also make sure that the network remains open during the rendering process and that the rendering manager and worker are not terminated.

You can see the rendered output in the folder where the blend file is stored. Be careful to give read and write permissions to this folder on all computers before rendering!

First of all, please make sure that the server ip address and port in config.json under the worker folder are filled in correctly (manager can see the relevant information), and then please make sure that both manager and worker have network privileges, you can check your firewall to make sure they are not blocked!

Manager and worker need network access only for transferring data content between each other, generally for LAN intranet, and will not upload any of your information to any other server. Neither manager nor worker has the ability to read other irrelevant files.

First of all make sure you have a shared read/write folder with the blend files you need to render, after the rendering is done it will automatically check for missing tiles or missing frames and re-render until this task is done!

The worker is just a command line program that takes up less than 10MB of memory when not rendering and does not consume CPU/GPU resources. When it receives a render job, it will call blender to consume the computer's performance.

We currently only support the built-in EEVEE Next and Cycles rendering engines, if you have other engine adaptations, feel free to ask us!

Yes, we're all for it.