User avatar
Support Team
2,412 posts
If you are using the latest Windows 10 "Creators" update, then you most likely are experiencing an issue with your Tablet peripheral not working as intended, or your cursor being stuck in the top left of your screen.

This seems to be an issue with Raw input in the latest Windows update, as having Raw input enabled causes the cursor to not work for most.

Currently the only "fix" or workarounds are to;
  • Disable Raw Input

  • Disable Windows Ink
    Wacom Tablets
    For Wacom Tablet Users, there should be a checkbox in your Tablet Driver settings to disable / enable Windows ink.

    You want it unchecked like so.


    Huion / Other
    For Huion or other Tablets, if the driver you are using does not have a checkbox toggle, you may have to follow these steps.

    1. Find your tabletconfig.ini in your driver folder.

    2. Change SupportINKDisalbe to 0 (Disable) Might be different dependent on language.

    Visual Representation courtesy of of pasi123567

    If you don't have a Huion tablet, I'm sure the procedure should be similar. If you can't figure it out. Try Googling your Tablet and seeing if you can't find out the info there.

  • Rollback to the previous Windows update.

These "luckily" seem to work a good Majority of the time. If none work, it's possible your issue is caused by something else, and not this one specifically.

Do remember that having your sensitivity set to anything not 1x will force Raw Input, and so you will have to set your sensitivity to 1x.

If this messed up your Tablet Area, please change the active area in your Tablet Driver Settings instead of using Sensitivity ingame.

This thread serves to show this is a known current issue. Please do not post in this thread unless you have found another Workaround or "Fix", and or have some information that could be useful to this issue.

DO NOT BUMP THIS THREAD WITH "Thanks", "same", or "I have this issue too and none of the fixes work :(" If none of the fixes work, you can try making a new thread, as it's possible this is not your issue.

Curse you Windows 10.
Reply 1 post

Users browsing this forum: None

Jump to: