Add zig zag to controller connection

[Ebuechner]

I have a 270 degree tree with 12 strings 330 nodes per string and 3 strands per string.
I often sequence down to the Strand level and it's a pain in the ass when some of the strands operate in the opposite direction while dropping something like a single strand effect or a morph.
Up until now I've used a custom set up 36 strings  110  nodes per string  1 strand per string with zigzagging in the controller and individual start channels to have xlights operate correctly.
While testing out the beta this custom setup shows up as a mess especially when you visualize the controller.

[Gilrock]

I can't follow what the problem is reading this.  I understand the part about not having zigzag in xLights and doing it in the controller because that's how I like to do it.  But when you do that there is no need for individual start channels you only need to do that when you have a gap between strings which if you do then I'd say get rid of the gaps they aren't needed.  What does "shows up as a mess" look like?

[Ebuechner]

We can ignore the part about the individual start channels because that's something that went back to a much earlier set up when I had gaps which I've fixed since then.
The problem is with a conventional setup letting xlights do the zigzagging instead of the controller, sequencing at the Strand level has some strings behaving in the opposite direction.
With my custom set up showing 36 strings instead of 12 like I actually have it shows overlaps on the visualize controller.
I was hoping that adding a zigzag to the controller connection will allow xlights to behave correctly at the Strand level while allowing me to better match my physical layout.

[Gilrock]

I'd have to check tonight but I thought there was already the ability to define zig-zag in the controller properties under a model.