Pen pressure does not work on my computer in Krita 3.0
I have two devices, Cintiq Companion 2 with Win 8.1 and desktop with Win7. Krita3 works fine on Cintiq in computer mode, but pen pressure does not work on Win7 desktop (from both tablets). Krita 2.9 also works fine (see screenshot for more information and versions).

I have tried these steps to fix, but it does NOT help.

1) Delete profile:
C:\Users\me\AppData\Roaming\krita\
C:\Users\me\AppData\Local\krita\

2) reboot computer

3) turn off and plug out second tablet.

Screenshot with problem in Krita 3.0 and Krita 2.9 which work fine: http://imgur.com/spi6PSt

This issue is very important to me, because I can't use Krita with my new tablet (Cintiq 27QHD Touch). Nor 2.9, nor 3.0

Krita 2.9 have pen offset from actual pen position, on bottom edge (vertical offset) and right edge (horizontal offset), something about 5 pixels. This offset is not reproduced in Photoshop or MsPaint, so it is very unlikely to be device calibration problem. Krita 3.0 also does not have this problem with pen offset.


But krita 3.0 has this problem with missed pen pressure. So now I just can't use Krita at all with this tablet.

I have old krita 3.0 executable, built from source. It seems, that this old executable has same problem now, but worked fine in the past, when it was just buit.

I can edit and recompile any source file. Not sure I want to use fresh version from git, it will require rebuild again, and likely requires CMake-files regeneration (and maybe requires rebuild of dependencies, which scares me most), it may require unexpected time, it has taken two days last time to setup environment and fix all problems. So I prefer to debug this old version.

But I don't know where it better to start to debug pressure problem. At least, what is best way to check - this is initialization-time problem, or device input data reading problem, or interpretation of this data?

Also, maybe there is some log file, which can report about non-detected pressure, but I don't know where to find it.

Hello dobrokotov,

I am not a Krita developer...

Have you tried to report this issue on the Krita bug-tracking system, since it is the right place to do so?

Today, Dmitry has fixed a bug concerning pressure sensivity not working on Krita 3. Compared to Krita 2.9.x It looks like this bug is due to a QT regression related to the new version ( 5.6 ) which is deployed with Krita 3 (Krita 2.9 used QT 4.x instead).
See here for more details regarding this particular bug:
https://bugs.kde.org/show_bug.cgi?id=359642

AFAIK, especially on Linux, it is possible to debug "easily" any Tablet problem in order to send the log to the Krita developers to allow them to take a look (again, through the Kde bug tracker...).

I am not sure, is this bug of Krita, or is it bug of my system.

Anyway, thanks for the ticket link. It is unlikely that it solved my problem, because I have Wacom, not uc-logic. And same executable which worked earlier, with one-tablet non-cintiq configuration.

Anyway, the ticket link is VERY usefull. this I have read the ticket, I have googled the "tablet-log krita" query, and have found "DebugView" for Windows. And now I have the following line in the log:

http://dobrokot.ru/pics/i2016-05-18__12-45-30_337kb.png

[1156] Unable to set queue size on tablet. The tablet will not work.

If an older version of Krita, that used to not have this problem, has it now, it's pretty sure that this is a problem of your system.

krita-3.0-RC-1-master-6f75b0f-x64.zip (64 bits) - same problem.
http://dobrokot.ru/pics/i2016-05-22__06-45-25_754kb.jpg
debug output from Dbgview.exe - http://pastebin.com/bMUmhr5G

Krita3 stable release 3.0 - same problem
Screenshot: http://dobrokot.ru/pics/i2016-06-02__15-49-18_830kb.jpg
DbgView output: http://dobrokot.ru/pics/i2016-06-02__15-47-29_295kb.png

version 3.0.1.1 - same problem, no pen pressure (it is always 100%). No problem in other sofware, and no problem in old Krita 2.9
vesta.informatik.rwth-aachen.de/ftp/pub/mirror/kde/stable/krita/3.0.1.1/krita-3.0.1.1-x64.zip

Screenshot of DbgView.exe: http://imgur.com/delete/JHLzq0oUAfl39ED

I got this problem after installing the Windows 10 update on my Surface 3, updates like this can break the drivers, from what I've been told.