Geometry from the new H16 boolean node mishandled by Octane

Forums: Geometry from the new H16 boolean node mishandled by Octane
Houdini Integrated Plugin

Moderator: juanjgon

Geometry from the new H16 boolean node mishandled by Octane

Postby mz2 » Thu Apr 06, 2017 11:07 am

mz2 Thu Apr 06, 2017 11:07 am
I've hit what looks like a bug in Octane with dealing with some geometry produced by the new boolean operator in H16. I've attached a screenshot from the viewport, from a Mantra render, and an Octane (notice how the side pieces have an extra "triangle"). Any idea of how I would work around this? I've tried adding a cleanup node in there, but that has no effect (and indeed the only way I can see erroneous geometry is with Octane, both Mantra and the viewports are consistently fine with the geo).

Octane:

Screen Shot 2017-04-06 at 12.00.31.png
Octane rendering



Mantra:
Screen Shot 2017-04-06 at 11.58.37.png
Mantra rendering


Viewport:
Screen Shot 2017-04-06 at 12.04.02.png
Wireframe viewport showing it's all fine

Screen Shot 2017-04-06 at 12.04.07.png
Shaded viewport showing it's all fine there too


Houdini project file:
bunk-bed.hiplc.zip
Houdini bunkbed project
(96.6 KiB) Downloaded 67 times
mz2
Licensed Customer
Licensed Customer
 
Posts: 18
Joined: Sat Feb 25, 2017 11:40 pm

Re: Geometry from the new H16 boolean node mishandled by Octane

Postby juanjgon » Thu Apr 06, 2017 11:18 am

juanjgon Thu Apr 06, 2017 11:18 am
Hi,

It seems a ngons issue. Please add to the object the Octane spare parameters and enable the "Tessellate NGons" parameter. This should fix this kind of issues.

In the new Boolean SOP, there is also an option to detriangulate the polygons that probably should be disabled to work with Octane.

Thanks,
-Juanjo
Attachments
image002553.jpg
Computer Graphics Software Developer
Octane plugin development and support: LightWave and Houdini
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 7358
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Re: Geometry from the new H16 boolean node mishandled by Octane

Postby mz2 » Thu Apr 06, 2017 12:16 pm

mz2 Thu Apr 06, 2017 12:16 pm
Amazing, thank you so much! I can confirm also at my end that your suggestions worked.
mz2
Licensed Customer
Licensed Customer
 
Posts: 18
Joined: Sat Feb 25, 2017 11:40 pm

Re: Geometry from the new H16 boolean node mishandled by Octane

Postby juanjgon » Thu Apr 06, 2017 12:27 pm

juanjgon Thu Apr 06, 2017 12:27 pm
Yes, remember that Octane doesn't have a native support for NGons, so for render them they must be tessellated on the plugin side.

Thanks,
-Juanjo
Computer Graphics Software Developer
Octane plugin development and support: LightWave and Houdini
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 7358
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Re: Geometry from the new H16 boolean node mishandled by Octane

Postby mz2 » Thu Apr 06, 2017 6:19 pm

mz2 Thu Apr 06, 2017 6:19 pm
Is there an argument against toggling the NGon tesselation on by default? Is the thinking that I'll be able to achieve a better result potentially with the host application's "native" tesselation?
mz2
Licensed Customer
Licensed Customer
 
Posts: 18
Joined: Sat Feb 25, 2017 11:40 pm

Re: Geometry from the new H16 boolean node mishandled by Octane

Postby juanjgon » Thu Apr 06, 2017 6:36 pm

juanjgon Thu Apr 06, 2017 6:36 pm
Well, the main problem is that with this option enabled the extraction time is a bit longer, and usually it is not needed at all. This is why it is disabled by default. Perhaps I could add an option to the ROP node to enable this option globally if needed, or enable it by default.

Thanks,
-Juanjo
Computer Graphics Software Developer
Octane plugin development and support: LightWave and Houdini
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 7358
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Return to Houdini


Who is online

Users browsing this forum: No registered users and 2 guests

Fri Apr 03, 2020 9:02 am [ UTC ]