Replicated CHOP Updating Issue

Hi guys,

I have a replicated ContainerOP that has a constant inside. The constant parameter is using an expression to grab data from a table outside of the Container. If I load up the TouchDesigner file, all of the replicated items pull from the first cell in the table, but if I change the expression (in the original Container), and change it back to exactly the same as it was it works fine and all of the children pull from the individual cells. Is there a way I can make the expression work correctly without going in and “re-executing” the expression every time?

Here is the expression I am using to drive the Constant>Value0:
op(‘…/jsonData_useable’)[me.parent().digits,1]

*jsonDta_useable is a tableOP

Thanks!

Hi matochai,

Are your replicants clones?
Does making the constant clone immune correct this problem?

If you re-init the replicator network (there’s a pulse button on the replicator page of the replicator COMP) does this fix the problem?
You could use an Execute DAT to re-init the network at start - this might be a matter of initialization order, so maybe delaying 100 milliseconds would make sure that your source table has cooked before your replicator fires off.

At least, those are my first guesses.

Curious to hear if you’ve found a solution.

Well the “Clone Immune” option seemed like it gave me the fix I needed but there’s still a bit of a problem.

It began working when I started it up, but now when I hit ‘Create’ on the replicator the problem happens all over again. Also if I add a new item, it takes on the values of the original as opposed to its unique value. I think I isolated the problem to a script in my container: puu.sh/hqP9o/cea0ef466a.png

The RGBTable op is the first place in the tree that all the values are the same on through all of the items. I think it’s because the DATExecute is only occurring when the hue_data table changes, but I’m nut sure how to get it to run then, but also when the item is first created.

OK I got it now! Just needed another Execute DAT that runs on Create, then the Dat Execute to run if the table value changes.

Thanks for the help Matthew! Just took you pointing me in the right direction and a bit of me talking back and forth to myself to get the solution haha.

Glad it all got sorted out, sometimes all your really need is a push - happens to me all the time.