i have a question about how the team render server works with assets and its need to recreate assets in the repository instead of reference them from their original locations. Im doing a large project and want to move away from my previous method of using the render queue in C4D itself to sent stuff to my nodes. Mainly so i can keep working on that machine and if it crashes i wont risk looking a long blacklist of cued scenes (C4D only see,ms to remember queued items after the machine GUI has been closed and reopened). So I installed the team render server on an older slower machine which isnt being used, hoping this would basically be able to do the job of the render queue. Previously the nodes were pulling all the assets off of a NAS Drive and saving them as needed into their local repositories and that was working fine. However team render server is needing me to collect all the assets in its own repository to then have the nodes copy them again. Is this the way it has to work? as it just added another stage of copying and storing all the assets into the process which is going to be problematic down the line as im working with alot of assets, and many heavy textures? with this way theyre all duplicated 3 times in the render process (original location, TRS repository and TRC repository)
ive tried setting deadline up on the farm but had alot of trouble shooting issues setting up the acesss to the repository there. are there any other good render managing solutions people would recommend.
Im running R19 with Redshift, render lined nodes are all windows 7, team render server machine is a mac pro running os x.