- Tue Nov 17, 2009 8:51 pm
#314967
i could need a little help right now...
im working on a big scene, and i would want to cut ram usage by scaling down my textures..
i am using one shared drive across my local network, where all textures are located ( in several locations not in one folder)
now using pack and go, i can get all textures to one directory (and resize them), but when i open the .mxs in the target folder, all paths in studio are still linked to their original locations on my networkdrive.. and not relative to the folder i "packed & go" to.
that is a problem, because even if i define a texture folder when sending jobs via network, maxwell will use the orgiginal texture paths, as long as the network drive is present and the textures still there...
any chance to force using "only" the given alternate folder?
thanks,
Daniel
im working on a big scene, and i would want to cut ram usage by scaling down my textures..
i am using one shared drive across my local network, where all textures are located ( in several locations not in one folder)
now using pack and go, i can get all textures to one directory (and resize them), but when i open the .mxs in the target folder, all paths in studio are still linked to their original locations on my networkdrive.. and not relative to the folder i "packed & go" to.
that is a problem, because even if i define a texture folder when sending jobs via network, maxwell will use the orgiginal texture paths, as long as the network drive is present and the textures still there...
any chance to force using "only" the given alternate folder?
thanks,
Daniel
workstation: EVGA SR-2 / dual x5650@3.5Ghz / quadro 4000