Hey Octane renderers!
I apologize if this is something discussed here before, but I'm interested to hear what you guys think of the fact that Octane render seems to render errors/corrupt objects as soon as a couple of polygons intersect? I even have problem with render errors when the object is 100% dissolved through the dissolve panel and when the object is subpatched and some POINTS enters the surface next to it, i.e. not even the subpatched surface itself.
The only workaround I have today in my scenes is to first make the object 0% visible and then MOVE it to another location quickly with stepped motion so that it doesn't continue to give artefacts to objects that would happen to occupy the same space.
I love Octane, but I must say, this is very annoying and I haven't seen this behaviour in any other renderer.
Does anyone have an advice for me or is it me doing something wrong?
Thanks
Overlapping surfaces problems
Moderator: juanjgon
-
3dreamstudios
- Posts: 479
- Joined: Fri Apr 03, 2015 8:55 pm
Could you create a simple scene that shows what your describing? I think I get it but not sure I see the issue on my side. Could be a ray epsilon issue? I run into that with big scenes where the camera is far away, quite a bit!
Hi,
A dissolved object is an object with 0% opacity in all its shaders, but the object is still there, so if the polygons are overlapped with the polygons of other objects, you are going to get rendering artifacts. You need to fully disable the object to avoid this problem.
There is an option in the Octane object properties custom object plugin to animate the object enable state that could help with this problem. While this parameter is 1.0 the object is enabled, but as soon as it has a lower value, the object is disabled. You can animate this parameter to disable the object just when the object dissolve value becomes 0.
Hope this helps,
-Juanjo
A dissolved object is an object with 0% opacity in all its shaders, but the object is still there, so if the polygons are overlapped with the polygons of other objects, you are going to get rendering artifacts. You need to fully disable the object to avoid this problem.
There is an option in the Octane object properties custom object plugin to animate the object enable state that could help with this problem. While this parameter is 1.0 the object is enabled, but as soon as it has a lower value, the object is disabled. You can animate this parameter to disable the object just when the object dissolve value becomes 0.
Hope this helps,
-Juanjo