New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pen no longer works in Aseprite with Windows 10 Fall Creators Update #1595

Closed
amzeratul opened this Issue Oct 27, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@amzeratul

amzeratul commented Oct 27, 2017

We've had an issue this morning on multiple machines, after they received the Windows 10 Fall Creators Update. Pen input, which worked fine before, stopped working in Aseprite.

To be more specific, attempting to use the pen would sometimes have no effect, or sometimes scroll instead of using the selected tool. Very rarely (about 1 in 15 times, they report) it would behave correctly, using the selected tool as expected. The artists affected also reported that while trying to use it on the scroll bar, the scroll bar would react visually as if the mouse was hovering it, but attempting to drag it would have no effect.

Pen input still works correctly on other programs, such as Adobe Photoshop. Reverting the Windows update makes Aseprite work again (and is our temporary workaround), but is not a long-term workable solution. We would really appreciate a fix for this, as we have a lot of people here using Windows 10 and Aseprite. :(

Aseprite and System version

  • Aseprite version: Aseprite v1.2.3-x64
  • System: Windows 10 Pro, x64, Version 1709, OS Build 16299.19
  • Computer: Microsoft Surface Studio

@dacap dacap self-assigned this Oct 27, 2017

@dacap

This comment has been minimized.

Show comment
Hide comment
@dacap

dacap Oct 27, 2017

Member

Hi @amzeratul, I'll be working on this issue today as it was already reported by a couple of other users. I have a Surface Pro to test it so a fix might appears next week ASAP.

Member

dacap commented Oct 27, 2017

Hi @amzeratul, I'll be working on this issue today as it was already reported by a couple of other users. I have a Surface Pro to test it so a fix might appears next week ASAP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment