Hello. I just (re)discovered Krita which really evolved since last time i tried it. However i have a rather strange issue when trying to use my tablet.

My computer runs under windows 10. My tablet is an old Wacom from the Bamboo line, not sure which one (there have been several) the model on the back side lists MTE-450/K(B). I have installed the latest Wacom drivers listing some Bamboo tablets as compatible devices (under legacy devices) but it's more than 2 years old and unlikely to see any further updates.

Here is what happens in Krita :

• If i try to use the Windows Ink API, "everything" works except i have no pressure sensitivity which isn't a small issue.
• With WinTab API however, things get really "funny". If i select a brush in the brush docker and try to paint on the canvas, it doesn't work at all but the side button (stylus right-click) does bring the brush selector and the tablet buttons i've configured for "4" and "6" keys rotate the canvas correctly.
  If OTOH i select a brush with the top bar selector and the directly start painting (without first clicking outside the selector to close it), everything works fine including pressure sensitivity but stylus right-click and tablet buttons don't work.
  Also if i put away the stylus and then move the mouse, the brush will continue painting under the mouse until i click with the mouse anywhere, at which point i can no longer use the stylus until i reselect a brush in the top bar.
  Finally, the second stylus button (set to "pan" in my Wacom Control Panel) apparently toggles a full pressure stroke as if i was holding my mouse button down and prevents the stylus from working (exactly as if i had clicked with the mouse)

Any idea how to solve that mess?

1. means that the tablet is only sending mouse events, so it doesn't work at all.
2. probably means you should first start with completely resetting the wacom tablet configuration and Krita's configuration. Don't create a generic wacom configuration, but create per-application configurations. For example, by default, without configuring anything, your pen button will already pan in Krita.

See https://docs.krita.org/KritaFAQ#Resetti ... figuration for how to reset Krita's configuration.

Thanks for the reply.

My Krita config is as clean as it could be given it's a brand new install (i had never used it on windows before) so the issue doesn't come from that.
As for the Wacom config, there's nothing like per-application config with the limited software for that model. In trying to reset the config i uninstalled the wacom driver and reinstalled it, however as a test i reinstalled an older version (specifically mentioning MTE generation Bamboo) i found on a hidden download page that's no longer accessible from the wacom front page. It's a Windows 8 version from 2014 rather than the win 10 "compatible" version from 2015) and now it looks like the pressure is working with Windows Ink API (but no longer works with WinTab API) and i don't have the strange behavior i had with the new driver.

So it looks like it's a driver issue but one i had to solve by downgrading to an older version. I fear that tablet isn't going to work much longer despite having no actual issue itself simply because of lack of driver support. If a windows upgrade ever breaks compatibility with the win8 driver i'm now using i'll have no choice but to purchase a new one (unless i can actually get foobar2000 to run under linux since it's actually the main reason i'm sticking with win but that's another story).

Well, looks like it's fixed, at least temporarily. I'll keep a backup of that 2014 driver.

In my experience, trouble with tablets is pretty much always a driver issue