Page 1 of 1
Visible edges/polygons in bump or anisotropy
Posted: Sun Feb 23, 2020 12:32 am
by RC-HelicX
Hi,
I have a problem when using anisotropy or bump shader on non-planar surfaces.
Don´t know wether it´s my fault or a problem with Octane Render itself, but I can´t figure out whats the problem. Already tried Octane 2018, 2019 and 2020.
Maybe there are some people who can try to recreate my problem.
Create a primitive sphere with 100 segments and assign a standard metallic Octane material with Beckmann BRDF, roughness and anisotropy. No matter if I have phong and smoothing activated, remapped the UV´s, changed the normals, or anything else. I always have visible edges of the polygons.
Like mentioned, the problem only occurs when using a bump texture or anisotropy.
Thanks in advance!
Greets,
Robin
Re: Visible edges/polygons in bump or anisotropy
Posted: Sun Feb 23, 2020 5:13 pm
by frankmci
I can confirm, at least in the anisotropy I tested. It's interesting and perhaps helpful to the devs that it's only happening on the primary bounce, while secondary, etc., don't exhibit the behavior.
Re: Visible edges/polygons in bump or anisotropy
Posted: Mon Feb 24, 2020 9:08 am
by bepeg4d
Hi,
this is a known limitation of Octane core, not related with plugin.
You need to increase the geometry subdivision, or reduce the anisotropy strength.
As a workaroud, you can use the Octane Object tag to add subdivisions only at render time.
ciao Beppe
Re: Visible edges/polygons in bump or anisotropy
Posted: Mon Feb 24, 2020 4:06 pm
by RC-HelicX
Hi
thanks for help!
Thats realy sad to hear. Is there anything known when this problem will be solved, oder will it even get solved anytime?
Subdivision is no option for industrial parts with defined surfaces. The only way I could go is increasing the mesh resolution to an insanely high amount when importing into C4D.
But thats not ideal for my scenes with hundreds of objects.
If this problem wont get solved, I have to rethink if Octane really is the best suiting render engine for me...
Greetz,
Robin
Re: Visible edges/polygons in bump or anisotropy
Posted: Tue Feb 25, 2020 8:04 am
by bepeg4d
Hi Robin,
please, give it a try with Octane object tag Subdivision tab, there is also an option for corner subdivision, it works only at render time, and you can check the results in realtime in Live View.
ciao Beppe
Re: Visible edges/polygons in bump or anisotropy
Posted: Tue Feb 25, 2020 4:59 pm
by Goldorak
A fix is now in progress for 2020.2, didn’t have time to squeeze this in 2020.1 as RC1 is now feature locked.
Re: Visible edges/polygons in bump or anisotropy
Posted: Tue Feb 25, 2020 6:59 pm
by RC-HelicX
bepeg4d wrote:Hi Robin,
please, give it a try with Octane object tag Subdivision tab, there is also an option for corner subdivision, it works only at render time, and you can check the results in realtime in Live View.
ciao Beppe
Thanks I already tried, but it messing up more than fixing my problem
Goldorak wrote:A fix is now in progress for 2020.2, didn’t have time to squeeze this in 2020.1 as RC1 is now feature locked.
These are good informations, thanks!
Then I´ll wait for the fix. Possible to say when it will be released? I have to render some stuff for a fair in 5 weeks and want to get the results as good as possible.
Greetz,
Robin
Re: Visible edges/polygons in bump or anisotropy
Posted: Mon Sep 13, 2021 2:50 am
by krivel
Has there been a fix for this? I have some hard surface modeling that I wanted to apply a nice anistropic to and I just see these hard edges/polygons. Its not a surface I can subdivide. This seems like a pretty major bug to me. I can't imagine there's not a solution yet?
Re: Visible edges/polygons in bump or anisotropy
Posted: Mon Sep 13, 2021 7:21 am
by bepeg4d
Hi,
please try with 2021.1-RC1-R3:
viewtopic.php?f=85&t=78153
But it is a test version, not ready for production yet.
ciao Beppe
Re: Visible edges/polygons in bump or anisotropy
Posted: Mon Sep 13, 2021 2:26 pm
by krivel
I will try and that's great if its fixed but I need to render this on Rebus and I'm sure they don't have this version right?