Strange behavior with TOPs inside/outside a Base Component

Hi!

I tried to replicate this basic tutorial, but I’m experiencing a strange issue. When I place everything inside a Base Component, I can see the correct TOP animation inside the Base, but I don’t see the same result outside of it.

I’ve attached the project file and I uploaded a video here.

Any idea what might be causing this?

topIssue.toe (5.1 KB)

Ok, I fixed. In the tutorial the CHOP Execute was trigger on “Off to On” but this doesn’t work when all is inside anoter COMP. I’m not really sure the reason. Now I set the trigger on “On Value Change” and it works fine.

It’s easy but I add the fixedp project anyway.

topIssue_fixed.toe (5.1 KB)

Hi @Mauro,

not quite sure what prevents it from cooking in your first example tbh. But great that you found a simple solution. The onValueChange will execute twice for 0→1 and 1→0 - perhaps that why it’s all being cooked properly. I’ll have a closer look.

This effect can be created in another generative way by utilizing the Event CHOP. It’s a bit simpler in a way and arguably more versatile. You can see exactly this as an example in the OP Snippets for the Event CHOP.

Hope this helps
Markus

Thanks a lot @snaut!

Yes, you’re right. I missed the issue with onValueChange. Right now it’s triggering twice because I’m handling both state changes (0 → 1 and 1 → 0).

As for the snippet, I actually discovered it a few days after I fixed my example. Thanks anyway for the suggestion!

1 Like