Bug 376003

Summary: Tablet Support for Wacom Cintiq 13HD does not recognize pressure sensitivity.
Product: [Applications] krita Reporter: jackmontegue21
Component: Tablets (tablet issues are only very rarely bugs in Krita!)Assignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: major CC: halla
Priority: NOR    
Version: 3.1.2   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Attachments: Debug Log of Krita while problem persists.

Description jackmontegue21 2017-02-04 14:07:33 UTC
Created attachment 103822 [details]
Debug Log of Krita while problem persists.

Krita does not recognize pen pressure on the Wacom Cintiq 13HD.

Instead lines are thick as if drawing with a mouse. The cursor follows the pen like normal, there is no offset. 

Picking up the pen and placing it back down on the canvas causes the pen to not be registered. 

Moving the window to the main monitor (the laptop screen) gives Krita the ability to use pen pressure again, but the canvas has a section where it jumps, not being registered. The rest of the window has tracking as normal. Only the canvas has the issue.

Pen pressure is also confirmed to work in other applications such as Paint Tool Sai and Photoshop. 

Upon opening Krita, when the pen is first detected a popup appears claiming:
"The driver for your drawing tablet and Windows do not agree on the size of your screen your tablet is connected to." Wintab seems to register 1920x1080 (the actual screen size) while Qt registers 3840x1080, which is completely bizarre. If there is some way to manually change this in the Qt files, I would be happy to hear it. 

My own personal troubleshooting is as follows:
Like I said before, I checked to see if it was a monitor problem and used Krita on my main monitor. Pen pressure returned, but there was a strange area of the canvas not being used. When drawing it was normal, but when just hovering over the screen the mouse would jump over it.

Since it looked like a monitor problem, I changed the Wacom Cintiq to be the computers main monitor and opened Krita. Pen pressure worked, but there was an offset by about 5-6 cm. 

I have restarted the computer and reopened Krita. Problem persists. 

I have downloaded the latest drivers for the Cintiq. Problem persists.

I only have versions 3.0 and 3.1.2 to work with, and the problem is active in both versions. I cannot find any older versions to test on.

I have included an attachment with the Debug view while using Krita and attempting to use pen pressure. 



If there is a way to manually change some files or edit something on my machine, that would be the best option probably. 
I am running:

Windows 10 64bit
i7-4720
GTX 960m
7.9 GB RAM
Graphics drivers v. 369.09
Tablet drivers v. 6.3.20-5
Comment 1 jackmontegue21 2017-02-04 14:22:23 UTC
UPDATE:

I have just calculated 3840 and realized that it's 1920 x 2. I'm really dumb.

I have been using my monitors (the laptop and Cintiq) in extended display mode so Qt was picking that up. 

I just switched it to duplicate display, opened Krita, and was able to confirm that pressure sensitivity was working. 

THEN, I switched settings back to extended and opened Krita again.

This time, however, no popup appeared asking for screen resolution and after testing, pressure sensitivity was working once again. 

I have no idea. This is just weird.
Comment 2 Halla Rempt 2017-02-04 15:48:35 UTC
It's a settings problem I'm afraid. I've seen the same thing happening with my own cintiq hybrid companion now and then, which is setup as the second monitor in my case, no display duplication. Sometimes rebooting helps, sometimes the wacom settings app is confused about which monitor it is. As you can see from the tablet log, there are no stylus events coming in, only synthesized mouse events.

I know that some other applications might work with this setup, but tbh, the photoshop forums and reddits are full of people telling Adobe people that Photoshop has a bug "because Krita works".

In the end, it's the wacom driver that has the bug...
Comment 3 Halla Rempt 2017-03-27 13:51:43 UTC
There's nothing that I can do with this report, sorry. It's not something we can do anything about from within Krita.