Created attachment 107327 [details] Here you can see how the lines are connected if you change places quickly. Every time I change from drawing in one place (point A) and go to another (point B) Krita connects the strokes between these two places. This problem stops if you wait about 1.5-2 seconds in between which is pretty long for every stroke. I am using Ugee 1910b which may not be supported and this may be the cause of the problem.
This is a driver problem. Please see https://bugs.kde.org/show_bug.cgi?id=363284 . It is not a bug in Krita. *** This bug has been marked as a duplicate of bug 363284 ***
Created attachment 107332 [details] attachment-23917-0.html Are you sure about that? Because I have tried drawing in other programs (Photoshop and manga studio ) and it works perfectly fine. четверг, 17 августа 2017г., 15:16 +01:00 от Boudewijn Rempt bugzilla_noreply@kde.org : >https://bugs.kde.org/show_bug.cgi?id=383626 > >Boudewijn Rempt < boud@valdyas.org > changed: > > What |Removed |Added >---------------------------------------------------------------------------- > CC| |boud@valdyas.org > Resolution|--- |DUPLICATE > Status|UNCONFIRMED |RESOLVED > >--- Comment #1 from Boudewijn Rempt < boud@valdyas.org > --- >This is a driver problem. Please see >https://bugs.kde.org/show_bug.cgi?id=363284 . It is not a bug in Krita. > >*** This bug has been marked as a duplicate of bug 363284 *** > >-- >You are receiving this mail because: >You reported the bug.
Yes, I am sure. Application X works fine is no argument because the idiots who code these wintab drivers don't code to the specification; they tweak their "work" until it works with the set of applications they are told to make the driver work with. And until the most recent driver, that didn't include Krita. As you can see from the bug I linked to, if you get the right driver, the problem goes away. And that proves that it's not a bug in Krita.
Created attachment 107335 [details] attachment-28648-0.html Ok, thank you very much for explanation! четверг, 17 августа 2017г., 17:54 +01:00 от Boudewijn Rempt bugzilla_noreply@kde.org : >https://bugs.kde.org/show_bug.cgi?id=383626 > >--- Comment #3 from Boudewijn Rempt < boud@valdyas.org > --- >Yes, I am sure. Application X works fine is no argument because the idiots who >code these wintab drivers don't code to the specification; they tweak their >"work" until it works with the set of applications they are told to make the >driver work with. And until the most recent driver, that didn't include Krita. >As you can see from the bug I linked to, if you get the right driver, the >problem goes away. And that proves that it's not a bug in Krita. > >-- >You are receiving this mail because: >You reported the bug.