While drawing quick, a lot of the strokes happens in wrong place. eg I draw quick 5 centimeter long strokes on the same place and suddenly a random stroke hapens about 5 centimeters away from the place i draw them(on the same imaginative line). also if i stop drawing exactly when the wrong stroke occurs, the brush indicator maintains the deflection until i touch the stylus on tablet again. this never happens in other software (i tested on gimp and mypaint) !! this also happens in windows 7 with the original tablet diver !! (in ubuntu i use the digimend huion driver) Reproducible: Always Steps to Reproduce: 1.open any file in krita 2.draw quick lines with the stylus 3.strokes Actual Results: wrong mapped strokes here are the tablet log when the bug occured, and the command outputs https://paste.kde.org/pwkyz1kui (tablet log) https://paste.kde.org/puabumjwf (lsmod output) https://paste.kde.org/pcb29l5cp (xinput output) https://paste.kde.org/pux1tlpjc (xinput list-props output)
Created attachment 95647 [details] Tablet log reuploaded Hey dmitri, thanks for going through the bother. I am reuploading the tablet log as an attachment so we don't lose the information(paste only pastes up to a week or so)
Hi, Dmitry! Do I understand it right that the offset was bigger than 7-8 pixels? And could you tell me, did you use any assistants or smoothing during these tests?
Hi, again. Yes, the offset depends on how long the previous stroke was. The longer the lines the more distant the offset. it happens usually on bigger files, and a lot more when firefox is open. my pc is not great but this happens only in krita unfortunately. Even with no assistants or smoothing it keeps doing it. it happens also when autosaving
i attached an image in description in DA to demonstrate the problem
HUION H610 tablet
Does this still happen with Krita 3.0?
yeah! the problem is solved. after the krita 3 update the bug no longer exists. everything works fine. thanks for everything!
(In reply to Boudewijn Rempt from comment #6) > Does this still happen with Krita 3.0? the problem is solved. after the krita 3 update the bug no longer exists. everything works fine. thanks for everything!
Yay!