The mysterious thing for the first: one time i open up the c4d file with the native shaders from c4d, activated octane and the firts render looks like my old shader is nearly compatible.
I was so lucky to open it without big changes and thought: "Yeah, better compatiblity as expected" - but now i got the opposit.
The next time i open it up it does not recognize the original state like before
- only some elements was looking like the original c4d scene.I am new to Octane and now i have to make some of my shaders in octane again to have the best results.
Because the converter did not made it like it should.
So i have to make my alpha shader trix again. They worked very nice as Cinema 4D shader.
But conversion was not like the original. I started from scratch. I made the first version ready in Octane.
But now i see that there is a line of pixels at the gap where the texture loop is closing - and i can not get rid of it.
I exported the scene to Octane Render 2018.1.2 - sadly i saw it there too.
See my pics attached, you can see the line of pixels that normallly should not be there at the gaps - the sphere primitiv got it too..
The old c4d shader where this shader was originally made, was renderd without this pixel failures.
I saw that thisline of pixels can be seen in other alpha shaders i loaded from LiveDB too.
So i guess it is very important to inform about and hopfully can be fixed easily.
May be someone got a work around for this?
Have a good day, best regards
