Bug 363657 - No pressure sensitivity on Surface Pro 4
Summary: No pressure sensitivity on Surface Pro 4
Status: RESOLVED DUPLICATE of bug 355179
Alias: None
Product: krita
Classification: Applications
Component: Brush engines (other bugs)
Version First Reported In: 2.9.11
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-29 10:49 UTC by Geoffrey Mégardon
Modified: 2016-05-30 06:56 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Geoffrey Mégardon 2016-05-29 10:49:31 UTC
Hello, 
Just to say that there is no pressure sensitivity on Surface Pro 4, even after installing the Wintab drivers.
Note that the pressure sensitivity works on MyPaint, Sketchable, Mischief, Graphiter but not on Sketchbook pro. If that can help.

Reproducible: Always


Actual Results:  
Same opacity and size while varying the pen pressure

Expected Results:  
Variance in opacity and/or size when varying pressure
Comment 1 Scott Petrovic 2016-05-29 11:30:36 UTC
Have you tried a 3.0 build. You need that version for it to work. Also how are you checking for Windows updates?
Comment 2 Geoffrey Mégardon 2016-05-29 11:53:19 UTC
I tried Krita 3.0 RC 1. I experience the same problem.

I updated my Surface using the check update in the windows 10 settings.
I download the Wintab drivers from MS website:
https://www.microsoft.com/en-gb/download/details.aspx?id=49498
Comment 3 Halla Rempt 2016-05-30 06:56:58 UTC
After updating to windows 10, my SP3 refuses to be restored to factory state, so it's a bit hard to figure out what's going on since Krita now works on it... People tell me there are two possible solutions: the filthiest hack is to install and then remove the Photoshop CC trial, after installing the wintab driver. Apparently, that replaces some broken Microsoft system component...

*** This bug has been marked as a duplicate of bug 355179 ***