Camera clipping issue Tweet

[nickmedukha]

Hi everyone,

So i've got this interesting bug/problem in Houdini, using the Octane plugin.
Octane version: 2020.1.3.0 (Jun 22 2020)
Houdini version: 17.5.173

I have a spline set up, checked in Octane to render as hair, but apparently only a part of the mesh is visible in IPR.
As soon as I move the near clip slider in the camera settings all the way to the up and bring back down to 0, everything works.

I have exported this as alembic in C4D and it works perfectly, so I'm guessing what could cause this issue in Houdini.

Please see attached screenshots.

Any suggestions will be greatly appeciated.
Thanks in advance,

Nick

[juanjgon]

Hmm, this seems a problem with the near clipping parameter in the camera OBJ node. Do you say that you have set it to a very small value and the clipping is still there?

Thanks,
-Juanjo

[nickmedukha]

Yep, I've tried even with zero.

The fix for IPR live preview is attached. But that doesn't work for rendering. Might be I can keyframe it going
frame 1 = 0
frame 2 = 10
frame 3 = 0

like I manually do, but that feels like a tricky workaround.

Please see the attachments.

[juanjgon]

What a weird issue! Can you send me this scene to take a look at it here? Perhaps the object is too big, or small, or too far from the center ... it is hard to say without the scene.

Thanks,
-Juanjo

[nickmedukha]

Sure thing, attached.

Will appreciate if you will have any solutions

As I cant attach .hip files, here is a DB link
https://www.dropbox.com/s/s0ap2bqj3s6os ... s.hip?dl=0

[juanjgon]

Hi,

Sorry, I'm still investigating this issue. It is something really weird that I don't fully understand yet.

Thanks,
-Juanjo

[juanjgon]

Ok. I've just found the problem. It was a tricky issue related to how the plugin was computing the near and far planes from the Houdini camera node. It should be fixed in the next build, but meanwhile, if you need the fix for your project, send me a pm including your houdini version and Octane license type and I'll send you a custom 2020.1.5 plugin build including the fix.

Thanks for reporting this issue!
-Juanjo