This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Unable to use Tablet with Krita

Tags: None
(comma "," separated)
User avatar
TheLetterW
Registered Member
Posts
3
Karma
0
OS

Unable to use Tablet with Krita

Sat Jun 09, 2018 6:13 am
First of all, wanna say I love the program and I've been using it for years. Normally I'm able to fix my own issues that arrive with Wacom and its hijinx, but this is a whole new one for me.
Last week the program was running fine, registering the tablet correctly etc. I upgraded my graphics card and memory and now it's unable to register the fact I'm using a tablet? I've done wipes of the tablet drivers from my system, and I've tried downgrading to the version previous (an upgrade came out when my computer was being worked on.) I've also tried using older versions and clean installs of Krita (don't rule out the possibility, right?) and still no luck. A bit of poking around eventually led me to here.
I've uploaded a Debug log which if I'm reading it correctly, Krita is unable to properly communicate with the user32.dll...?
I'm not really tech savvy but when I ran Krita on another laptop I have (both running Windows 7 Home Premium) that line didn't come up in the Debug log and the tablet works fine.

Thanks in advance!
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS

Re: Unable to use Tablet with Krita

Sat Jun 09, 2018 11:16 am
Windows 7 doesn't provide the Windows 8 pointer api... And apparently the drivers for your tablet cannot be found.
User avatar
TheLetterW
Registered Member
Posts
3
Karma
0
OS

Re: Unable to use Tablet with Krita

Sat Jun 09, 2018 4:30 pm
That’s so bizarre... The tablet works with other programs such as Photoshop on the same computer. Is there something I missed when reinstalling the drivers...?
Any help is appreciated I’ve been trying to fix this for two days. >_<
User avatar
TheraHedwig
KDE Developer
Posts
1794
Karma
10
OS

Re: Unable to use Tablet with Krita

Sat Jun 09, 2018 5:13 pm
Krita should just take the drivers.

However, it does seem like it can find a context:

Code: Select all
krita.tabletlog: Opened tablet context  0x803  on window  0x120d46 changed packet queue size  50 -> 128

(...)

00000122   29.88699150   [4000] krita.tabletlog: # Getting current context data:   
00000123   29.88704491   [4000] krita.tabletlog: lc.lcName = 0x22bfc0   
00000124   29.88707733   [4000] krita.tabletlog: lc.lcDevice = 0   
00000125   29.88710976   [4000] krita.tabletlog: lc.lcInOrgX = 0   
00000126   29.88713837   [4000] krita.tabletlog: lc.lcInOrgY = 0   
00000127   29.88717079   [4000] krita.tabletlog: lc.lcInExtX = 44704   
00000128   29.88719940   [4000] krita.tabletlog: lc.lcInExtY = 27940   
00000129   29.88722992   [4000] krita.tabletlog: lc.lcOutOrgX = 0   
00000130   29.88725853   [4000] krita.tabletlog: lc.lcOutOrgY = 0   
00000131   29.88729095   [4000] krita.tabletlog: lc.lcOutExtX = 44704   
00000132   29.88732147   [4000] krita.tabletlog: lc.lcOutExtY = -27940   
00000133   29.88735390   [4000] krita.tabletlog: lc.lcSysOrgX = 0   
00000134   29.88738251   [4000] krita.tabletlog: lc.lcSysOrgY = 0   
00000135   29.88741112   [4000] krita.tabletlog: lc.lcSysExtX = 3600   
00000136   29.88744164   [4000] krita.tabletlog: lc.lcSysExtY = 1080   
00000137   29.88747597   [4000] krita.tabletlog: Qt Desktop Geometry QRect(0,0 3600x1080)   
00000138   29.88813400   [4000] qtDesktopRect = QRect(0,0 3600x1080)   
00000139   29.88816833   [4000] wintabDesktopRect = QRect(0,0 3600x1080)

(...)

00000277   160.96339417   [4000] krita.tabletlog: Failed to load function GetPointerPenInfo from user32.dll



Is it just pressure sensitivity that doesn't work? Or is even the tablet mode weird?

Maybe the winink autodetect just doesn't work really well?
User avatar
TheLetterW
Registered Member
Posts
3
Karma
0
OS

Re: Unable to use Tablet with Krita

Sat Jun 09, 2018 8:31 pm
The tablet maps fine and I can do things such as open new documents/menus, change brushes, etc.
However when a canvas is opened, the default brush will not lay strokes (doesn't even register a click) and once a different brush is selected, it just makes ugly not pressured lines. This is really the most baffling error I've ever had regarding my tablet.
(Screencap taken in older version when I was ruling out that possibility, but still does the same thing in newest version)

If there's anything else I can state to help with diagnosing this please let me know, I really don't want to have to switch off Krita as a program!

Edit: Some other poking around/things I left out
I use a dual monitor set up and generally have my tablet constrained to one monitor (less warped movements that way). Unsure if this is confusing either Krita or my drivers, or both as the resolution dialog on boot + shift tap wants to use a 3600 x 1080 monitor which lines up with both displays being mapped. Inputting the correct resolution in the manual options fixes the offset but disables the correct pen pressure input? Peculiar...
If the monitors are set to 1 display/repeated display, the automatic detection works fine. This was not a problem before a couple of days ago.

Edit (again): The problem seems to have been resolved by forcing the tablet's Screen Area to portion mode (despite it already being constrained to Monitor 1), and setting the monitor dimensions manually. Then I had to restart Krita and enter in those same values (which admittedly hadn't changed from what I had in there previously) into the manual option and suddenly the pressure's there. The two default options still think I have a 3600 px wide monitor though...
Strangely, putting the tablet back onto just a constrained monitor hasn't returned previous behaviour. Unsure of what doing this shook up but it's a solution I'll take!
I appreciate the replies in helping me figure this out! ;D

Hopefully this will help someone bungled up by dual monitor tomfoolery in the future.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]