-> There are 2 clients... The Windows client contains java, so you open it, and it runs... The other one requires java to be installed, but it should work on Windows, Linux, and Mac as well with java installed... On ubuntu you can install java with this command in terminal: sudo apt-get install openjdk-8-jdk (If you're using my autoconfig script it should take care of everything it needs except the video card driver...)
-> CPUs usually work best with a tile size of 32, while GeForce cards usually work best with a tile size of 256. If you enable both and let the server pick compute method, I recommend setting a tile sise of 128.
-> Rendering usually requires substantial amount of RAM and VRAM. The minimum I recommend is 3-4GB. I've tested a GeForce GT 710 video card with 2GB of VRAM, and it often runs out of memory...
-> ARM CPUs are not supported. Newer AMD video cards are supported older ones may not be. Rendering with more then 1 vido card requires some fiddling, and launching separate instances of the client, just like you have to if you want to render with both CPU and video card simultaneously...
-> On Linux: In order to be able to render with GPU, you have to have the proprietary driver installed for your video card, it doesn't work with the open source driver(nouveau)...
-> On windows: Do I still have to say that you absolutely need the drivers for almost everything?!
-> On mac: I believe you don't need to fiddle with drivers on a mac as it should come with every driver already installed unless it's a hackintosh...
-> You need several GBs of free disk space in the work directory... If you're running 2 or more instances, multiply several GBs with the number of instances you run. The longger it renders, the more space it will use. (For me 2 clients ran out of 17GB in a month...)
-> Same with internet bandwidth... (For multiple machines setting up a proxy is recommended, but that's out of the scope of this guide.)
Set the client as you see on the image using
and a separate empty working directory for each instance.
By default you can only render with CPU OR GPU, not with both, however you can run 2 clients. One for the CPU, and another for your GPU, but you need to specify 2 separate work directories, one for each client, and note that they still use the same config file, so you have to re-configure one of them each time you connect your machine. The next image shows single client with the recommended config.
If you're using linux(debian, or ubuntu), then you're lucky, because I made an auto-configuration script for easy and efficient setup. :D Keep reading!
The easiest way in command line is using my auto-config script, that collects information about the machine, finds the best configuration both for CPU and GPU, launches 1 or 2 instances of the client depending on available RAM, VRAM, CPU cores and disk space. It also check for java, inxi and htop, and offers installation if not found. (And it also has some additional features like built in script and client updating, can easily be made a systemd service with the help of my systemd service generator script to launch automatically at startup, etc. Check the readme file, and --help for more.)
-> Download it, and run it, that should be it. My username and key are by default specified in the code, it will check for requirements, and ask if you want to install them, and it contains a working client. It should work out of the box. You can specify -C option(Uppercase "C" !) to download the latest sheepit client from the sheepit website. (The reason I included a working client is because I've experienced issues twice in 6 month with the latest client. But no need to panic if you've updated it and doesn't work, you can roll back to the previous client by specifying -RC option. And notify me on OSRC or the Blender Discord.)
-> Please note that my autoconfig script is not entirely tested, it should work, but I only have 2 PCs to thinker with both of them being 8+ years old, one of them having a supported nvidia graphics card.
(The sheepit client does communicate with the sheepit server(s), it has to... However the auto-config script does not communicate with anything or anyone! It only uses the information it collects about the machine to configure the client instance(s) properly!)
Alternatively you can download the official Sheepit client and use the following commands to launch the client(s) without the autoconfig script.
java -jar ~/sheepit*.jar -login rpbcacueaiibh -password d5y7FgPYCQjrg9JP0iqqjt5AlCYXkGmiKcgCF0O8 -compute-method CPU -cores 7 -priority 0 -memory 4200 -cache-dir ~/Sheepit
java -jar ~/sheepit*.jar -login rpbcacueaiibh -password d5y7FgPYCQjrg9JP0iqqjt5AlCYXkGmiKcgCF0O8 -compute-method GPU -cores 1 -priority 0 -memory 2000 -cache-dir ~/Sheepit2
Single instance with both CPU and GPU enabled
java -jar ~/sheepit*.jar -login rpbcacueaiibh -password d5y7FgPYCQjrg9JP0iqqjt5AlCYXkGmiKcgCF0O8 -compute-method CPU_GPU -cores 8 -priority 0 -memory 6200 -cache-dir ~/Sheepit
You may have to change the core count, memory, cache directory, and the location of the sheepit client.
Run java -jar ~/sheepit*.jar --help for more information...