Offset growth animation with falloff and Set Time Sequence

[ApzzpA]

Hey Toadstorm,

Following Rick Noseworthy's In Bloom course.
https://www.youtube.com/watch?v=S9Ccta-6YC8

To offset the growth along the branch Rick is using Redshift proxies and s@instancefile using a falloff however I am using Octane which does not use proxies.

So I was wondering how I could achieve this using mops falloff and set time sequence?

Thanks

[toadstorm]

I'm not an Octane expert, but according to https://render.otoy.com/forum/viewtopic ... 01&t=76202 it's possible to directly instance bgeo files using the instancefile attribute, which MOPs supports.

[ApzzpA]

Thanks Toadstorm! I've been using Alembics for each plant animation and then copying to points. I created a mops falloff before my scatter to points and then after the copy to points I use the set time sequence using the mops falloff as the attribute but everything disappears for some reason. I don't suppose you have a hip which demonstrates offsetting animation using a mops falloff?

[toadstorm]

With Alembics you need to enable the sequence length / cycling override and specify the start and end ranges. The included example file "animated_instances.hip" should show you the workflow.

If you're able to post your hip file here I can try to debug it for you. Or email it to me at henry@motionoperators.com if it can't be shared publicly.

[ApzzpA]

So, I tried the bgeo method and that actually works. I don't know why this is more well know vs the redshift proxy version.

I am going to the following a try also as I would like to use this method in future as it is easier to setup i.e a lot less vex

[ApzzpA]

If you're able to post your hip file here I can try to debug it for you. Or email it to me at henry@motionoperators.com if it can't be shared publicly.

Still can't seem to get it to work so would absolutely greatly appreciate you taking a look. You have been extremely helpful so far. I will email you as it is a paid course.

[toadstorm]

Based on your scene, what you'd want to do is use the Redshift Proxy Output SOP to write your plant sequences to disk as .rs files, then load them back in using the Redshift Packed Proxy SOP. Copy those to points using the variants workflow you already have in place, then use MOPs Set Sequence Time like you already are. If you look at the instancefile attribute, you'll see each sequence individually retimed based on the index attribute you created. You might want to also set the mode to "clamp" instead of "cycle" so your plants don't re-bloom as your index increases beyond frame 150.

The viewport doesn't support this retiming but Redshift absolutely does; you'll just need to do a few test renders to see it. Writing out Redshift proxies means your scene translation and render times will go way down!