Page 2 of 2
Re: Convert relative tex paths into absolute
Posted: Fri Oct 21, 2022 9:29 am
by aoktar
Writing is easy but there are a tricky part to search textures. It should be exact same behavior as plugin does. It makes it a bit harder to find the way. I'm still not understanding why do you wish to convert to absolute paths? Explain it shortly
Re: Convert relative tex paths into absolute
Posted: Fri Oct 21, 2022 10:31 am
by ShivaMist
Globalized file names are used when rendering on a network with UNC path, especially with Thinkbox Deadline. It's used so the rendering machine will find the path on the network instead of looking for the c4d tex folder.
Re: Convert relative tex paths into absolute
Posted: Fri Oct 21, 2022 1:01 pm
by silanbekjarov
Hey @aoktar,
I wish to convert to absolute paths for two reasons:
1. I want the textures to be found by the network rendering manager (which is deadline). It cannot find them if it gets just a filename for instead of a full path. (tried all the tricks, folder mapping etc). It seems that it takes the filename provided by cinema 4d which cinema 4d unfortunately declares as an absolute path and shows the texture as missing, as it doesnt know where to look.
2. In the octane texture manager everything is in order and found. The suggested path shows what cinema4d basically shows: only the file name. But in the "real path" tab the full path is shown correctly leading to the textures on the network. When I manually replace the filename in suggested path with the full path from "real path" it is also changed in the cinema4d project asset inspector and thus is now also found by deadline.
I dont need the script to look for the textures as octane texture manager shows the correct path in "real path". I just need to autopopulate "suggested path" with what is inside "real path"
Hope this makes sense.
