Bug 361515 - [UGEE] Brush Cursor Doesn't Follow Ugee Tablet Pen on Hover
Summary: [UGEE] Brush Cursor Doesn't Follow Ugee Tablet Pen on Hover
Status: RESOLVED DUPLICATE of bug 363808
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 2.9.11
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL: https://gyazo.com/1b60bf1acb0f450a3df...
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-08 06:04 UTC by Bee
Modified: 2016-08-08 12:08 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bee 2016-04-08 06:04:24 UTC
When I use the brush tool the outline of the brush doesn't follow the cursor when the pen is hovered. When I draw, it works fine and follows the pen but once it's lifted a little bit away it stops following it. It still follows it in the menu, but not in the active canvas area. Some other tools follow it- like the calligraphy brush shows a cross hair, and the line tool shows a little cross hair with a line that follows- but the actual brush shape just stays put. Pressure sensitivity is fine, and everything else about it is working perfectly in other programs.

Reproducible: Always

Steps to Reproduce:
1. Have a Ugee UG-2150 tablet
2. Tap down with brush tool in canvas area (anywhere in the canvas or in the grey outside of it- but not in the actual menus) and watch how it follows.
3.  Lift off slightly, enough to stop drawing but not enough for it to stop sensing the pen is near.

Actual Results:  
Brush shape cursor stops following pen.

Expected Results:  
The brush shape cursor should have continued to follow the pen.

I just re-downloaded the tablet driver for this because I noticed the people at Ugee pushed an update last month, and it was being screwy in other really annoying ways. (I couldn't use it in PS, and it started glitching out in Krita, but both of those have been resolved with the new driver!) 

Also I'm on Windows 7.
Comment 1 Halla Rempt 2016-04-08 06:11:07 UTC
Hi,

Thanks for your report. Could you also check with the latest windows alpha build? You can download it here: http://files.kde.org/krita/3/windows/krita-2.99.89.zip

Since we don't have an ugee tablet we cannot test ourselves :-(
Comment 2 Bee 2016-05-18 22:57:56 UTC
Sorry for the delay, but that unfortunately didn't fix it. :( in fact, it made it slightly worse- now it'll draw a faint line in between touches. So if I draw a squiggle, lift the pen and press it elsewhere, a faint line will draw between the two. :C
Comment 3 Bee 2016-05-18 23:04:54 UTC
Sorry to comment again; I just wanted to let you know I tried to gif the new problem but it won't let me draw while using gyazo to record. To be a little more specific, the line thickness and opacity is effected by how hard I'm pushing on my pen so it's still reading that. It just draws from where I left the pen last to the new mark in a straight line.
Comment 4 Dmitry 2016-05-22 13:03:22 UTC
Hi! I'm also a ugee 2150 owner (and my cursor also doesn't follow). May i ask you if faint lines between strokes are appearing in krita 2.9 or 3.0 (or both). I'm asking this because krita draws lines between my strokes in 3.0 version.
Comment 5 james 2016-06-01 23:16:42 UTC
I am having the same issues with my artist 22hd XP-pen tablet, including Dmitry's issue of seeing connecting lines between strokes in Krita 3.0.
Comment 6 Halla Rempt 2016-06-17 09:27:11 UTC
That's a different issue, though. It sounds like some tablet drivers don't send the proximity leave event correctly.

*** This bug has been marked as a duplicate of bug 363808 ***
Comment 7 gclarcy 2016-08-08 12:08:13 UTC
Hi I am also having the same issue on mac el capitan, wacom intuos pen tablet. cursor doesnt follow the pen when hovered, only follows when you actually put the pen down on the tablet. this makes it difficult to see where I am actually drawing on the canvas. Is there a fix on this yet?