Page MenuHome

Pen pressure cannot be detected on Wacom Cintiq Pro 16
Closed, ResolvedPublic


System Information

Windows 10 ( with Bootcamp on MacPro 2013)
GPU : AMD FireProD700

Blender Version
Broken: 2.78c, 2.79 test build

Short description of error

Pen pressure from Wacom Cintiq Pro 16 cannot be detected. It works with Intuos Tablet.
Tested in GreasePencil, Sculpt mode, Texure Paint mode.

Exact steps for others to reproduce the error
You need to have Wacom Cintiq Pro 16, but it might be able to reproduce the issue with other graphic tablets as well.

Event Timeline

Bastien Montagne (mont29) triaged this task as Normal priority.

The problem will indeed be to find some dev with said material able to reproduce the issue… :/

In the meanwhile, can you try to reproduce the issue on a genuine Windows machine? Doubt mac/bootcamp could cause such issue, but you never know… Also, checking for updates of Wacom drivers might be a good idea.

I was testing with some different tablets and had a similar problem with a Wacom Intuos 4 Model PTK-640. After digging into it, I found the cursors being reported as values that aren't handled in GHOST. The following diff fixed it for me.

Looking into it more I think that there is a programmatic approach to knowing which cursors are active according to Wintab, using WtInfo and WTI_CURSORS, which might bullet-proof this more. I'll look into this more next time I have access to a bunch of tablets.

Thanks for the patch. I committed a more general fix now, hopefully works for the Cintiq too. Tomorrow's build will have the fix:

Certainly more improvements in tablet handling are welcome, ideally even using Windows Ink.

Great! No problem! Sure I will look into Windows Ink problems next time I have access to the hardware.

This is still broken for me but it usually doesn't start right away. When it starts, even my mouse won't work and it also affects texture and curve drawing. If I disable pressure sensitivity then I can make brush strokes again.

This report has been closed, should I file a new report somewhere else? I'm not sure how to trigger this problem to start happening so I've been putting it off.