You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2024. It is now read-only.
Ok, first of all it's a good idea to understand the structure of the BlendNet tasks
execution process. If it's too much for you - skip it for now, but return when it's needed.
Basics
On the high level BlendNet contains 3 components:
BlendNet Addon - UI to interact with the user, send workloads to the Manager and receive
the data from the Manager.
BlendNet Manager - controls the Agents and making sure the workloads are processed well.
BlendNet Agent - workhorse which receives the workloads and performing the render itself.
All those components are stored in the addon distributive, so if you download BlendNet - it
already have everything you need to run your own render farm in cloud or using your
resources.
Advanced
This schema shows a big picture of how the BlendNet is working.