Hi guys.
I've noticed incorrect QStrip.ComputeStrips behavior when stripping one triangle with { 0, 1, 2 } indices, evaluation depth = 1 and cache size = 2 (maybe it affects the bug).
QStrip returns this incorrect array: { 65021, 2, 2, 1, 0 }
This issue is not critical for me, just FYI.
Thank you Dmitry, I've let the team know so they can investigate.