Using the Transform tool on a large layer, the image on the layer often disappears while manipulating it, and it can't be made to reappear. Usually it's after scaling it up and clicking the visibility icon off and on. Sometimes the transparency is also glitchy while adjusting it when using the Transform tool. Reproducible: Sometimes Steps to Reproduce: 1. Create a 4000 x 4000 canvas 2. Create a new layer 3. Draw something large on the layer 4. Select the Transform tool and use it to scale the layer up 5. With the Transform tool still selected, turn the layer visibility off and on Actual Results: The image is gone even though the layer visibility is on, or transparency fails to work on the layer Expected Results: Image remains visible If this is an OpenGL issue, then I am becoming increasingly suspicious of my GPU (GeForce 9600 GT), since this other OpenGL related bug I reported has not yet been confirmed: https://bugs.kde.org/show_bug.cgi?id=331794
No, this isn't an opengl issue, I think. It must be some logic error that happens with the transform tool and layer visibility. I can also reproduce it on Intel gpu's.
Dmitry, could you take a look at this? I'm sure it's something simple, but it still happens.
*** Bug 343783 has been marked as a duplicate of this bug. ***
Created attachment 98235 [details] Redraw error example Example of redraw error when selecting with rectangle tool on a layer.
I sometimes get what is probably the same error when using the rectangle selection tool. The example attached resulted from: -copy image to new document. -resize document to 3508 px wide -create new layer, draw on it -use rectangle selection to select something on the new layer Most of the layer in the bacground turns transparent, as if some tiles fail to draw correctly.
Hm, I cannot reproduce it here. I think I have fixed this bug during the Krita 3.0 release cycle. Could you please check with Krita 3.0?
Repeating the steps in my original post, the problem appears resolved. I couldn't reproduce rebuilderster@gmail.com's error, although I'm not certain I'm replicating the steps in exactly the same way. 2.x often exhibits strange behaviour on a second open document - could it be related to this? I haven't tested 3.0 enough to encounter issues with a second document yet.
Thanks for checking!