Bug 473468

Summary:	Layer's stroke effect appearing in wrong animation frames.
Product:	[Applications] krita	Reporter:	AE_2
Component:	Animation	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	emmetoneill.pdx
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description AE_2 2023-08-17 05:26:33 UTC

SUMMARY
When a layer contains a few animation frames and a Stroke effect (and perhaps this might happen with other effects as well), playing the animation and then stopping it will often result in the stroke effect from another frame appearing in the frame it stopped on. Scrubbing through frames will usually correct it.

STEPS TO REPRODUCE
1. Create a multi-frame animation on a layer, add a Stroke effect
2. Press the Play button on the timeline
3. Press the Stop button on the timeline

OBSERVED RESULT
On occasion the stroke effect from another frame will appear in the frame it is currently showing.
***NOTE: This MAY technically be a case where Krita is incorrectly overlapping the frames from 2 layers (one Stroked, the other not).***

EXPECTED RESULT
Stroke or stroked layer frame should match the frame number it belongs on.

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
The animations where I have observed this use several layers, each dedicated to a different element of the image (linework, color, shadow, and most relevantly, a stroked white silhouette to thicken the contour of the animating object). Is Krita perhaps aligning things layer-by-layer as it plays, only to get its display instructions abruptly stopped, thus misaligning one of the layers?

Comment 1 Emmet O'Neill 2024-04-19 00:37:49 UTC

Hey there. I think that this issue has been fixed!

If you can, please test again using the "Krita Next" nightly version from http://krita.org (or by building Krita's "master" branch from source.) 

If "Krita Next" works correctly, then you can expect to see the fix included with the next stable version release of Krita. However, if you're still having this issue in Krita Next or with Krita's master branch, please feel free to reopen this bug report and we can continue to investigate. 

Thank you,
Emmet.