Currently we have everything on our network drives. Textures, models, etc.This is causing a bottleneck in our scenes. Long scene asset/texture loading times, long render start times. It's god awful.
I'd like to convince our IT sys admin to move our assets to a drive on our workstations, and have these local folders sync to our network drives as a backup. So if I alter a file/folder on my workstation drive it will reflect this change on the network drive. Ultimately I would like everything local to keep things zippy when we are testing lighting and adding our assets, then we can submit final renders to the farm with 'transfer missing assets' option in DR settings. But we need to have the insurance of a backup on the server in case the workstation drives explode.
How do you all manage your assets paths? Whilst I imagine the above would be possible on an IT footing, I wonder how such a setup would affect other users opening the same file? Given it's using a local path?
Cheers
I'd like to convince our IT sys admin to move our assets to a drive on our workstations, and have these local folders sync to our network drives as a backup. So if I alter a file/folder on my workstation drive it will reflect this change on the network drive. Ultimately I would like everything local to keep things zippy when we are testing lighting and adding our assets, then we can submit final renders to the farm with 'transfer missing assets' option in DR settings. But we need to have the insurance of a backup on the server in case the workstation drives explode.
How do you all manage your assets paths? Whilst I imagine the above would be possible on an IT footing, I wonder how such a setup would affect other users opening the same file? Given it's using a local path?
Cheers
Comment