- Wed Jul 06, 2005 10:26 pm
#43642
Relative Paths for Textures
The issue of absolute paths for all texture maps existed prior to the CIRI (Cinemaxwell Issue Report Index) but it seems to have been addressed in Cinemaxwell 0.6.
Basically you do not have to hard path your texture paths. Just let Cinema 4D use your paths from your preferences and it should work with just the normal file name of "Filename.ext" for those files that reside in those directories. All others that are outside those paths will trigger the prompt from Cinema 4D that will ask if you want to move your textures into your the directory that your scene resides in.
At the moment, this is something that a lot of people have wanted and it looks like it has been addressed by Next Limit.
See following reference for more information.
http://www.maxwellrender.com/forum/view ... 3640#43640
The issue of absolute paths for all texture maps existed prior to the CIRI (Cinemaxwell Issue Report Index) but it seems to have been addressed in Cinemaxwell 0.6.
Basically you do not have to hard path your texture paths. Just let Cinema 4D use your paths from your preferences and it should work with just the normal file name of "Filename.ext" for those files that reside in those directories. All others that are outside those paths will trigger the prompt from Cinema 4D that will ask if you want to move your textures into your the directory that your scene resides in.
At the moment, this is something that a lot of people have wanted and it looks like it has been addressed by Next Limit.
See following reference for more information.
http://www.maxwellrender.com/forum/view ... 3640#43640