Bug 368094 - [PARBLO A610] pen pressure doesn't work
Summary: [PARBLO A610] pen pressure doesn't work
Status: RESOLVED UPSTREAM
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (other bugs)
Version First Reported In: 3.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-01 09:48 UTC by Dmitry
Modified: 2017-11-25 09:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry 2016-09-01 09:48:23 UTC
My graphic tablet is PARBLO A610. 
I use pen to launch program and create new file.
And I can use the pen to drawing but it's pressure doesn't works. I tried several brushes and result was the same.

Reproducible: Always

Steps to Reproduce:
1. Launch the program and create new file.
2. Select the brush that has pressure option (e.g. basic_tip_dafault).
2. Start drawing with a tablet pen performing a different pressure.

Actual Results:  
Solid lines, regardless of the pressure.

Expected Results:  
The width and/or transparency of the drawn line changes depending on the pen pressure.

Krita 2.9.11 has the same bug. But I can avoid it when launch the program and create/open file by using tablet pen.
Comment 1 Halla Rempt 2016-09-01 11:02:19 UTC
Hi Dmitry,

Unfortunately we don't have access to this tablet brand so it's unlikely we will be able to support it. The smaller brands of tablets usually have a very bad quality driver on Windows, where the problem is that the driver was not written to conform to the specification but to what Photoshop expects.
Comment 2 Halla Rempt 2017-11-25 09:04:02 UTC
Hi,

You might be able to get your tablet to work by enabling the Windows Pointer API in the tablet settings of Krita, but we cannot support tablets of this brand. It's also quite likely that it's just a broken wintab driver.