Bug 388311 - I have a P50S stylus and a ugee2150HD and the krita cant seem to track the stylus
Summary: I have a P50S stylus and a ugee2150HD and the krita cant seem to track the st...
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 3.3.1
Platform: Microsoft Windows Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-28 22:40 UTC by shadowdragon1200
Modified: 2017-12-29 09:28 UTC (History)
1 user (show)

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


Attachments
a debug log of the problem (16.97 KB, text/plain)
2017-12-28 22:40 UTC, shadowdragon1200
Details

Note You need to log in before you can comment on or make changes to this bug.
Description shadowdragon1200 2017-12-28 22:40:17 UTC
Created attachment 109565 [details]
a debug log of the problem

while it works fine in autodesk sketchbook, it will write but the strokes have to be exaggerated, and it acts almost as if it treats the stylus as a mouse because if I draw small circles it treats it as if I held it in place and pulls up the on page advanced color settings and stroke styles rather than actually drawing anything.

I searched through the settings of the program to see if there was something to activate like some sort of stylus specific tracking setting however found nothing and after looking through the log it seems that this tablet has been confirmed as broken on the windows platform with this program but I figured I would report the bug to at least bring extra awareness to what seems a minor bug.
Comment 1 Halla Rempt 2017-12-28 22:43:01 UTC
Thanks for adding a log. The log says:

00000078	0.30225435	[6840] "Could not load wintab32 dll: Cannot load library wintab32: The specified module could not be found."	

This means that for your tablet there is no wintab driver installed. Please update to the latest version of Krita, 3.3.2, and enable Windows Pointer API in Krita's Settings/Configure Krita dialog, the tablet page. That might solve your issue, or you might be able to find and install a wintab driver for your tablet.
Comment 2 shadowdragon1200 2017-12-28 23:17:55 UTC
First off I'm going to start by thanking you for replying as quickly as you have

however: I mislabeled my krita as 3.3.1 while it is 3.3.2 my fault

         The wintab was what was used on the settings in the first place and I just updated my drivers for my monitor today. However there was a secondary option (windows 8 + pointer imput (depends on windows ink) (experimental)) here that after you pointed out this setting being the problem I tried swapping to and it resolved the issue


I am currently working with wintab32.dll and will see if it further amends the problem but I did want to post that the win 8 experimental seems to have the capacity to resolve the issue to a workable state.

thank you
Comment 3 Halla Rempt 2017-12-29 09:28:46 UTC
Okay, thanks for the extra information.