Input inaccurate/offset when using multiple monitors with some graphics tablets

Bug #1188211 reported by Dean Lillie
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what resolution the secondary monitor is set to.

I actually managed to "fix" it. I opened up a memory editor, hooked it to inkscape and searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.

Inkscape doesn't seem to be reading screen width (edit: make that height as well) from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's far from a permanent or practical fix, the memory layout changes every time so it's inconvenient to do every time to say the least.

This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers.

Tags: tablet win32
description: updated
summary: - tablet input inaccurate/offset when multiple monitors
+ Input inaccurate/offset when using multiple monitors with some graphics
+ tablets
description: updated
description: updated
description: updated
description: updated
description: updated
su_v (suv-lp)
tags: added: win32
removed: input
Revision history for this message
Eva (huion-eva) wrote :

Hi, I read the article you published above, I also have a Huion 580 graphic tablet, I bought it recently. It is perfect at first, I like it very much. Then one day I draw on my tablet on screen, it takes a few seconds to respond. I wrote to their service center to ask for a solution. They told me I did not install the driver well, and ask me to update a new driver. I did as their instruction reset the driver, then the tablet worked perfectly again. Hope this will hope to solve your problem./this Link is where I download the new driver. you can have a try. http://www.huiontablet.com/download/

Revision history for this message
Travis Stewart (travisstewart42) wrote :

This bug appears to still exist in Inkscape 0.91. I am using Windows 10, have a Wacom Intuos Pen Small CLT-480/S0-AX. When I draw without my second monitor being used it works well, and there is no offset. However, when I attach my second monitor, a TV through HDMI, the cursor and drawing are offset, with the drawing offset to the left of the cursor position. My driver is set to use a single monitor, monitor 1.

Revision history for this message
Jasper (jasperslot) wrote :

Yesterday I made a forum post (https://forum.inkscapecommunity.com/index.php?topic=1274.0) about this, because I thought I did something wrong. Point is that even if I say to my Wacom it should only use monitor 1, Inkscape thinks it still uses 2 so it seems. As posted by the original poster a few years ago, this issue seems easy to fix? Let me know if I can test something.

Some extra info:
I use Windows 10, Inkscape 0.92.3 and a Wacom Intuos pro M (current model). An important finding: when I disable the Wacom tablet pressure stylus in the input devices options, it works perfect! However... pressure sensitivity is broken. Or if I enable my Wacom to use both screens, it also works, but I can only use half of my Wacom... since the other half is used for my second monitor. Pro: pressure sensitivity does work...

Please fix!

Revision history for this message
Carsten Pietzsch (theonlytruth) wrote :

Problem is still existing in Inkscape 1.1 on Windows 10 with Wacom Intuos Pro M. Three monitors.
For me it also doesn't work when I disable pressure sensitivity.

Revision history for this message
Mike Cline (uglycoyote) wrote :

I have the same problem. Windows 10, dual monitor setup. Left is a 4K (3840x2160) display at 150% scaling, right monitor is a 1200x1600 portrait screen at 100% scaling.

I like to run Inkscape on the 4K screen, but the tablet then has this offset problem.

Tablet is a Huion 1060Plus

When drawing with the mouse it is fine. When drawing with the tablet, the "ink" appears a ways to the right of the cursor.

It's definitely related to the scaling. If I drop the 4K screen down to 100% scale, the offset problem goes away. (but then I have a not-being-able-to-read-anything problem)

If I try Inkscape on the 1200x1600 screen, which has 100% scale, it still has the offset problem. Probably because that's the second monitor, and so whatever incorrect math Inkscape is doing is based on the origin of the first monitor and it's faulty assumption that the first monitor has a scaling of 100%

Why can't Inkscape just draw where the mouse cursor is? It seems like the problem here is that inkscape ignores where the mouse cursor is and uses some incorrect internal math to try to derive where it thinks I am drawing based on the tablet input. Is it circumventing the correct math that the OS already does to determine the cursor position?

Revision history for this message
Christian Zommerfelds (christianz) wrote :

I have the same problem on the Microsoft Surface Pro 8 with a 4K monitor attached. The external monitor is on top of the other.

Display 1 (built-in): 2880x1920 at 200% scale
Display 2 (external, on top): 3840x2160 at 125% scale

The pen offset is not constant, the lower it is on my screen the more offset it becomes.

This makes Inkscape unusable. Let me know if I can provide more info.

Revision history for this message
Christian Zommerfelds (christianz) wrote :

This bug is also listed here: https://gitlab.com/inkscape/inkscape/-/issues/1892

What is the official bug reporting process?

Lots of related reports you can find via Google search.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.