Bug 422180

Summary: Layer Style: Stroke produces severe artifacts
Product: [Applications] krita Reporter: Tyson Tan <tysontanx>
Component: layer stylesAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: ahab.greybeard, dimula73
Priority: NOR    
Version: 4.3.0-beta1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Artifacts of Layer Style: Stroke (Inside)
Artifacts of Layer Style: Stroke (Inside) disappeared after toggling Fx button
Stroke-Inside-Artifacts

Description Tyson Tan 2020-05-28 14:11:45 UTC
When using Layer Style: Stroke (Position: Inside), any new freehand brush dab on the layer creates strokes with severe artifacts, and those artifacts are kept in the saved files as well. 

By simply toggling the "Fx" button in Layer panel, the artifacts will disappear.
Comment 1 Tyson Tan 2020-05-28 14:12:29 UTC
Created attachment 128862 [details]
Artifacts of Layer Style: Stroke (Inside)
Comment 2 Tyson Tan 2020-05-28 14:13:03 UTC
Created attachment 128864 [details]
Artifacts of Layer Style: Stroke (Inside) disappeared after toggling Fx button
Comment 3 Ahab Greybeard 2020-05-28 20:49:14 UTC
Created attachment 128881 [details]
Stroke-Inside-Artifacts

I can confirm this for the 4.3.0 beta-1 and the 4.2.9 appimages.
However, I don't see that they are also in a saved .kra file.

The artifacts don't happen on horizontal or vertical lines but do happen on diagonal lines and the outer edges of curves.
They have the form of a step with an exponential decay.

This does not happen with Stroke Outside. However, if you toggle off FX for Stroke Outside, there is a residual artifact that does not go away if you toggle layer visibility. It is not Saved in the .kra file.
You can get rid it by removing FX for the layer.
Comment 4 Ahab Greybeard 2020-05-28 20:49:37 UTC
Setting to Confirmed
Comment 5 Tyson Tan 2020-06-17 09:35:56 UTC
Additionally, when Stroke's Size is set to 2px and smaller, it will also introduce severe artifact around the layer's image.
Comment 6 Dmitry Kazakov 2020-08-20 21:45:43 UTC
The bug has been fixed in commit a37cbcec401cab859c240037e3f377e12dbbd757

The fix has been released in 4.3.0
Comment 7 Tyson Tan 2020-08-21 02:58:57 UTC
Thank you Dmitry! :D