Closed Pherakki closed 3 years ago
Bug was due to some over-zealous interpolation in the frame integerisation step... for frames that were already integers, the interpolator would replace the frame value with an interpolation between its neighbours. Since this bug should only ever occur for frames where the frame index is exactly an integer, the fix is to replace the less-than and greater-than comparators with less-than-or-equal or greater-than-or-equal, so the interpolation is between two identical values at the integer frame. See the alteration to the comparators in f1c6e8f703dc12ecafb5dc4c62bae4d5a154b6aa.
Small fix but annoying to track down... and not the prettiest solution, but it works.
See: cam_chr005_bv01.anim