I hope somebody can tell me what we do wrong.
We are trying to migrate from Blender to Cinema 4d at the company and we are hitting a wall when it comes to textures:
Cinema does seem to have some basic problems with textures linking on our network.
Even if the path name is right when we look at it through the Asset Inspector, Cinema shows a red cross. Relinking doesn’t work We tried absolute and relative path names but for both ways cinema doesn’t recognize the file or it does for the active session but after a restart it shows up black again.
Through testing we found some strange solutions:
- duplicate the texture folder and using the “new” textures works
- even duplicating just the texture and using this copy works
- copying to a local drive works
Both network “solutions” still seem to break randomly
But working completly locally doesn’t make sense to us. All of our Artist would need to have a local copy of our big! product database and keeping that synchronized with all the other artist. Thats what a network drive ist for, right?
Can somebody point us the way forward?
One of our artist suggested that the Server is messing with the metadata while creating a backups and this keeps breaking the linking? Sounds a bit far-fetched to me. I mean the texture file is working fine in every other program even after a backup.