Question

Q: Tablet issues since Windows 10 Fall Creator's Update

Hi, I've been having some really frustrating issues with my Intuos Pen and Touch Medium that I can't seem to find any solution for.
These issues seem to be stemming from the Windows 10 Fall Creator's Update.

When using the application Paint tool SAI, the pen will sometimes 'hitch' very subtly when I hover the pen over an already existing line. Video example here
.

When using the application Drawpile, there is always a slight pause in the pen input-- this is especially noticeable when drawing circles. Video example here.

I draw for commissions and require a lot of precision in my lineart, so these issues have absolutely frozen my workflow.

The first time I had these issues was around October, when the update first came out. With no working solution then, I simply rolled back the update. This solved all of my issues. However, I am now using a brand new computer and cannot roll the update back. I am stuck with the Fall Creator's Update and the same issues have returned.

I have tried:
- Replacing my pen nib
- Checking if my drivers are up to date (they are)
- Uninstalling and Reinstalling the drivers
- Changing Windows Ink settings, including "Ignore touch input when I'm using my pen"
- Turning off Windows Ink completely
- Tweaking pressure sensitivity
- Testing it out on two other computers (one without the Fall Creator's update worked fine, but the one with it had the same issues.)
- Reinstalled the applications that I use (SAI and Drawpile)
- Contacting Wacom (they didn't solve any of my issues)


None of these attempts have fixed the issues with my tablet on my new computer. 
I hope that you can supply some help or at least give an ETA on any updates that might fix my problems. Thank you.


* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hi,

 

 

Thank you for letting us know the troubleshooting steps that you've performed. However, if the issue persists, we suggest submitting your issue using the Feedback Hub. You can either vote on an existing submission or submit a new issue. When you submit a feedback item we gather additional details and information about your issue that will help determine what’s causing it and address it. Feedback items regularly receive Microsoft responses on the submissions in the Feedback app so you can see what we are doing about your feedback. Please revisit frequently to see the status of your feedback items. 

In order to submit new feedback, please follow these steps:

  1. On a Windows 10 device, search for “Feedback Hub” in Cortana search, then launch the app.
  2. Navigate to Feedback in the left menu, then press + Add new feedback.
  3. Select the Problem, and share any details you think are relevant, and choose an appropriate category and subcategory.
  4. Important: If possible, reproduce the problem(s) after clicking Begin monitoring (or Start capture) near the end of the form; Stop monitoring when you’re done.
  5. Once you’ve completed the form and monitoring, click Submit.
  6. Click Continue using Feedback Hub.
  7. Click My feedback at the top, then find the item you submitted (it may take a while to appear).
  8. Open the item you submitted, then click Share.
  9. Click Copy link, then paste the link here in your response (it will look like https://aka.ms/<unique link>).

Free to post back should you have other concerns.

Did this solve your problem?

Sorry this didn't help.


Ironically, I only posted here because the feedback hub post I made didn't have nearly enough details due to the character limit, and it didn't get any replies from microsoft. 

The link is here

Thanks again.

Did this solve your problem?

Sorry this didn't help.


Thank you for providing the feedback link. Our software engineers already got your feedback. We'll follow this up with them, and we also suggest checking your feedback item from time to time to see the status.

 

Regards.

Did this solve your problem?

Sorry this didn't help.


Wacom had a driver update on 2/22/18. However, I'm still having these same issues. Nothing has changed. There have been no updates or follow-up with engineers or developers here or on the feedback hub-- I haven't been able to do my work in two months now. I've tried everything aside from buying a new tablet outright. 

If there's anything I can do or try, or some sort of update, please let me know. :(

Did this solve your problem?

Sorry this didn't help.


If you pay attention to any forums, Micro$oft has completely ruined graphic tablet response, precision and dependability across the board,  and hasn't done squat about it for 4 or so months now. Its gone so far as to disrupt functionality of their own surface pro line without a fix, and sparking "flickergate" so it's clear that they don't care at this point. 

Oh, but everything works GREAT with affiliated software designed just for windows 10 exclusively... but if you're like me, and already spent a few grand on versions of photoshop and manga studio, your ONLY option thus far is to roll back to an earlier build. 

I have a lot of money invested into my artwork, and my stuff does exactly what you describe and more, in photoshop, illustrator, and Manga Studio EX 5, with a Dell Canvas 27 and a Wacom Cintiq 12 inch. By Odin's Beard, the bloody Dell Canvas WAS CREATED FOR THE UPDATE AND THEY STILL BORKED IT!!!

They dont get (dont care?) that the "CREATOR'S" update has done exactly the opposite of what its namesake implies. 

We're not the only artists losing money, and it needs to change before someone out there gets lawyers involved.

Did this solve your problem?

Sorry this didn't help.

20 people were helped by this reply


Just an addition, to make matters worse Microsoft has apparently spent alot of time making it increasingly difficult to find .iso files of 1703 creator's update Windows, instead of working on 1709 Fall update crippling issues. much like a hard dump, there's a real push for this turd.

Did this solve your problem?

Sorry this didn't help.

2 people were helped by this reply


I've seriously looked everywhere and tried everything. I can't believe how much I've come to regret building a new pc. I can't roll back the updates, so I guess I'm just screwed for now :(

I've contacted windows support on twitter. I'll let you know if they tell me anything of value there or anywhere else. 
It's the least I can do for another artist. Solidarity, man :(

Did this solve your problem?

Sorry this didn't help.

4 people were helped by this reply


Hey. Just a small update. I've purchased a brand new tablet (Wacom BT M) in the hope that it was just my old tablet butting heads with the new "functionalities". 
I'm having the same exact problems that I've had with my old tablet! I've also tried switching the tablet's connection between USB 2.0, 3.0, and Bluetooth, as well as checking for latency issues. No dice. Needless to say, this has driven me to a near-madness.

But it seems hope is not lost-- there was a slight tablet functionality tweak in the latest Cumulative update (I'm updating right now! really hope I can finally be done with this nonsense!) and I've also heard whispers from some windows beta testers of a Spring Creator's Update that fixes the tablet issues.

Still, I'm very disappointed with the lack of real response from Microsoft. I've gone through three of their support systems and have gotten the same stock answers.
The Microsoft support twitter kept deflecting me to the phone line that costs money, THEY DELETED MY FEEDBACK HUB POST, and this forum has been completely silent. I am beyond angry at this level of "support".

I haven't been able to draw in >3 months now and I've been forced to find another method of making extra cash. This has directly impacted my livelihood and I don't know what to do now other than wait for an update that may or may not exist.

As always, if anyone has any new troubleshooting ideas, I'd really love to hear any and all of them. Thanks.

Did this solve your problem?

Sorry this didn't help.

8 people were helped by this reply


May we know what is the current Windows version and build of your device. This is information is vital in isolating the issue. To get the details go to Start > Settings > System > About.

Regards.

Did this solve your problem?

Sorry this didn't help.


I've had the same exact "hitching" problem in Sai, after having to reinstall my entire OS after it got corrupted (thanks, Microsoft), I was forcibly given the Creators Update and I had no way to roll back. However, with some messing around, I managed to get a solution that works in both Sai and Sai 2. I'm not sure if everything I did is necessarily how the problem was solved, but I'm adding it all here just in case.

For starters, I fully updated Windows 10. There was apparently a small patch that I was lacking, and I installed that. (This seemed to be the thing that ultimately fixed it, at least for me.)

I also added something to the registry which is supposedly supposed to undo all the Windows Ink functions. It can be found here:
https://www.reddit.com/r/Windowsink/comments/8508fi/controlling_pen_behavior_in_windows_10/dxb6mxj/
Open your command prompt, copy and paste the command. Apparently you are supposed to restart after adding this, but I'm not sure it's necessary or not. 

And then for good measure, I disabled Windows Ink for Sai in the Wacom Properties and also changed my pen tablet control within Sai. You want it to be set to "Use WinTab API) instead of TabletPC API. Depending on what version of Sai you have, this may or may not be an option. For example, I don't have this option in my old Sai but I do on Sai2. Either way, it worked for both versions when I tested them. 
To change this, in Sai, go to Help > Options, and it will probably be under the Pen Tablet tab or something similar.

Hopefully this helps!

Did this solve your problem?

Sorry this didn't help.


* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
Question Info

Views: 2,489 Last updated: July 16, 2018 Applies to: