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
Start of stroke stuck #886
Comments
There is no pen mode hack in Drawpile at current version. What version are you running? |
Does the problem happen in Krita also? I suggest installing it for two reasons... A) You'll get a preview of ORA files on your computer! Download and install here https://krita.org/en/download/krita-desktop/ or here https://ninite.com/krita/ ... let me know. |
It might not have been Windows Ink specifically, what I was saying earlier is that Drawpile pulled tablet support from Krita for Windows Ink so that might have some impact. That is to say, the operating system has it's own Windows Ink API (there was some issues in Windows 10, version 1803 and 1809 I believe) and the drawing programs must support that API... so if both aren't up to date, you could have issues. I don't know all the specifics however, so there is something I could be missing regarding that. I think Krita has made some improvements to the Windows Ink API so importing it into Drawpile might be helpful, though last I knew they were also waiting on patches to QT to be accepted... which Drawpile also uses. Anyway, glad you figured it out. I've seen some weird tablet issues like that where I had to try updating, reinstalling, and/or going to an older version with Wacom. At least it works now! |
While I'm aware that this issue has been brought up here: #238 (and suggests that it has been resolved), I'm having no such luck.
Only as of the last few patches I've started having this issue, which is exclusive to Drawpile.
Things I have tried to resolve the issue include:
Enabling/disabling windows ink, enabling/disabling the pen mode hack, restarting my computer and the program, reinstalling my drivers, closing other programs, changing input smoothing, etc.
I'm not sure why this would only start happening as of the past few updates, so I'm assuming it's a bug. I was wondering if anyone has any other suggestions because I'm not sure what else I can try from here to stop it.
The text was updated successfully, but these errors were encountered: