It would seem that when creating arrays of somewhat complex, nested components and multiple layers with multiple tool changes there is a kind of layer panic that happens and objects/vectors get dumped to random layer/s.
The fix that worked for me was to add the items to the layer to which a tool path is associated to clear things up.
Would be great to be able to force a tool to do all its work on each group within an array in order to avoid jumping between the array.
It seems that CC will create any new objects in the Active Layer…period. So whether you’re duplicating or creating arrays, etc. everything will be produced in the active layer regardless of their current layer.
If you’re assigning toolpaths by layer, then every new object will get the toolpath of the active layer
For example: Given this layer setup…each object is in its own layer
With one layer active (in this case, the layer with the triangle), if you create an array, duplicate, or copy/paste, the new objects end up in the active layer and all the objects inherit the Texture toolpath of that layer
However - if you assign the toolpaths by object, and then create an Array, Copy / Paste or Duplicate, the toolpaths remain with the objects, regardless of layer (although all three new objects do still end up in the active layer)
And…just confirming: There does seem to be a defect in that the “Duplicate To Current Layer” checkbox does not have any effect. It’s going to duplicate to the ACTIVE layer, regardless of the checkbox state.