This forum has been archived. All content is frozen. Please use KDE Discuss instead.

No support for Dual Monitors or Monoprice tablets?

Tags: None
(comma "," separated)
armvoid
Registered Member
Posts
3
Karma
0
I just tried Krita (newest stable build) for the first time, and it looks like my set up isn't supported at all unfortunately :(
When running Krita on my second monitor, or even just moving it there and back to the first moentarily, brush strokes wouldn't release after being started.
I also use a Monoprice tablet (aka. UCLogic) instead of Wacom, but the brush jumps back and forth from theft to right whenever a stroke is started.

I'm also running Windows8 on this PC, though I'm not sure how much that matters.

I'd like to know if there's anything I can do to get these issues resolved, as I've been hearing great things about Krita for a while now and would like to be able to give it a chance.

Edit: Just found this thread, where some progress seems to be being made on these issues: viewtopic.php?f=281&t=117746&p=294524
dkazakov
Registered Member
Posts
64
Karma
1
Hi, armvoid!

Do you use the build from "New Wintab Support" topic, right? (http://www.valdyas.org/~boud/krita_x64_2.7.8.23.msi)

If yes, could you generate a log as described in comment 33 on bugzilla: https://bugs.kde.org/show_bug.cgi?id=298144#c33
You can skip the step with calibration, but don't forget to turn on the logging with "Ctrl+Shift+T".

I would also like to know the size of your screens and how they are placed one to another.
User avatar
stipend
Registered Member
Posts
13
Karma
0
dual monitors works for my setup. i believe i did have to change mapping options in wacom's tablet properties to map the pen to a single monitor; are there properties for your tablet? (i only have experience with wacom tablets)
armvoid
Registered Member
Posts
3
Karma
0
Yea I'm using the latest release from that thread; it fixes the brush release issue, and the cursor doesn't jump back and forth anymore, but it doesn't take into account the current screen mapping and just assumes the tablet is mapped across both screens at once instead of the set active one.

Here's the requested log file, hopefully it helps:
http://www.sendspace.com/file/aubji9
tylerjones
Registered Member
Posts
4
Karma
0
armvoid wrote:Yea I'm using the latest release from that thread; it fixes the brush release issue, and the cursor doesn't jump back and forth anymore, but it doesn't take into account the current screen mapping and just assumes the tablet is mapped across both screens at once instead of the set active one.

I'm using a Yiynova MSP19U and have the same problem. Krita 2.7.9.5, x64.
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
Well, when I use my cintiq I effectively have a dual monitor setup too. On Linux, this can be configured correctly with the gnome wacom applet, but not the KDE one. On Windows, it actually worked out of the box. If not, the tablet/monitor mapping is something the wacom config utilities should handle -- Krita just takes the events the tablet sends.
tylerjones
Registered Member
Posts
4
Karma
0
boudewijn wrote:Well, when I use my cintiq I effectively have a dual monitor setup too. On Linux, this can be configured correctly with the gnome wacom applet, but not the KDE one. On Windows, it actually worked out of the box. If not, the tablet/monitor mapping is something the wacom config utilities should handle -- Krita just takes the events the tablet sends.

My tablet monitor is made by Yiynova, not Wacom, and does not work properly with Krita on Windows.

The strange thing is that I can use the menus just fine, but when I touch the stylus to the canvas the mapping goes wrong, as described before.
User avatar
halla
KDE Developer
Posts
5092
Karma
20
OS
Moar hardware... We need more hardware to test... I actually would have expected that the yiynova monitor tablets would work just fine on windows these days, since the huion tablet works as well, and both use uclogic digitizers.

Bah... it really sounds like we need more hardware -- a second monitor and a yiynova monitor tablet to fix these issues :-(
tylerjones
Registered Member
Posts
4
Karma
0
I just tried the windows 2.8 build and I hate to say but the problem is still there. My Yiynova MSP19U doesn't track accurately in the canvas.
User avatar
achibrucie
Registered Member
Posts
36
Karma
0
OS
tylerjones wrote:I just tried the windows 2.8 build and I hate to say but the problem is still there. My Yiynova MSP19U doesn't track accurately in the canvas.


If it is a tracking issue it could be a driver/ calibration issue. Have you tried to recalibrate? If you computer forgets the calibration it would be a hardware/ software issue and not krita.
tylerjones
Registered Member
Posts
4
Karma
0
achibrucie wrote:
tylerjones wrote:I just tried the windows 2.8 build and I hate to say but the problem is still there. My Yiynova MSP19U doesn't track accurately in the canvas.


If it is a tracking issue it could be a driver/ calibration issue. Have you tried to recalibrate? If you computer forgets the calibration it would be a hardware/ software issue and not krita.

No, the problem is only in Krita. The tablet works fine elsewhere.
brunodeleo
Registered Member
Posts
1
Karma
0
Sorry to revive such and old thread, but I'm having this same problem and it doesn't seem to have been fixed. I have two 1920x1080 monitors and an Ugee M1000L tablet on Windows 7 64bits. I've set up the tablet to work only in one of the monitors and it works perfectly everywhere but in Krita. Krita behaves as if the tablet was set up for both monitors and so uses only half of the tablet, this happens only when painting with a brush, not when using the pressure pen as mouse cursor. If I set up WIndows to only one monitor, everything works perfectly.
Thanks in advance!
hsing99
Registered Member
Posts
1
Karma
0
I have same problem use Tablet monitor of
YIYNOVA MVP20U-RH
User avatar
scottpetrovic
Registered Member
Posts
520
Karma
4
OS
I have a similar problem with a Wacom tablet. What causes it was starting Krita, then changing how many monitors you are displaying. For example.

Using laptop with one monitor
1. Start Krita
2. Plug in cable to have two monitors

Krita does not learn about the new monitor, so it maps oddly. This also happens when going from two monitors to one monitor. Restarting Krita fixes the issue for me.

Does restarting Krita help?


Bookmarks



Who is online

Registered users: abc72656, Bing [Bot], daret, Google [Bot], lockheed, Sogou [Bot], Yahoo [Bot]