Bug 377965 - Pen pressure does not work with Artisul tablet
Summary: Pen pressure does not work with Artisul tablet
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.1.2
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-23 00:11 UTC by Riley
Modified: 2017-03-28 12:08 UTC (History)
1 user (show)

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


Attachments
Log of using Krita with Artisul D10 Tablet (108.20 KB, text/plain)
2017-03-28 01:40 UTC, Riley
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Riley 2017-03-23 00:11:49 UTC
Krita does not seen to support Artisul tablets. My pen pressure does not work in Krita. I've tried updating my drivers, reinstalling, etc.
Comment 1 Halla Rempt 2017-03-23 07:44:16 UTC
Which tablet model exactly? https://docs.krita.org/List_of_Tablets_Supported lists four artisul tablet models, and none of them are reported to work or reported to be broken.

Given that artisul is uc-logic, I'm not surprised. Quite a few tablets are uc-logic based and whether they work or not varies from driver version to driver version. So... Which driver version exactly are you using?

Please also follow these instructions: https://docs.krita.org/KritaFAQ#Windows and make a tablet log and attach it to this bug.
Comment 2 Riley 2017-03-28 01:40:11 UTC
Created attachment 104770 [details]
Log of using Krita with Artisul D10 Tablet

Here is the log.
Comment 3 Riley 2017-03-28 01:44:14 UTC
(In reply to Riley from comment #2)
> Created attachment 104770 [details]
> Log of using Krita with Artisul D10 Tablet
> 
> Here is the log.

I am using the Artisul D10 with driver version 3.1.
Comment 4 Halla Rempt 2017-03-28 08:18:55 UTC
Hm... From the log it looks like you have a multimonitor setup. We get a tablet context, so we can open the wintab driver:

00000024	22.38659096	[28520] krita.tabletlog: # Getting current context data:	
00000025	22.38666916	[28520] krita.tabletlog: lc.lcName = 0x23bbc0	
00000026	22.38676453	[28520] krita.tabletlog: lc.lcDevice = 0	
00000027	22.38682938	[28520] krita.tabletlog: lc.lcInOrgX = 0	
00000028	22.38695145	[28520] krita.tabletlog: lc.lcInOrgY = 0	
00000029	22.38701820	[28520] krita.tabletlog: lc.lcInExtX = 21694	
00000030	22.38710785	[28520] krita.tabletlog: lc.lcInExtY = 13558	
00000031	22.38719177	[28520] krita.tabletlog: lc.lcOutOrgX = 0	
00000032	22.38725090	[28520] krita.tabletlog: lc.lcOutOrgY = 0	
00000033	22.38731766	[28520] krita.tabletlog: lc.lcOutExtX = 21694	
00000034	22.38735962	[28520] krita.tabletlog: lc.lcOutExtY = -13558	
00000035	22.38739967	[28520] krita.tabletlog: lc.lcSysOrgX = 3840	
00000036	22.38747025	[28520] krita.tabletlog: lc.lcSysOrgY = 0	
00000037	22.38751793	[28520] krita.tabletlog: lc.lcSysExtX = 1280	
00000038	22.38756180	[28520] krita.tabletlog: lc.lcSysExtY = 800	
00000039	22.38762093	[28520] krita.tabletlog: Qt Desktop Geometry QRect(0,0 5120x1080)	
00000040	22.38768196	[28520] qtDesktopRect = QRect(0,0 5120x1080)	
00000041	22.38772583	[28520] wintabDesktopRect = QRect(3840,0 1280x800)

But then the tablet doesn't send any tablet events to the Krita window, only mouse move events and proximity events. That must be a problem in the driver configuration, since it's the driver that is responsible for sending tablet events to our window. We just cannot do more from within Krita, I'm afraid.
Comment 5 Riley 2017-03-28 11:51:33 UTC
So my best bet is to hope that the next driver update will fix this?
Comment 6 Halla Rempt 2017-03-28 11:56:23 UTC
Yes -- or downgrade to an older driver, that sometimes helps people as well. Drivers for tablets are uniformly awful, even wacom's, but wacom's drivers are still the best... Everything that's based on uc-logic is a huge headache.
Comment 7 Riley 2017-03-28 12:08:03 UTC
Pen pressure works inside a little test area in the artisul software. Also I had moved the wintab drivers out in an attempt to fix the problem. Should I have them installed or will that cause a conflict?