Created attachment 108339 [details] Log using DebugView I have followed your instructions to run a DebugView and to recreate the problem. When I open Krita there is no problem, I can move about the UI without any jumps, but as soon as I open a file to create a new painting or to edit an existing one the brush jumps about, sometimes producing a double cursor as though it is existing in two places at once. If I lift the pen off the tablet and put in a different place it acts like a "Relative" control and the jumps occur in different areas. I have tried this on both "Relative" and "Absolute" and the issue exists on both. If I am drawing a line, however, and go beyond the point where the cursor would normally jump, as long as I do not lift the pen off the tablet it will continue into the correct area, then as soon as I lift the pen, ending the line, it jumps again. I think these are all the issues I have come across. If there are any further tests you would like me to do, please let me know. Many Thanks.
You haven't got any tablet logs in your log so there's not really much info that can help. You need to press Ctrl + Shift + T to get them (see https://docs.krita.org/KritaFAQ#What_if_your_tablet_is_not_recognized_by_Krita.3F ) Krita does not support any "relative" modes for tablets. In fact I believe no other programs support "relative" modes without some special config. So you can disregard the "relative" mode. However, it is supposed to work in "absolute" mode. It's a bit unclear what exact behaviour you are getting, so I would like to request a video demonstrating the issue.
Hi, The tablet log doesn't actually include any tablet events, I'm afraid. But on the other hand, this doesn't sound like a bug in Krita. It sounds like an issue with the Ugee drivers (which are awful). You probably should try to find updated drivers, or if you've got the most recent version, older drivers. Try to purge the Ugee configuration completely, as well -- I have no idea how to do that, since I don't have an Ugee tablet, though. Note that wintab tablet drivers keep settings per-application, so "but it works with application X" isn't relevant. Worse, these driver programmers often only test with a limited number of applications, hacking around until those applications work, without paying any attention to the wintab specification. But the upshot is, we cannot do anything about it. You could try to enable the Windows 8 Pointer API in Krita, since that bypasses the wintab driver, but I don't know whether Ugee sends events using that API as well.