It was recommended to me that I try Krita 3.0, specifically because of improvement to brush speed. I've downloaded and used build krita3-prealpha-b4bac8d and already have a small amount of feedback to provide.

The first thing I immediately noticed, which was very pleasing, was the fact that the program seemed faster to start and to create a new canvas.

I did a small painting test and found a couple of issues unfortunately; for comparison, I've been using 2.9.10 prior to trying the alpha.

• The brush cursor outline has a static colour; I managed to lose track of where the cursor was a few times because the colour didn't change dynamically when over certain colours in the canvas.
• Normally I use shift+pen tap+drag to change the size of a brush; Normally I can change it a little bit, and then change it a bit more, while still holding down shift, but in this version, even if I'm still holding down shift after having changed the size once, I'll need to let go of shift and do it again to change it again, otherwise the brush tries to paint the canvas. This is a bit difficult to explain through words. Note, this works fine with the mouse, just not the tablet's pen.
• Similar to the brush size changing issue, if I hold down space bar and tap to pan the canvas, it'll do it the first time, but I'll have to let go of the space bar and hold it again and tap again to pan an additional time, and so on. If I don't, the same happens in that the brush starts to paint the canvas instead of panning. Again, this works correctly with the mouse, but not the pen.
• A minor issue, but Krita's window doesn't start out maximised between sessions.

Point 3 is known as the focus issue, but it seems like it must have become worse in 3.0(it was briefly, for a full month, fixed in 2.8, but then we introduced the multiple documents and it broke again)

Point 1 seems like there's something funky going on with the shaders.

Point 2 seems a problem with events, I would need to have someone check this in 3.0 for linux or if it's a windows only thing.

Point 4 must be windows only.

Frankly though, I am surprised that these are the only issues you've found . I recommended the alpha mostly to make sure that you would benefit from the 3.0 speed-up work in the future, so that you wouldn't have to worry so hard about configuring Krita just right.

TheraHedwig wrote:Point 3 is known as the focus issue, but it seems like it must have become worse in 3.0(it was briefly, for a full month, fixed in 2.8, but then we introduced the multiple documents and it broke again)

Point 1 seems like there's something funky going on with the shaders.

Point 2 seems a problem with events, I would need to have someone check this in 3.0 for linux or if it's a windows only thing.

Point 4 must be windows only.

Frankly though, I am surprised that these are the only issues you've found . I recommended the alpha mostly to make sure that you would benefit from the 3.0 speed-up work in the future, so that you wouldn't have to worry so hard about configuring Krita just right.

Thanks for the reply; I only wanted to make the post to provide my personal experience with any issues I'd found so far in the version. Is there a bug tracker for Krita? Perhaps it would be better for me to report potential issues on a platform like that?

Is point 1 something I can resolve on my end? Though, I suppose I did notice some other things, but honestly anything that doesn't really impact my ability to paint is usually quickly forgotten about.

Edit: I did notice there was a change in the way my tablet seemed to be working with the alpha; no drivers (or other software of the like) have changed and no hardware has been changed either, since I was using 2.9.10. Previously I could put my pen close to the tablet to just move the cursor, without painting. On the alpha, I have to press (or tap) with the pen on the tablet, which may mean I paint without wanting to. However, after this has happened I can move the cursor as "normal" without having to be too close to the tablet (i.e. touching it), until I move the pen far away enough to not be sensed anymore, and so it begins anew. If I minimize Krita, it will always behave as normal, I've tested it consistently.

There is an exception to this, where if I leave the pen for a few seconds, at the normal "no touch" distance where it is "sensed", it will pick up on it and work as "normal".

That was a long explanation!

The bug tracker is at bugs.kde.org; but to be honest, we've got such a large amount of things to fix that new bug reports probably aren't necessary or helpful. What I would love, though, is if you'd keep a list of issues yourself and then on subsequent releases check whether stuff has been fixed. What hasn't been fixed by March should then be reported

boudewijn wrote:The bug tracker is at bugs.kde.org; but to be honest, we've got such a large amount of things to fix that new bug reports probably aren't necessary or helpful. What I would love, though, is if you'd keep a list of issues yourself and then on subsequent releases check whether stuff has been fixed. What hasn't been fixed by March should then be reported

Very well, thank you. I will do that. c:

That was the most pointless edit I've done.