Page 1 of 1

Instance Range no longer working for a cloner

Posted: Sun May 22, 2022 12:58 pm
by speltrong
It seems like Octane is no longer getting instance id numbers directly from a cloner.

I grabbed the example file from https://docs.otoy.com/cinema4d/InstanceRange.html and put it into C4D s26/Octane 2021.1.5(R2). Attached is a screenshot showing that the instances with Octane Object Tags are still responding correctly, but the Cloner itself is no longer mapping to the gradient.

I'm using Win 10 with an RTX 3080.

-s

Re: Instance Range no longer working for a cloner

Posted: Sun May 22, 2022 8:17 pm
by aoktar
I supposed I've ruined something and checked. But it's working! Did you use render instances?

Re: Instance Range no longer working for a cloner

Posted: Sun May 22, 2022 11:59 pm
by speltrong
I supposed I've ruined something and checked. But it's working! Did you use render instances?
Oh, no - didn't try render instances, since in the help file it doesn't say that you need to do that. Neither the screenshots in the help nor the test file is set up like that, so I'm assuming it worked with normal instances in previous versions.

Render instances are extremely limited in what you can do with them (no deformation, can't offset animation, doesn't work with Subdivision Surfaces, etc etc), so I always avoid them.

Any way you make it work with regular instances in a cloner?

-s

Re: Instance Range no longer working for a cloner

Posted: Mon May 23, 2022 12:10 am
by aoktar
It should be changed to fix something else in a previous version. You can activate ID generation by adding some effector with using the color parameter. Also you can use Instance Color for different usage.

Re: Instance Range no longer working for a cloner

Posted: Mon May 23, 2022 12:18 am
by speltrong
Ok, thanks much :)