First beta of Krita 4.4.2 - Help in testing needed!

I am using 4.4.1.

If you scroll up the News section, do you see it on top? (Don’t ask why scroll up if here is nothing to scroll :smiley: I’ve just discovered an interesting bug there myself… :stuck_out_tongue: ) If not, then it looks like it was caused by the fact that the recent News about the beta version was classified as ā€œOfficial Releaseā€ instead of ā€œDevelopment Releaseā€ so your Krita thought it needs updating, but it shouldn’t think that anymore because it was fixed on the blog already.

@tiar Great. Thank you. it was just a small thing. :slight_smile:
Cheers
alex

The work of the new ā€œMesh transformationā€ with Bezier guides is amazing!

Hello,
Im currently using the beta, it works wonders! I’m painting on a 4k file, that is 2gb, it has vectors, and layer effects and I have near 0 lag with brushes, zooming in and out work fantastic, the vector tools also have no slow down, and layer effects while they do take some time to show the changes for the most part work as fast as expected from a file this big, I do have some bugs from the tag and brush manager system but I read that that is getting addressed as soon as possible with the 5.0 release (I wouldn’t mind testing the current new manager even if its not polished), this is the only thing that used to make not want to switch to Krita, as I was worried I would loose brushes unexpectedly, however the tag bugs has not deleted my brushes like so, and I think I got the hang of the kinks it has.

I’m working with a nvidia 1080gtx and a i7 10700, this hardware works great with Krita.

I used to work with Photoshop for years now, but the current version of it cant handle a 4k file like this one, the vector systems are too slow, specially if I have any layer effects on the .psd, and turning a layer on and off to check a change also take ages, I’m so very happy Krita’s development is this advanced, its so nice to work on a file this big and have a responsive application, the switch will be a bit hard (learning curve and all as well as migrating some brushes), but so far its been worth it.

If I find any bugs I will report them.

Thank you for making this great application.

2 Likes

I think I found a bug… I was using the clone tool, it works just fine with one layer as the source of the cloned image, by pressing ctrl on the source you want, then I looked around google and I found that to take a source that takes into account all the visible layer stack, the tool needs you to press ctrl+alt then click on the canvas, I did that, but the engine is not picking up a source, meaning the clone tool draws nothing.

Since it works with a single layer I can just copy merge a section of the canvas on a new layer and use that as the cloning source, still it would be nice to have that working, if I’m doing something wrong and that’s the reason this is not working, please let me know, cheers!

I think that is a nice feature request, and it would need a separate topic on a forum - this post is more for finding the regressions - bugs that got introduced between 4.4.1 and 4.4.2, while this is technically not a bug :slight_smile:

Clone brush uses a whole different brush engine, and using ctrl is a different action of picking the origin point, not the color. ctrl + alt according to info in its settings does nothing, as it picks the source from a previously selected layer.

To get what you want, you will have to go to brush editor (F5) with clone brush selected, Pick painting mode and select clone from all visible layers. You can switch that back and forth, or save it as a different clone tool. But to be able to toggle it by pressing some key combination makes some sense for me, though, I’m not using this tool too often.

3 Likes

How do you achieve the images for Ctrl or Alt keys? Thanks :blush:

It’s just what a description on a tool said. As I tested it, it doesn’t do anything, so maybe there is a bug here after all :slight_smile: But regardless, this topic is not really meant for this type of conversation, and it should be moved somewhere else.

Oh! I see what you mean, some how I read the docs of Krita and I miss understood the use of ctrl+alt, and also I was not able to find the option to make the clone tool be able to scan all the layer stack before I read your reply, thank you very much for the clarification, :slight_smile: I wont be writing about this on this thread any more, I thought it was a bug because I’m very new to the application, cheers!

1 Like

Ok I think I did found a bug this time around, on the Edit Shapes Tool.
In Kirta4.1 (the officially released version) if I create a path and then just grab a vector line
I can adjust its shape without grabbing the individual nodes, like in this video:

But on the 4.4.2 beta1 if I create a path and try to do so, I can only directly change the shape of
a curve on some of the line segments, I don’t know why on some segments it works an on others
does not, but on Kirta 4.1 I can consistently directly alter any line segment by just dragging,
I would image this version should work the same way, so Im 99% sure this is off.
But I’m wrong I apologize for the inconvenience.
Cheers!

There is a change in behaviour going from 4.4.1 to the 4.4.2-beta1.

In 4.4.1, as you say, you can grab and drag a line segment, which then displays a dashed line overlay; this is the case for previous versions as well.

In 4.4.2-beta1, clicking the line segment causes a dashed line to appear and also the line control handles going to each node. Only the control handles can be grab-dragged to alter the line, not the dashed line segment itself.
There are other changes in the exact details of the overall UI appearance and sequence of overlay changes when doing this action.

It may be that the UI has had some deliberate changes in this area.
I suggest that you wait for comment from a developer who knows about this area.
It’s not technically a ā€˜fault’ because you can still edit the line segment with no problems.

Hi, @Renderluz!

Thank you for the report! I have just fixed that in the development branch. The fix should appear in the tomorrow nightly builds :slight_smile:

1 Like

I’m hoping that this is still being watched.
I tried out importing brush bundles on Android (Samsung Galaxy Tab S7 running Android 11) and when I do so, I get checksum error messages.

I asked about it on this thread: Krita For Android Beta; Feedback and Bugs and included a screenshot.

(I ended up giving up on it and deleted Krita and then reinstalled and haven’t tried importing any brushes since).

A post was split to a new topic: Colors are inverted