Help!Can't the Replicator be used like this?

I want to achieve that every time I click on the keyboard 1, a new geo will be generated. I transfer all the data to the table to implement the logic of the replicator, but each time the model is generated, the same geo master model cannot be updated each time.

I feel that there seems to be something wrong with the logic, but I don’t know how to solve it, or is there any other way to achieve this effect? ​​Please let me know, thank you! ! :sob: :sob:

test.2.toe (6.1 KB)

I think you’re askin, how can each replicant (g#) show one of the three box/sphere/tube. To achieve this you’ll want to modify your Select TOP inside the master to point to a unique shape. Right now they’re all pointing to null2 so they’re all going to be the same.

Create a unique Null TOP for each shape, e.g. shapenull1, shapenull2, shapenull3 and so on. Then set the select node inside to select from f"../shapenull{parent().digits}".

Personally I’d add a custom integer parameter, say Shapenum, onto my master and have the select node inside refer to that custom parameter. That way you can test with your master. Then, in the replicator’s callback, set the the expression c.par.Shapenum.expr to the value you want (or pull it from the table if that’s easier).

Thank you! I tried your method and it still copied the same shape. I have thought about this problem, but if I want to make a large number, such as 300, I need to copy a lot of data to correspond, and also have position information and color information. Maybe this is a more troublesome thing?

If 300 is what you’re aiming for, then yes, this approach doesn’t scale that well, and using a component for each instance invokes a lot of machinery which will impact performance.

Maybe back up a bit and explain the bigger picture of what you’re trying to achieve?