How can we help?

 

Or browse articles in the categories below:

Found 1 answers matching your query:

 

Using Team Render Server

Team Render Server has significant advantages in terms of controlling render jobs on large render farms, however, using INSYDIUM Fused with TRS can be problematic.
With TRS, you 'upload' assets to the server which then distributes them to the clients rendering that job. You do this by saving the project with all its assets (Cinema 4D File menu->Save Project with Assets...) which collects all the assets into one single folder. In the X-Particles Cache object, if you turn on 'Cache Files as Assets', the cache files will be saved to the folder 'Save Project with Assets' created.

However, TRS will recognize only certain file types as assets - e.g. Cinema 4D scene files, various image formats, etc. and it does NOT recognize X-Particles cache files. This means that TRS will not distribute the cache files to render clients.

To use TRS with a cached X-Particles scene, you need to set up the scene in the same way that you would if using Team Render. You must choose the cache type and a location for the cached files. You can turn on 'Cache Files as Assets', but then the files will be saved to the project folder and you will need to share that folder so it is visible to the client machines.

If you are using internal caching, once the scene is cached and saved, you simply upload it to the server in the web interface and click 'Start'.

If you are using external caching, you will have to save the cache files to a shared folder on your network. If you enable 'Cache Files as Assets' in the Cache object, the cache files will be stored in a subfolder of the project folder that Cinema created when you save the project with assets in the Cinema 4D File menu, and you need to share that project folder over the network.

Instead of the above, we recommend that you create a shared folder that will be used for any render job and save the cache files into that. Do not enable 'Cache Files as Assets' in that case, and there is no need to upload the cache files to the server. The workflow using TRS then becomes very similar to using Team Render - create the share, save the cache files to it, and point the folder field in the Cache object to the shared folder where the cache files are located. And of course, adjust the 'Alt Folder' field as well if using mixed networks.