Hi @Ewan_Opie I just had a look; I haven’t given much time to seeing how this can be worked around just yet but thought I would still chime in to tell you what I see occurring when I run the script.
Changing the lacing to Longest on the .dyf solves the issue of the value only being written to one element, but the misalignment of values appears to be due to the values being assigned to the dimension elements in the order of element creation (so based on Element ID).
The only way I am able to assign values in the order I want and without the last value being applied to remaining elements (due to lacing being set to longest) is to structure the other inputs to follow the order of Element IDs (example below, I’m telling the custom node to give Element 414714 no prefix, then 414721 prefix “pre2”, 414728 “pre3”, 414240 “pre1”)
I’m at a loss for how the inputs would be correctly associated with the correct elements without an extent of manual list structuring of the other inputs, but maybe I am misunderstanding what you were trying to feed the node. I might be wrong but I’d speculate the Rhythm Dimension.Set___Value nodes are separated (i.e. SetBlowValue and SetAboveValue are separate nodes) because then there isn’t a situation where you’d be feeding a dimension that you didn’t want to set a value for.