Bug 404681

Summary:	Krita does not draw the whole picture
Product:	[Applications] krita	Reporter:	dieter.de.moitie
Component:	Tools/Transform	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	ahab.greybeard, dieter.de.moitie, ghevan
Priority:	NOR
Version First Reported In:	4.1.7
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	The original kra file Screenshot after opening issue.kra Screenshot after disabling and re-enabling the layers workaround of issue by clone transform Simple generated vector shapes: no issue Hand drawn raster shapes: an issue

Description dieter.de.moitie 2019-02-22 06:18:07 UTC

Created attachment 118265 [details]
The original kra file

SUMMARY
I have drawn a picture on a vector layer, with a colorize mask. Those two layers are inside a group, which has a transform mask.
Whenever I open the drawing, it only shows part of it.

This is troublesome because I have more layers in my final drawing and it often happens that I only see parts of the drawing. Also, if I export this, it will export it as shown on my screen.

STEPS TO REPRODUCE
1. Open attached issue.kra in Krita, you will see that only part of the image is drawn (screenshot krita1.png attached)
2. Disable the transform mask, disable the vector layer, and re-enable them, the picture is now fully shown (screenshot krita2.png attached)

OBSERVED RESULT
Only part of the picture is drawn

EXPECTED RESULT
The picture to be drawn completely

WORKAROUND
It seems that creating a clone layer and do the transform on the clone layer does not have this issue.

SOFTWARE/OS VERSIONS
Issue seen on both Windows 10 and Fedora 29 (GNOME + Xorg) machine

Krita
Version: 4.1.7.101

Qt
Version (compiled): 5.11.3
Version (loaded): 5.11.3

OS Information
Build ABI: x86_64-little_endian-lp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: linux
Kernel Version: 4.20.6-200.fc29.x86_64
Pretty Productname: Fedora 29 (Workstation Edition)
Product Type: fedora
Product Version: 29

ADDITIONAL INFORMATION
This has also been discussed in this forum thread: https://forum.kde.org/viewtopic.php?t=157183

Comment 1 dieter.de.moitie 2019-02-22 06:18:42 UTC

Created attachment 118266 [details]
Screenshot after opening issue.kra

Comment 2 dieter.de.moitie 2019-02-22 06:19:15 UTC

Created attachment 118267 [details]
Screenshot after disabling and re-enabling the layers

Comment 3 Ahab Greybeard 2019-02-22 07:10:49 UTC

Created attachment 118271 [details]
workaround of issue by clone transform

Comment 4 Ahab Greybeard 2019-02-22 07:15:22 UTC

I confirm that this issue also happens in the 4.2.0-pre-alpha (git 7dc0c43) appimage.

It does not happen if the vector image is made of three ellipses made with the ellipse drawing tool (simple smooth shapes) but it does happen if a raster drawing is made by hand (rough irregular shapes).

Comment 5 Ahab Greybeard 2019-02-22 07:17:22 UTC

Created attachment 118272 [details]
Simple generated vector shapes: no issue

Comment 6 Ahab Greybeard 2019-02-22 07:18:11 UTC

Created attachment 118273 [details]
Hand drawn raster shapes: an issue

Comment 7 Ahab Greybeard 2019-02-22 12:18:20 UTC

Addendum:

The image attached in Comment 5 does not have a problem because the transform used is a 'simple' skew + rotation. If the transform is a rescale + move then that image does have a problem on opening.
Similarly, if the image attached in Comment 6 has its transform changed from rescale + move to skew + rotation, then it also does not have the problem.

Also, if the transform layer is placed above the colorise mask so that it applies to the drawing (not the group) then it will open with no problems but turning off the transform layers will show the problem until the Colourise Mask is toggled.

Furthermore, If the transform layer is placed below the colourise mask (still applied to the drawing) then the rendered image shows separation of the transformed drawing and the colourisation of the original drawing. It would be useful to know about any rules or guidelines for stacking layers masks in this manner, in terms of rendering priority/order and any combinations that should not be used.

Comment 8 vanyossi 2020-01-13 16:01:03 UTC

this bug cannot be reproduced anymore in 4.2.8, anyone else can confirm?

Setting to needsinfo fixed

Comment 9 Ahab Greybeard 2020-01-13 18:52:52 UTC

I've opened all the attached files using the 4.2.8 appimage and had none of the problems that were present in 4.1.7.