Possible bug: Unexpected User Instance ID AOV behavior

[speltrong]

Hi

I make a standard cloner and use the Cryptomatte User Instance ID AOV, all of the clones are on the same matte (ID=0). If I add an effector and make sure "Use effector color" is on, then all the clones appear on different mattes like I'd expect, even if all the parameters for the effector are turned off.

Is this a bug, or some limitation of C4D that has to be worked around?

Windows 11 (current) / Mobile 4090 GPU / C4D 2025.0.2 / Octane 2024.1-[R3]

Thanks

-s

[bepeg4d]

Hi,
this is expected, it works correctly if you change the MoGraph Instance mode from simple Instance to Render-Instance, or Multi-Instance:

ciao,
Beppe

[speltrong]

Thanks for the reply @beppe

Interesting, but I'm just curious why you'd need an effector - even one that doesn't do anything to the clones - to make it work in regular instance mode.

Do normal instances not get proper color assignments or something that an effector's color mode fixes?

Multi-instance and render instance don't work well with some other C4D things, so it's not always a viable option (though it's MUCH faster when it is). Adding an effector with all the effecting parts turned off to fix an AOV isn't intuitive and slows you down if you don't know why it's happening. Just trying to get my head around why it's like this.

-s

[aoktar]

The plugin's logic on Cloners written for instanceIDs to generate them when an effector with color mode activated. It's for normal mode of Cloners.
It's activated for other modes by def. It's a choice to avoid the extra calculations because of unused cases.

[speltrong]

ah, makes sense - thanks @aoktar!

-s