welcome to this QuickStart tutorial for
v-ray for rhino and this video will show
you how to use various warm a
distributed rendering system that allows
you to render on multiple machines at
once using a simple web interface swarm
may be installed alongside v-ray for
rhino but also may be installed on its
own by launching the v-ray installer and
selecting to install just very swarm you
do not need to install rhino or v-ray
for rhino on a machine that you just
want to use as a render node machine
just install swarm likewise you don't
need to install swarm if you do not want
the machine to be a render node you can
just install rhino and v-ray for rhino
without swarm and still be able to
render on render nodes that have swarm
if you already have installed v-ray for
rhino with its license you won't need to
install the license server on machines
that do not have the way for Rhino
already installed you will need to
install the license server and set that
up with your proper license for that
machine to be able to render in this
warm lastly you can install the license
server or each machine or have the
machines look at a network machine for
their license the local machine always
uses one render node licensed during
rendering a random node license is
required for each additional render
known machine participating in the job
now I'm gonna go ahead and install just
swarm you gladly don't need to change
any of these settings just make sure to
uninstall any previous installations if
you have any and make sure that our
firewall exceptions is checked on
we'll leave the address and port options
as this unless you're using a license
server so this is what input that
server's IP
quick install now and that's it you want
to install swarm on all machines you
intend to distribute renders - now that
we're installed let's get into the
configuration for the interface of the
render node machine open a web browser
here I'm using Microsoft edge to access
the interface you need to type in the
browser localhost - 4 - 6 7 where - 4 -
6 7 is the default port used in the
Installer to set a different
communication port during installation
turn off outer discovery and this will
display the relevant option as a side
note you can remotely access warm
installed on a different machine by
typing in that machine's IP address and
the port number instead of using
localhost
now that we are in localhost we are
greeted by the network page and we can
see the name of the current machine up
here and other machines in the swarm in
the list below in the right corner you
can enable or disable the node for swarm
rendering
click in the upper left axis the
different pages for the interface switch
to the lock page to see any messages
from this machine's render job progress
which is good for troubleshooting if
needed
this icon access display options for the
look
and the resource usage page you can see
how machines in the swarm are doing as
far as CPU usage GPU usage for the
current machine it's memory network and
storage now let's dive into
configuration making any changes to
configuration here requires that the
node be disabled for rendering before
those changes take effect so go ahead
and disable the render node and the
options become available
tags allow you to tag this node with a
descriptor that defines something about
the machine like if this is one of the
few machines that has a powerful GPU or
let's say a machine is not a workstation
but a note on a render farm all of these
when they're known machines come with a
default tag
so let's stack this machine as render
node and click Add and then click Save
now you can rename oh the node now let's
click on the network page again this
shows all the available for machines on
the network displaying their machine
names status IP address and their tags
right here along with some important
information like the fare a version here
we confirm the addition of the tag that
we added to this machine number 52
selecting a machine allows you to enable
or disable it easily
coppy configuration will duplicate the
settings from your current machine which
is number 52 to the ones selected in the
list you can select multiple machines
using the shift or the control key I'll
go ahead and copy my configuration to 50
and 51
but our first need to disable them both
at once
and then copy the configuration over to
them before renaming them both
now if you select one render node you
can access the swarm interface by
clicking where it gives the IP and URL
here in the interface this opens a new
tab putting us into that machine so
managing several render nodes can be
much easier than going to each physical
machine now let's see swarm in use on a
Rhino project here we are already in the
scene file code swarm start which you
can download from the tutorial page
linked below once you have the project
loaded open the asset editor from the
v-ray toolbar click the Settings tab and
click on swarm in a box want to see some
more settings appear once you start
rendering you notice the current usage
bar gives you feedback on the swarm
usage the go slider below determines how
much of the swarm to throw onto the
rendering which is defined by a
percentage of the available machines
tags is where the render node tag that
we created earlier comes in handy you
can click on the text to add or remove
them so that your swarm render
distributes only to the machines with
this tag when no tags are chosen or
available render no machines visible and
swarm manager will be used
click on the text field here to add tags
as needed by typing them in or selecting
from the drop down menu go ahead and add
the render node tag by enabling the cap
CPU utilization button you cap the CPU
usage of the local machine to a single
core let's leave it all for this
tutorial and the local machine will
render at full capacity all the render
settings are taken care of in this scene
for the final image and as you can see
progressive is disabled which is
typically better when you want a swarm
render as distributing the render is
more optimized for using buckets over
progressive and since we already have
swarm enabled go ahead and start a
render after a moment the render begins
and you can notice the usage goes up a
33 percent once it got passed 25 percent
it stops adding render nodes to the
swarm but as its rendering you can
increase the cost later to dynamically
adjust and add more resources to the
render and of course you can also turn
that down as well and the render nodes
will drop off this warm now I'll add a
couple more texts to swarm pool and more
nodes will populate the render
dynamically
zoom into the render and you can see
each render note name in the individual
buckets of the render click this icon
and it opens the swarm interface of the
currently selected master node you can
see some more details of whoops were
missing on the render
for example our remove resources from
the render and you can see the interface
updates as a machine drops off okay
let's get this frame rendered with all
our nodes and here we can see the image
being finished up with distributed
rendering using v-ray swarm saving a lot
of time over rendering on just my one
local machine thank you for joining us
for this quick start video on swarm for
v-ray for rhino