Tomas Slancik

traileverse
tons of errors and all pointing to polysplit nodes

PolySplit is very sensitive to the input geo as it needs to do split on exact prim number, exact edge, etc.
so it's likely to error out if for example is expecting to cut 10e5:0.5, but suddenly prim 10 doesn't have 6 edges anymore

so all I'm saying is that because Poly Split errors out it doesnt necessarily mean that polysplit is the issue
however if you stash the geo on node before in working build and then plug it to next PolySplit in non working and it still errors out, then you can assume it's the PolySplit, since on the same geo it should work

when I have time I'll check your file on 684 to see where the geo changes between builds

from a quick look it doesn't seem like the PolySplit is the main issue

it seems like by the time it gets to Polysplit, the geo is already not containing the elements that PolySplit is supposed to split

I compared 3 different builds, but can't find a single one that would work, however all 3 resulted in different geo after "fuse2" node

it may be easier to find a culprit knowing which build has it working

VEX is best when used for processing elements in parallel and each element will figure it's own attribute values

however if you want to set values for other elements, it may be helpful to know this [www.sidefx.com] as those limitations may be confusing if you are not aware of them