New driver ruins Clip Studio pen performance

[rramrram]

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]

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]

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]

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

[rramrram]

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]

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

[Moonstalker]

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

[FVorange]

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]

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]

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