bug is fixed.

The referenced bug is already closed, closing this.

This is for the QUICK brush engine specifically.

Okay, so this one seems like it is related to the multithreaded brush bugs, as it only happens with pixel brushes:

I think all the multithreaded brush bugs I know about are fixed now! :)

Wraparound bug is confirmed

In T7309#118421, @alvinhochun wrote:

When using the "deevad 2c flat" brush, it doesn't seem to be reducing the update rate for a faster stroke?

In T7309#117880, @alvinhochun wrote:

Some opinions on update rate: https://bugs.kde.org/show_bug.cgi?id=386767

In T7309#116882, @scottpetrovic wrote:

I noticed on linux the pixel brushes seem to stop working when the pixel size gets under 1 or 2 pixels. If it is larger than that they are ok.

When using the "deevad 2c flat" brush, it doesn't seem to be reducing the update rate for a faster stroke? On the other hand the update rate of "deevad 2e big brush" is horribly low...

Drawing outside the main canvas in wrap around mode is broken with the pixel engine, getting disconnected line segments.

Some opinions on update rate: https://bugs.kde.org/show_bug.cgi?id=386767

I experiencing crashes with textured brushes. Noticed on brush like here https://phabricator.kde.org/T7052 but it happens with other too. It need a couple minutes of painting to get the crush, simply brushes seems to be more stable but I got crashes with them too. Even just hard round with texture can crash.

A regression with brushes with really big textures:

So here are what I have:

I noticed on linux the pixel brushes seem to stop working when the pixel size gets under 1 or 2 pixels. If it is larger than that they are ok.

Moar bugs:

@dkazakov - I was doing some painting this morning on my Surface pro and got this crash. Not sure if it is related to your work, but probably needs to be fixed.. https://bugs.kde.org/show_bug.cgi?id=386523

In T7309#116546, @woltherav wrote:

Use fuzzy stroke with the hue or value options in the pixel brush: it'll seem as if it is working on a few dabs before generating a new random value.

Use fuzzy stroke with the hue or value options in the pixel brush: it'll seem as if it is working on a few dabs before generating a new random value.

In T7309#115689, @woltherav wrote:

Ah.... I noticed that in the multithreaded branch, the "fuzzy stroke" sensor is a bit broken...

Ah.... I noticed that in the multithreaded branch, the "fuzzy stroke" sensor is a bit broken...

I tested the branch out on my Ubuntu 16.10 box. I tested various things including painting with different engines, different sizes, and instant preview.

The bugs should now be fixd in https://commits.kde.org/krita/02461e0852a18ae312f1c5cfc2758b838d550193

I feel auto fps make it pretty smooth on low-mid brush size but it becomes low fps too early.
Brush - Block_textured_1, low pressure (because it high pressure makes spacing lower).
Size 200px - 20 fps
260px - around 15 fps
365 - very 11 fps but brush still very fast
506 - still pretty fast
650 - it noticeable slower

Full video clip:

Issue 2: Updates happen in rectangles

Issue 1: Too big (stepped) updates

The bug is already present in 77fdc851205b574ab50381202a98f221ba9093b0 from 2017-01-05 :(

When things like that happens, there might be two reasons: