@Shakes999 - What an incredible accomplishment!!
Can’t wait to see it fully mapped.
I would think you can go with the “ghost pixel” approach for most volumetric patterns and get pretty great results without needing the custom code approach I wrote out in that thread.
You’ll still be able to clone most 3D patterns to all 4 PBs and not need to make any pattern code tweaks to the individual copies. (Apr '23 edit: Not anymore! Now you can use the new Sync feature to just write code in one place and have it used on all 4 towers!)
If I understand a “tower” correctly, it’s two upright 16x16 planes, and one Pixelblaze drives one tower using two output expander channels.
Let’s say you have a cube map that generates [x,y,z] from [0-15, 0-15, 0-1]. Even though each Pixelblaze will be configured for 512 LEDs, you’ll add one or two extra points to your map on each board. The extra points you add will be different for each board. Let’s assume Cartesian coordinates where as you look at the front of the cube, [0,0,0] is in the left-bottom-rear (farthest plane from the viewer).
The Pixelblaze driving the two furthest towers of [x, y, 0] and [x, y, 1] will have a map that you append one phantom pixel position to: [0,0,15].
The next Pixelblaze driving towers of [x, y, 2] and [x, y, 3] need two phantom pixels of [-2,0,0] and [14,0,0].
Does this make sense?