This means you'll actually be able to see which of them are alive and able to be used and which are offline (or just not posting cause they're not logged in). Using this allows the vm's / containers to post to your cloud account on our servers when they are alive. -ct - authorisation token of your Crowdrender cloud account.This can be literally anything, but its important if you're using containerisation or vms on your own hardware since if you do, chances are the hardware id of those vm's containers could be the same, which totally prevents you from connecting to more than on of them at once, defeating the purpose of using our software. -ak - called the access key, if you setup multiple vm's on your own servers, best give them each a unique access key.-p false - if you're using a virtual machine from a cloud provider, you may not want to permanently store it in your crowdrender account as if you do, each time you use a vm from a cloud provider, you'll get a different vm and they'll start to pile up in your account.Now it should show the IP address of your server and you should be able to connect to the server via any client running in the same network additional CLI arguments Start server for Crowdrender = 0.1.7 / Blender = 0.1.7 / Blender >= 2.80 $ blender -noaudio -b -python ~/.config/blender/2.80/scripts/addons/crowdrender/src/py_3_7/serv_int_start.py -t "server_int_proc"įor Crowdrender >= 0.3.0 / Blender >= 2.80 $ blender -noaudio -b -python ~/.config/blender/2.80/scripts/addons/crowdrender/src/cr/serv_int_start.py -t "server_int_proc" > _install(overwrite=True,filepath='/path/to/addon.zip') > .addon_enable(module='crowdrender')įor blender >= 2.80 (thanks to $ blender -b -python-console > .addon_install(overwrite=True, filepath="/path/to/folder/addon.zip") Install and activate addon for blender > import bpy optional: GPU drivers for GPU-rendering.
Blender v2.79 or v2.80 - v2.93 (from package manager or ).GUIDE: How To create a headless blender renderserver with CrowdRender addon Requirements
0 kommentar(er)
