Fix T86745: trace sequence keyframe offset
The offset when creating the keyframes was set to `frame_target + i` but `i` starts iterating from the current frame number. The fix uses just `i` as the frame number. Reviewed By: antoniov Maniphest Tasks: T86745 Differential Revision: https://developer.blender.org/D10772
This commit is contained in:
parent
d0f05bfbcd
commit
95a2549d90
Notes:
blender-bot
2023-02-14 01:21:16 +01:00
Referenced by issue #86745, GPencil: Trace image sequence offsets frame by double the framenr
|
@ -257,8 +257,7 @@ static void trace_start_job(void *customdata, short *stop, short *do_update, flo
|
|||
ImBuf *ibuf = BKE_image_acquire_ibuf(trace_job->image, iuser, &lock);
|
||||
if (ibuf) {
|
||||
/* Create frame. */
|
||||
bGPDframe *gpf = BKE_gpencil_layer_frame_get(
|
||||
trace_job->gpl, trace_job->frame_target + i, GP_GETFRAME_ADD_NEW);
|
||||
bGPDframe *gpf = BKE_gpencil_layer_frame_get(trace_job->gpl, i, GP_GETFRAME_ADD_NEW);
|
||||
gpencil_trace_image(trace_job, ibuf, gpf);
|
||||
|
||||
BKE_image_release_ibuf(trace_job->image, ibuf, lock);
|
||||
|
|
Loading…
Reference in New Issue