Establish LightNet Cluster

When the other machines are found, your LightNet Management window will most likely look similar to this.
In order to Establish cluster there are just a few steps that you need to do:
Invite the machines into Primary's cluster
Assign correct roles to them
Establish the cluster
Inviting a machine into a cluster

The quickest way to invite a machine into Primary's cluster is simply to drag it into it. This will also automatically assign it a Secondary role.
Assigning a role to every machine

Use this dropdown to assign a role to a particular machine.
Establishing a Cluster

The quickest way to establish a cluster is to simply click on the Establish Cluster button. What this will do in the background is:
Save the project file on the Primary
Establish a LightNet connection with all the machines in the cluster
Check if all the machines have the same version of LightAct.
Check if Primary has access to the LightNetProjects folders on all the machines
Transfer project file to all the machines
Open the project file on all the machines
Establish LightSync
Check if Project files match on all the machines
If any of the above steps fails, your cluster won't work as intended.
LightNet connection

When you have a server established, you'll see these green circular lights blinking every now and then. These lights blink whenever there is LightNet message (real-time updates across the cluster).

If you move drag an object, for example, these lights will blink much faster.

What also affect the frequency of LightNet messages are Real-time edit updates and Heartbeat frequency dropdowns in Project settings window in LightNet tab.
Manually managing LightNet connection

It is possible to manually manage LightNet connection with these 2 buttons:
Access check: checks if Primary has write access to the LightNetProjects folder on this machine
Connect/Disconnect: manages LightNet connection with this machine.
If LightNet connection breaks for any reason, it might be worthwhile to analyse why it happened in the first place.
Multi-user
LightAct allows users to modify project on Primary, all Secondaries and all Editor machines. Everything that you change on any of these machines should be propagated first to the Primary and then to the entire Cluster in real-time.
Even though we don't prohibit changes made in Secondary servers, we recommend the users use only Primary and Editor machines.
This is also the only workflow that we officially support.
Last updated
Was this helpful?