Yeah, font was missing the config files. Copied one over from the default package, and that about sorted things out.
Great
Looking through the provided configs and lightsaber.ino, am I right in assuming FireBlade is the only pattern that supports delayed ignition of second/third blades?
Yep, that is currently the case.
However, that would be relatively easy to fix, maybe I can work on it this weekend.
Also curious if there's any technical reason both crossguards (four strips) can't operate from one data pin while still being on separate grounds. Would be nice to have the third data line open for a pixel crystal since I have that last FET available anyway. Won't be doing it on *this* build, but I've got another crossguard I'm planning on building out. Think I've got it figured out code-wise from the dual-blade example, but thought I'd ask before possibly messing something up.
That is entirely doable, and would be configured exactly as if the grounds were hooked up together, something like:
WS2811BladePtr<144, WS2811_ACTUALLY_800kHz | WS2811_GRB, 7, PowerPINS<bladePowerPin4, bladePowerPin5> >()
The only drawback is that you can't control the crossguards individually.