Most editor buttons cannot be used with a graphic tablet if winink driver is selected (new default in Godot) but Windows drivers have "Use Windows Ink" unchecked

[Jowan-Spooner]

Tested versions

• broken in 4.4beta 1
• broken in 4.4dev3
• works in 4.3 stable

System information

Godot v4.4.beta1 - Windows 10 (build 19045) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 (NVIDIA; 32.0.15.6094) - AMD Ryzen 5 3600 6-Core Processor (12 threads) + Wacom Tablet

Issue description

Most buttons can no longer be pressed using my tablet pen. This also affects buttons in exported products. I only know of this because a user informed us that this broke in the newest material maker 1.4 alphas. Then I noticed the same is true in the godot editor, but was working fine in previous versions.

This affects most editor buttons, though there are some exceptions which I assume have some kind of different input code (e.g the menus and the little three dots on tab bars work as well). But any traditional buttons, toggles (e.g. in the inspector), the MainScreen buttons at the top, etc. all cannot be clicked anymore.

Steps to reproduce

Open the editor, connect a graphic tablet, try clicking a button.

Minimal reproduction project (MRP)

Godot Editor

[akien-mga]

• broken in 4.4beta 1
• broken in 4.4dev3
• works in 4.3 stable

Is 4.4.dev3 the first broken snapshot, i.e. does it work well in 4.4.dev2?

Which driver do you have configured in input_devices/pen_tablet/driver.windows? Can you try both winink and wintab to see if there's a difference?

[Jordyfel]

Cannot reproduce, buttons work properly for me with both drivers on a "one by wacom" (ctl-472) device

[Jowan-Spooner]

Is 4.4.dev3 the first broken snapshot, i.e. does it work well in 4.4.dev2?

It was just the earliest 4.4dev version I had still installed, but now I retested dev1 and dev2 and it turns out dev3 actually is the first broken snapshot as far as I can tell.

Which driver do you have configured in input_devices/pen_tablet/driver.windows? Can you try both winink and wintab to see if there's a difference?

Oh wow, yes, switching to wintab did fix this (had none specified before). It was a bit unexpected to find this project setting effecting the editor as well, but oh well. From what I can find online wintab is just a really old API? So this is probably just caused by using a fairly old tablet? Still a bit strange that it works fine with both drivers in 4.3. Is there a downside to using wintab in a project? Would we have to implement a setting in material maker to switch between those two drivers?

[bruvzg]

Oh wow, yes, switching to wintab did fix this (had none specified before).

Do you have Use Windows Ink in the tablet properties unchecked? Not sure if it's still possible to disable it, it seems to be grayed out on Windows 11. But it at least should be enabled by default. The setting page should look like this:

If it's disabled, I guess it is expected not to work unless Godot is also set to use wintab.

Default setting was switched since a lot of third-party tablet manufacturers ship half broken implementations of wintab.dll (Wacom original is fine).

Not sure if we can detect if what's configured in the table properties, but it might be worth at least checking the setting for Wacom and auto switch Godot to wintab.

[Jowan-Spooner]

Thanks! That does work for me. I will forward this to the user who originally reported this to me for the material maker alpha releases.

In my opinion this information does make this issue way less of a deal breaker even though it still does break compatibility. Thank you all for the quick input!