Page 2 of 2

Re: OctaneRender 2023.1.2 for Houdini production (2023.1.2.0)

Posted: Fri Jan 26, 2024 2:01 pm
by galleon27
There is a bug with analytic lights and motion blur on.
with Motion blur
with Motion blur
without Motion Blur
without Motion Blur

Re: OctaneRender 2023.1.2 for Houdini production (2023.1.2.0)

Posted: Sat Jan 27, 2024 8:53 am
by ricky_otoy
tripledistilled wrote:
ricky_otoy wrote:I don’t think we expose the up vector controls in Houdini. Is there a specific reason you need it exposed? Are you trying to use Perspective correction?
Is there any way to default the camera target to zero, with an up vector, for every orbx export?
No not as far as I know, maybe if you create a null with a contraint to look at the null. But I would have to test that theory first, otherwise I will put in a request for it and see what we can do.

Re: OctaneRender 2023.1.2 for Houdini production (2023.1.2.0)

Posted: Sat Jan 27, 2024 9:04 am
by ricky_otoy
galleon27 wrote:There is a bug with analytic lights and motion blur on.
withMotionBlur.png
withoutMotionBlur.png
Hi, it seems this is a core Standalone bug, I will chat to the team about it - thanks for the test scene and letting us know.

Re: OctaneRender 2023.1.2 for Houdini production (2023.1.2.0)

Posted: Fri Feb 02, 2024 12:30 am
by galleon27
Why is collapsing and expanding nodes in octane material reloading the render? Creating new materials and alt+dragging to copy nodes inside the material also reloads the render.
I don't remember if it was always like that, don't think it was, but it sure as hell is annoying especially when dealing with large scenes. I have to pause the render whenever i do any action because it takes ages to do any change. It defeats the whole purpose of the IPR.

Re: OctaneRender 2023.1.2 for Houdini production (2023.1.2.0)

Posted: Fri Feb 02, 2024 8:24 am
by ricky_otoy
galleon27 wrote:Why is collapsing and expanding nodes in octane material reloading the render? Creating new materials and alt+dragging to copy nodes inside the material also reloads the render...
Yes that really shouldn't be happening, will investigate - thanks and sorry for the inconvenience it is causing!