13K pixels in a 3D map will definitely push a few limits. The map would be 78k of coordinate data which has to sit in memory. There might be enough RAM, but I would’t recommend it.
What I’d recommend for something this large and going with the extra pixels method would be to have a few extra marker pixels (in the map only), just enough to keep the map coordinates scaled to the larger world, so it doesn’t normalize to the single subsection’s coordinate space.
I do not recommend setting the pixel count to 13k on each subsection. It is unnecessary to keep multiple PBs in sync for time() based patterns.
@LEDCreate, Some animation methods in some patterns do not lend themselves to parallelization across a Firestorm of Pixelblaze, which relies on synchronized animation time bases. KITT is an example of a pattern that doesn’t use time(), and instead uses the relative passage of time with delta and incremental calculations in beforeRender(). In cases like that, Firestorm/timesync can’t keep them synchronized.
However, we’ve recently had some fun noodling how to make a time() based KITT that would parallelize via a Firestorm setup with timesync.