aoktar wrote:plugin looks the file is available at absolute path. if it's not a full path or not available, looks project path and tex folder. if still not found, search in octane texture paths. but not in c4d preferences paths.
I should know it can be related texture counts. or scene is saved or new file? can some peope capture a video to show problem?
Hey aoktar, sorry I've seen your response right in the moment. No video, but problably some screenshots and explanations can show up a bit of the thing.
Let me try to describe what happens here on my machine.
First, in Cinema's program prefs I have defined a path to a folder with many subfolders for all my textures. Lets call this path E:\textures. Everything that is bitmap comes in there, so I do not have to seek anything and can be sure it is found by Cinema, only defining the texture's name in a material. Since there are 100s of subfolders, there is only one path to all of them.
Then I put a folder 'OctaneTex' in there. Due to the structure of this bunch of textures this folder is 2 steps deeper in the subfolder. Lets call it E:\textures\SomethingElse\OctaneTex
In OctaneSettings in Cinema I defined the same path like in C4D prefs, E:\textures, hopingly well that Octane works the same way, searching all the subfolders.
But working a while in Octane shows up behaviour like the following. As in Cinema itself, all textures are relative, without any path in the Octane materials. First pics show the diffuse and bump channels, wich are shelled in a ColorCorrection or ImageTexture shader or both. As you see, the textures are shown in the channels, but not calulated by Octane.
The third pic is the editor view. As you can see, the material and the editor do show the texture in the channels, but Octane can't calculate a material preview. I suppose because it can't find them. The views in Material and Editor are defined by Cinemas subroutines, right? But thats all guesswork.
In the last picture you see the rendering in LiveViewer. Like in the material preview, the textures aren't calculated.
Now, this all can take a while bevore it shows up, normaly minutes. Since I'm very new to Octane, working from the last weekend on a huge project converting all materials handish into Octane ones, I was able to monitor this problem for the first days and didn't get any idea. Because in the very first moment defining these materials, every material works well and was rendered also, leaving Cinema and Octane working. But minutes or quarter hours later on, every last defined material was gone like shown above. I mostly recognized this the next day, reopening the scene. And if so, there was now way to get Octane to render the material after that, until redoing this material. Octane even shows up render errors - it started exporting and voxelizing and then only showed an info *** RENDER FAILUR *** (don't remember the exact words, sorry) and could only be restarted after restarting cinema, wich must be shot down in task manager to completely close.
So after a few days I decided to change the path in Octane settings from E:\textures to E:\textures\SomethingElse\OctaneTex. Since then every material works fine, no render errors, amazing software. And as you said, it has nothing to do with the Cinema path prefs, because I was able to reproduce the described behaviour with and without defined Cinema paths. Switching the paths forth and back in Octane settings will show up this, certain and repeatable. Probably it takes some minutes, the faster way than waiting is to restart cinema.
Hope that helped.