Tweet
Afternoon.
Lets say I have a set of material libraries on Server A. All textures paths within these materials are linked to a folder - also on Server A.
I want to transfer these libraries to another server, Server B - and utilize them on another computer on the network that is also on Server B.
Seems pretty straightforward.
Problem. When loading libraries and materials into max on Server B, texture paths are pointing towards Server A. Long load times ensue (4k,8k textures) per material and there are around 50.
Anyone have an idea on the best approach here? I thought of copying all textures from Server A to Server B and re-linking them, but I can only do this once the material is actually loaded in to max.
Lets say I have a set of material libraries on Server A. All textures paths within these materials are linked to a folder - also on Server A.
I want to transfer these libraries to another server, Server B - and utilize them on another computer on the network that is also on Server B.
Seems pretty straightforward.
Problem. When loading libraries and materials into max on Server B, texture paths are pointing towards Server A. Long load times ensue (4k,8k textures) per material and there are around 50.
Anyone have an idea on the best approach here? I thought of copying all textures from Server A to Server B and re-linking them, but I can only do this once the material is actually loaded in to max.
