Geometry from the new H16 boolean node mishandled by Octane Tweet

[mz2]

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:

Octane rendering

Mantra:

Mantra rendering

Viewport:

Wireframe viewport showing it's all fine

Shaded viewport showing it's all fine there too

Houdini project file:

bunk-bed.hiplc.zip

Houdini bunkbed project

(96.6 KiB) Downloaded 203 times

[juanjgon]

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

[mz2]

Amazing, thank you so much! I can confirm also at my end that your suggestions worked.

[juanjgon]

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

[mz2]

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?

[juanjgon]

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