You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cursor appears and draws offset from where my actual stylus is on the screen. I am using an Artisul D16 Pro to draw, it renders too big on that screen as well.
A fix would be appreciated
The text was updated successfully, but these errors were encountered:
Having the same issue. I am using a UGEE 2150. It almost seems like it's exponentially offsetted. For instance, if I draw with my stylus at the very right corner of my graphics display, it will be almost accurate. But when I start to draw towards the center of my screen, the offset becomes greater the more I move away from the bottom right corner.
Update: Immediately after I wrote the above, I figured that it is a problem with having two monitors. So I disconnected my second monitor (The non-graphics display), and I was able to draw accurately. Even when I reconnected my second monitor, I was still able to draw accurately UNTIL I closed the application.
Now that I have narrowed down the issue to having two monitors, the exponential offset I explained before make more sense. It seems that the app is somehow re-calibrating my tablet to work off the total width and height of both my monitors put together, meaning the top left corner of my graphics display (My graphics display is oriented on the right hand side) is the simulated center accordin to the app. I proved this by placing my stylus roughly in the center of my graphics display which the app started to draw roughly around the top left corner of my display.
Hope this helps, relative version:
1.91.
Note: My second monitor is a 4K ACER, but to experiment I dumbed it down to 1080p to match my graphic display.
The cursor appears and draws offset from where my actual stylus is on the screen. I am using an Artisul D16 Pro to draw, it renders too big on that screen as well.
A fix would be appreciated
The text was updated successfully, but these errors were encountered: