Bug 381931 - Surface Book pen support only works intermittently
Summary: Surface Book pen support only works intermittently
Status: RESOLVED FIXED
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.4
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-02 18:59 UTC by stuff
Modified: 2017-09-21 09:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 3.3.0-rc.1
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stuff 2017-07-02 18:59:55 UTC
Using the pen with a Surface Book, Krita seems to only pick up the pen input correctly some of the time.

I'm running at 200% DPI, and on all occasions, Krita will prompt me to choose screen resolution - either 3000x2000 (Wintab) or 1500x1000 (Qt). On some occasions, picking the top [Wintab] option will work absolutely fine, and the pen input will work as expected. Other times, picking that option will operate with the pen input being detected 'offset' from its actual position - as though it hasn't detected the DPI correctly (i.e. positioning the pen 50% across the screen, Krita draws at a position 25% across the screen).

This can happen both while the screen is docked into the base, or when it's detached, so it's not dependent on which graphics card is active.

Sometimes, exiting Krita and restarting will fix it; other times, it won't, so it seems rather random. I've never observed picking the Wintab option causing it to work - that always seems broken (albeit I haven't exhaustively verified that it *never* works!). I have installed the Wintab drivers for the Surface Book.

The pen input works in other pen-enabled apps even when Krita's misdetecting it, so it certainly doesn't appear to be a hardware fault.

If there's any way to gather additional debug info that would help in tracking this down, I'm quite happy to do so, if anyone can direct me on how to do so.
Comment 1 stuff 2017-07-02 19:01:28 UTC
(D'oh - typo. Fourth paragraph should state 'I've never observed picking the ***QT*** option causing it to work - that always seems broken (albeit I haven't exhaustively verified that it *never* works!).')
Comment 2 Alvin Wong 2017-09-21 09:40:58 UTC
Using Windows Ink through Pointer Input messages on Windows 8 or above is supported in 3.3.0-rc.1 (though not enabled by default): https://krita.org/en/item/krita-3-3-0-first-release-candidate/

It should work better for N-Trig Surface devices than WinTab, and this issue should be fixed with it.