There are many questions, i will try to reply all of them:
At the moment all the crashes are happening during Graph editing [...], but I`m thinking that might be a problem with the speed of manipulation with all the nodes. I'm probably not waiting long enough to command complitly be finished and I`m already on the next node...
Yes, perhaps the hold operation is received while RC object is rebuilding. Theorically that should not happen, but we'll test it.
But, right now I`m more concerned about this Sequence behavior losing the last row on the Clipping threshold end
As far as i can see, there are not enough rows in the array to include that last segment. I mean, clipping area is not enough large to include a complete frame.
... the difference between Section vs Start reset.
Well, this is a tricky issue. Effectively, there is a know bug with Y Sequence, when applied to multiple sub-splines: first sub-spline is correct, but in next ones the first segment is incremented by one (in the sequence).
I can fix it, but that would break existing scenes, which have been designed considering current behaviour (that happens with the customer who reported this issue intitially).
Second, I think I`ll already requested or I was about to do during some Betas: Could be possible to have some General features from L1S like Reverse, Mirror, Flip A/B...
It's on the wishlist for next versions. By now we're releasing mainly update fixes, to get a fully stable version. Next, we'll start to make changes in a new beta.
On the Red Note I have set Transform Operator to Force Instance, I set Generators to be no-sliced Free but I still got some non-instanced segments on the Statistic report.
I have not checked this yet. I will take a look to it.