Not really, since the animations themselves are very much alike - they've just been hued and otherwise slightly edited to have a slightly different appearance.
The main factor in here is the $Flicker factor in tables. It would be easy to release optional table and, for example, embed it into the release along with script files that could be used to change file names of currently active and disabled table, thus creating an option. It wouldn't be too much of a problem.
I'll see how it turns out.
Of course there's also the fact that
currently the terran beam has 32 (or 33) frames, while shivan and vasudan beams have 22 frames. So, naturally the terran beam is the least "flickerish" as of now. Increasing amount of frames for Shivan beam would largely reduce "wildness" of the Shivan beam.
It wouldn't be too much trouble to make another, 32-frame set for shivan and vasudan beams... it would result in slightly bigger DL sizes, though.
Have you spotted any anomalies such as some beams having visibly abnormal tile factor, either too sparse or too dense, or mistyped section widths that would be probable in a work like this? I haven't yet met any 70 metres wide AAA beams, have you met anything like that?
I'm just asking because I really don't have time to properly playtest the tables after every change.
But I'm glad if you like my work, and I appreciate the feedback.
