Wacom Customer Support page: https://support.wacom.com/
Wacom Product Resources - Drivers, Manuals, Warranty Information & Others

Pen not working after Mac OSX update June 2019:
http://forum.wacom.eu/viewtopic.php?f=11&t=4011

Why is the cursor on Windows a white dot or crosshairs?
http://forum.wacom.eu/viewtopic.php?f=11&t=4013#p8912

Mac OS 10.15 Catalina Beta:
https://www.wacom.com/en-us/support?guideId=015-916

Product Registration:
Please register our products on https://www.wacom.com/register
How do I register my Wacom device?

Drawing software:
If you wondering which software to choose, check the trial versions below:

New driver ruins Clip Studio pen performance

Everything related to drivers
rramrram
Posts: 4
Joined: Thu 24. Jan 2019, 08:36

Re: New driver ruins Clip Studio pen performance

Postby rramrram » Sun 27. Jan 2019, 02:02

wacom5 wrote: I have not tested so I cannot confirm if it works but version 6.3.29-6 seems to help.

I tried Photoshop and there too faced the broken line problem, I'll be converting back to this version then, let us know if there's any update on the fix

wacom5
Posts: 722
Joined: Tue 8. Aug 2017, 14:35

Re: New driver ruins Clip Studio pen performance

Postby wacom5 » Mon 28. Jan 2019, 09:27

rramrram wrote:
wacom5 wrote: I have not tested so I cannot confirm if it works but version 6.3.29-6 seems to help.

I tried Photoshop and there too faced the broken line problem, I'll be converting back to this version then, let us know if there's any update on the fix

Your issue may be something else then... Please check with our support - https://support.wacom.com

FVorange
Posts: 10
Joined: Fri 21. Sep 2018, 18:55

Re: New driver ruins Clip Studio pen performance

Postby FVorange » Tue 12. Feb 2019, 18:45

Any news on this issue?

I'm missing several little fixes/updates on recent drivers, I'd love to update and have this solved at last.

wacom5
Posts: 722
Joined: Tue 8. Aug 2017, 14:35

Re: New driver ruins Clip Studio pen performance

Postby wacom5 » Wed 13. Feb 2019, 09:12

No updates at the moment. All I know is the driver team is working on it with Celsys.

rramrram
Posts: 4
Joined: Thu 24. Jan 2019, 08:36

Re: New driver ruins Clip Studio pen performance

Postby rramrram » Wed 13. Feb 2019, 23:12

wacom5 wrote:No updates at the moment. All I know is the driver team is working on it with Celsys.


cant the update team just contact Microsoft and get along about this whole Windows Ink issues? in every software it f's something up in a way every other Windows update does sth wrong about it, so much that it makes me wanna go back to Mac

wacom5
Posts: 722
Joined: Tue 8. Aug 2017, 14:35

Re: New driver ruins Clip Studio pen performance

Postby wacom5 » Thu 14. Feb 2019, 08:45

The driver team also works with Microsoft on other issues but this issue is not related to Windows Ink.

Moonstalker
Posts: 1
Joined: Fri 1. Mar 2019, 19:54

Re: New driver ruins Clip Studio pen performance

Postby Moonstalker » Fri 1. Mar 2019, 19:57

Did the latest update to Clip Studio on the 28th of February fix this issue, or is work continuing on it?

FVorange
Posts: 10
Joined: Fri 21. Sep 2018, 18:55

Re: New driver ruins Clip Studio pen performance

Postby FVorange » Sat 16. Mar 2019, 15:14

Moonstalker wrote:Did the latest update to Clip Studio on the 28th of February fix this issue, or is work continuing on it?


I believe it's fixed. In Clip Studio's Preferences > Tablet > Input Frequency check "Prioritize Quality" and the strokes behave normally.

wacom5
Posts: 722
Joined: Tue 8. Aug 2017, 14:35

Re: New driver ruins Clip Studio pen performance

Postby wacom5 » Mon 18. Mar 2019, 10:18

FVorange wrote:
Moonstalker wrote:Did the latest update to Clip Studio on the 28th of February fix this issue, or is work continuing on it?

I believe it's fixed. In Clip Studio's Preferences > Tablet > Input Frequency check "Prioritize Quality" and the strokes behave normally.

Good to know, thanks!

wacom5
Posts: 722
Joined: Tue 8. Aug 2017, 14:35

Re: New driver ruins Clip Studio pen performance

Postby wacom5 » Mon 24. Jun 2019, 07:41

The driver team has confirmed this should have been fixed after the 6.3.34 release.


Return to “Drivers”