Bug 346744 - [WACOM INTUOS] Mapping and Pressure Problems with Krita and Wacom Intuos Pro tablet when I use two monitors (laptop+second hdmi monitor).
Summary: [WACOM INTUOS] Mapping and Pressure Problems with Krita and Wacom Intuos Pro ...
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-04-26 23:54 UTC by Daniel
Modified: 2018-10-28 03:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Two DebugView log files (121.02 KB, application/x-zip-compressed)
2015-04-26 23:57 UTC, Daniel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel 2015-04-26 23:54:26 UTC
Krita ver. 2.9.2
OS: Windows 8.1
Tablet: Wacom Intuos Pro M
PC: Dell Laptop Core I7
1) Krita running on the laptop's  integrated monitor (main): It results in a wrong mapping/offset (only into the Canvas workspace). No offset while on the menus and dockers.
2) Krita running on the second monitor: The mapping gets OK, but NO Pressure sensitivity.
I made two log files: The first on the main monitor (offset). On the second Log I dragged Krita to the second monitor, switched the tablet mapping also to this second one e draw a couple of lines, but it has no Pressure sensitivity.
Thanks a lot!
Daniel


Reproducible: Always

Steps to Reproduce:
1. Run Krita in a Win 8.1 enviroment with two monitors
2. Try to draw at main monitor (offset)
3. Switch to second monitor (no pressure sensitivity)

Actual Results:  
Wrong Mapping

Expected Results:  
Right Mapping and Pressure Sensitivity  ;)

Thank you a lot!
Krita is great!
Comment 1 Daniel 2015-04-26 23:57:47 UTC
Created attachment 92240 [details]
Two DebugView log files
Comment 2 Halla Rempt 2015-05-20 11:33:47 UTC
Hi Daniel,

Thanks for your report. I haven't had time to setup a dual monitor setup (other than my usual dell + cintiq setup) so I haven't been able to reproduce it yet, I'm afraid.
Comment 3 krita1.3.bukbukbukark 2015-10-20 05:08:22 UTC
This sounds possibly related to the problem I'm seeing, apologies if it's a separate issue but this is what I've found:

I'm only seeing the offset problem.

I'm only seeing it with Krita Gemini 2.9 pre-alpha (Krita Desktop 2.9.8 is working correctly for me - beautifully in fact - so perhaps this bug has already been fixed?).

I'm using a surface pro 3, windows 10, without a secondary monitor.

I'm seeing an offset to the pen tracking that corresponds to the windows DPI scaling setting.

I have to have the DPI scaling set to 150% as the screen is so dense, and with that setting there is a varying offset from the physical position of the pen, as though Krita is getting unscaled coordinates for the pen. In other words it will track as if the screen was smaller than it actually is.

Setting the DPI scaling to 100% cures the problem, but makes all the UI unusably small.
Comment 4 Halla Rempt 2015-10-20 05:58:23 UTC
Yes, we fixed the n-trig/surface pro scaling issue in 2.9. The fix didn't work for gemini, but gemini 3.0 should be fine.
Comment 5 Halla Rempt 2016-06-17 09:13:30 UTC
Could you try: 

https://docs.krita.org/KritaFAQ#How_to_fix_a_tablet_offset_on_multiple_screen_setup_on_Windows

For fixing the offset?
Comment 6 Halla Rempt 2016-10-31 14:48:36 UTC
Please check back when having tested with that howto.
Comment 7 Andrew Crouthamel 2018-09-28 02:44:03 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-28 03:33:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!