Transfer and Open Project

All user actions done on the Primary should be propagated automatically to all the Secondary machines. However, there are 2 main reasons why you still need to manually transfer project and asset files across the cluster:

  • assets can, at the moment, be transferred only by clicking on Transfer button. So whenever you import a new asset on Primary, you will eventually need to copy it to the desired Secondary machines.

  • All changes done on Primary are automatically propagated across all of the Secondary machines. If, for various reasons, a Secondary cannot execute a particular change, it will notify the Primary. In this case, it is advisable to save, transfer, and re-open the project on all Secondary machines.

If you have not saved your project yet, you will need to do so. Now is also a good time to take a look at the Asset Distribution chapter. Once you have done the steps described in that chapter, you can proceed here.

In LightNet window of your Primary machine, click on Transfer.

Good to know: It is always best practice to save the project before transferring it, to ensure that all recent changes will be included in the project file which is transferred to the Secondary machines.

In the Project transfer pop-up window, select Transfer. Once the files have finished transferring, you can click Close.

If you encounter any issues here, please make sure all LightNet Prerequisites are set up correctly. Additional clues are also available in the Logs window.

Click Open on all to open the project on all machines in the cluster.

Good to know: If the text under the Project column is yellow, it means there is some kind of a mismatch between the projects. Click Refresh data to see the updated changes. If the text stays yellow after refreshing the data, save, transfer, and open the project again.

Last updated