Page 1 of 1

Houdini Instancing bug

Posted: Sat Nov 24, 2018 11:39 pm
by MagnusL3D
Houdini Instancing not working with 2+ instance attributes. Tested with both latest v3 and v4 in both 16.5 and 17.0 with latest supported production builds.

Image attached to show that the 2nd instance attribute for some reason gets ignored.

Re: Houdini Instancing bug

Posted: Sun Nov 25, 2018 7:06 pm
by juanjgon
Hi,

Sorry, I'm testing this feature here and here it seems to work fine. The "instance" attribute can point to any available OBJ node without problems, rendering all of them. Can you send me the scene to take a look a and check what could be the problem?

Thanks,
-juanjo

Re: Houdini Instancing bug

Posted: Sun Nov 25, 2018 8:28 pm
by MagnusL3D
I figured it out, if the object the instance attribute is pointing at has its blue display flag turned off it doesnt work in Octane (it works in Mantra / Redshift / Arnold).

Here is link to .HIP where it fails. Done in 17.0.352 and 4.00.0.21.
https://drive.google.com/file/d/1lcLio_ ... p=drivesdk

Re: Houdini Instancing bug

Posted: Mon Nov 26, 2018 11:02 am
by juanjgon
Yes, sorry, currently the objects to be instanced must be enabled for rendering because if they are not extracted, the plugin can't instance them. In any case, you have an option in the Octane OBJ spare parameters to hide the master object from rendering, if needed.

Hope it helps,
-Juanjo

Re: Houdini Instancing bug

Posted: Mon Nov 26, 2018 2:17 pm
by MagnusL3D
I seem to remember that this was working before, so did something change ? Just curious =) Thanks for the info.

Re: Houdini Instancing bug

Posted: Mon Nov 26, 2018 10:06 pm
by juanjgon
MagnusL3D wrote:I seem to remember that this was working before, so did something change ? Just curious =) Thanks for the info.
Nope, sorry, this is the behavior of the Octane plugin from the beginning, as far as I can remember. The objects to be instanced must be always enabled to let the plugin extract it without needing a second extraction pass or a scene preprocessing. This is something that could be fixed from the plugin side, I have this feature on my TODO list, but well, the workaround is easy, so I don't have any ETA about when it could be available.

Thanks,
-Juanjo

Re: Houdini Instancing bug

Posted: Tue Nov 27, 2018 8:23 pm
by MagnusL3D
juanjgon wrote:
MagnusL3D wrote:I seem to remember that this was working before, so did something change ? Just curious =) Thanks for the info.
Nope, sorry, this is the behavior of the Octane plugin from the beginning, as far as I can remember. The objects to be instanced must be always enabled to let the plugin extract it without needing a second extraction pass or a scene preprocessing. This is something that could be fixed from the plugin side, I have this feature on my TODO list, but well, the workaround is easy, so I don't have any ETA about when it could be available.

Thanks,
-Juanjo
Thanks for the update, was very curious because I rember doing test renders and it worked, and then it suddenly stopped..but i guess I must changed something myself then :D

Re: Houdini Instancing bug

Posted: Wed Feb 05, 2020 9:25 pm
by juanjgon
The next Octane 2020.1 plugin build will support the instancing of objects that are disabled. In this case, the master objects will be hidden automatically.

Thanks,
-Juanjo

Re: Houdini Instancing bug

Posted: Thu Feb 20, 2020 6:16 pm
by efxlab
From the actual XB3 ?

Re: Houdini Instancing bug

Posted: Thu Feb 20, 2020 6:21 pm
by juanjgon
Nope, in the upcoming 2020.1.0.3 RC1 build ...

Thanks,
-Juanjo