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

Correcting Surface Pro 3 ntrig wintab offset due to tilt

Tags: None
(comma "," separated)
jameskin
Registered Member
Posts
3
Karma
0
Version info: Krita 3.0.1.1 on a Surface Pro 3 Windows 10, ntrig stylus with wintab x64 1.0.0.20

Hi, when I write I get an offset that occurs if the pen is not perfectly perpendicular to the surface. I think this is happening since the driver is detecting a point inside the stylus. This means whenever the pen is tilted, the point at which kritas draws is always blocked by the pen.

I was wondering is there was a custom hard offset workaround? I think this would be a useful feature for all users as well.
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
Hm, I haven't noticed this with my Surface Pro 3.
jameskin
Registered Member
Posts
3
Karma
0
Really? Hmm, I might have a longer nib, let me try swapping with another pen (I had to get a replacement pen, the ones with the fancy colours, eraser, and is springless)
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
Ah, I only use the default pen -- and not even that often, because I find that the whole windows gui lags when trying to use a pen.
jameskin
Registered Member
Posts
3
Karma
0
Totally with you on the lag.


Took me a while to try some pens and nibs, the problem tilt problem is there. But it stems from the surface pro 3 or windows. When you calibrate there are two phases. One with 16 dots, four on each corner, the other with just 4.

The first is just for non linearity in hardware across the display, Tilt offset is removed by using four points at each corner.
The second phase corrects for one particular tilt, and it isn't perfect, ie, it gets an offset caused by tilt at those four points by interpolating the tilted positions. So you need to do this one four times, one for each orientation.

I think wintab is missing that second bit. Don't know how to calibrate it either.


Bookmarks



Who is online

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