Pen only drags canvas in PS (MSP)
Posted: Mon 2. Apr 2018, 14:19
I'm REASONABLY certain this is a problem with some random Windows update because there hasn't been either a Wacom or Adobe update since this weekend...
When I booted up PS this morning, I can not use the pen when trying to draw on the canvas. When I do, the pen simply drags the canvas as though it were a web page or something I was trying to scroll. Even if I hold a modifier key (Z for example) the pen will only drag the canvas. If I manage to zoom the canvas out to where it's entirely visible, ONLY THEN will the pen actually draw. But as soon as I zoom in to the point where ANY of the canvas doesn't fit on the screen, I can only drag.
Flicks has been disabled (it was never enabled in the first place).
If I disable Windows Ink in the Wacom properties, things behave as they should, but I lose pressure sensitivity. (I was able to enable WinTab in PS, so that much is working now.)
Has anyone encountered this before? Is this the first time this has been reported? I'd ask Wacom support directly, but their knee-jerk reaction to any problem is "factory default" and not "troubleshoot."
When I booted up PS this morning, I can not use the pen when trying to draw on the canvas. When I do, the pen simply drags the canvas as though it were a web page or something I was trying to scroll. Even if I hold a modifier key (Z for example) the pen will only drag the canvas. If I manage to zoom the canvas out to where it's entirely visible, ONLY THEN will the pen actually draw. But as soon as I zoom in to the point where ANY of the canvas doesn't fit on the screen, I can only drag.
Flicks has been disabled (it was never enabled in the first place).
If I disable Windows Ink in the Wacom properties, things behave as they should, but I lose pressure sensitivity. (I was able to enable WinTab in PS, so that much is working now.)
Has anyone encountered this before? Is this the first time this has been reported? I'd ask Wacom support directly, but their knee-jerk reaction to any problem is "factory default" and not "troubleshoot."