Created attachment 102520 [details] hanvon tablet log The summary isn't quite correct. Krita recognizes my pen movements, as in the cursor moves when I move my pen. But when I touch the pen to the tablet and move it around, nothing happens. No drawing occurs and the blank canvas stays a blank canvas. Thanks for any help you could share.
I forgot to add: Nothing happens too even when I click on the buttons on my pen and move my pen while touching the tablet... no drawing occurs. Thanks Krita team for a great product. I barely experimented with it, but I can already tell you guys are doing a great job with it.
Hm, from your log, I see that you're on Windows, not Linux. Krita sees the wintab driver and gets a context: 00000049 19.04427528 [2536] krita.tabletlog: # Getting current context data: 00000050 19.04435921 [2536] krita.tabletlog: lc.lcName = 0x22d7d8 00000051 19.04441643 [2536] krita.tabletlog: lc.lcDevice = 0 00000052 19.04446983 [2536] krita.tabletlog: lc.lcInOrgX = 0 00000053 19.04451561 [2536] krita.tabletlog: lc.lcInOrgY = 0 00000054 19.04456520 [2536] krita.tabletlog: lc.lcInExtX = 10206 00000055 19.04461288 [2536] krita.tabletlog: lc.lcInExtY = 7422 00000056 19.04466057 [2536] krita.tabletlog: lc.lcOutOrgX = 0 00000057 19.04470634 [2536] krita.tabletlog: lc.lcOutOrgY = 0 00000058 19.04475403 [2536] krita.tabletlog: lc.lcOutExtX = 10206 00000059 19.04480743 [2536] krita.tabletlog: lc.lcOutExtY = -7422 00000060 19.04485321 [2536] krita.tabletlog: lc.lcSysOrgX = 0 00000061 19.04490471 [2536] krita.tabletlog: lc.lcSysOrgY = 0 00000062 19.04495239 [2536] krita.tabletlog: lc.lcSysExtX = 1280 00000063 19.04500008 [2536] krita.tabletlog: lc.lcSysExtY = 1024 00000064 19.04505539 [2536] krita.tabletlog: Qt Desktop Geometry QRect(0,0 1280x1024) 00000065 19.04511070 [2536] qtDesktopRect = QRect(0,0 1280x1024) 00000066 19.04516220 [2536] wintabDesktopRect = QRect(0,0 1280x1024) But no tablet events are received at all... Could you also try with the latest beta, which has even more tablet debug output? But tbh, I'm afraid that it's still going to be hard to register your stylus if the driver doesn't send tablet events.
I'll try the latest beta. So total noob question though: what exactly are wintab drivers? I know it's a microsoft driver for surface pros but why is it needed for my non surface pro/non tablet desktop when Hanvon comes with it's own drivers? So is the line of communication like this? tablet -> hanvon tablet driver -> wintab -> krita as oppose to the way I traditionally understand it; tablet -> hanvon tablet driver -> krita ?
Mr Rempt, I tried going to the website to download the latest beta, but the links are dead. I even tried the source code links, but the links only lead me to the latest stable version. Any help you can give me would be great. Thanks.
Created attachment 102561 [details] tablet log I downloaded the latest beta and installed it. I opened up Krita, created a new document, made a mark with my mouse, then made a mark with my tablet, then rotated the canvas, then made a mark with my mouse, and then made another mark with my tablet before closing it. Whenever I made a mark with my mouse, it would draw on canvas. When I do the same thing with my tablet, nothing happens. :( Is my tablet a lost cause because it's old and have no new drivers?
Oh yah, I forgot to say, I also uploaded the latest log.
There are two tablet protocols: wintab and windows ink. Almost every tablet (wacom, huion, yiynova, uclogic, hanvon) come with wintab drivers. There can only be one wintab driver on a given windows installation. Krita only understands wintab, which is the reason that you also need a wintab driver for Surface Pro, which comes with an n-trig pen and which uses windows ink by default. The hanvon tablet driver is a wintab driver: will install a wintab32.dll somewhere. And from the log we can see that there is a wintab driver, otherwise we couldn't open a context. What isn't in the log is a record of you trying to draw a stroke. Did you close Krita directly after starting it?
Sorry, I didn't read correctly, you said you did -- but even mouse events should show up in the log if you enabled tablet logging with ctrl-shift-t. There is no line saying krita.tabletlog: vvvvvvvvvvvvvvvvvvvvvvv START TABLET EVENT LOG vvvvvvvvvvvvvvvvvvvvvvv So we haven't got a full tablet log yet.
Created attachment 102704 [details] tablet log 3 Here's a better log file.
Comment on attachment 102704 [details] tablet log 3 I wonder... prs: 0.000000 Stylus Pen id: 146028888065 xTilt: 15 yTilt: 5 rot: 0 z: 0 tp: 0 " That means that the pressure is always 0; no wonder that Krita doesn't draw a line. And I cannot believe that a Hanvan tablet supports tilt, but those values vary. Looks like the driver puts the values in the wrong variables.
Hm... there are some small pressure values though. Edgar, do does your tablet support tilt?
Mark as unconfirmed for now
No it doesn't have tilt, or if it does have tilt features, I wouldn't know since I have never used tilt/and/or noticed it. So if the hanvon driver is putting in values at the wrong variables, does this mean I'm pretty much out of luck with using Krita?
For now, yes -- if we get access to the hardware so we can experiment, we might be able to figure out what it's doing wrong. Weirdly enough. as dmitry said, I was wrong and there _is_ some pressure info in the logfile, and that _should_ result in a line: 00000455 37.93141556 [2368] krita.tabletlog: "[ ] TabletMove btn: 0 btns: 0 pos: 503, 400 gpos: 533, 514 hires: 532.894, 514.483 prs: 0.713587 Stylus Pen id: 146028888065 xTilt: 21 yTilt: 0 rot: 0 z: 0 tp: 0 "
Thanks guys... I might have to save money for wacom.
I'm sorry, we're going to have to close this report since there's nothing we can do with it.
Yeah that's fine. I'm sorry I haven't updated this since I bought a wacom and moved to Linux.
Good choice :-)