Hi, it’s probably not the reason, but your speed/smoothing settings look WAY too high to me.
Pfahah yeah, I tried small and big values to see if that would fix the problem. Didn’t bother changing them since I’m looking for the root of the problem still, but I’ll keep this in mind!
Today’s morning trials and progress:
-
disabled all plugins, checking one by one:
-
- bingo, I thought. Something is happening with the plugins I’m using (this has been proven to be untrue). Sidenote: the tablet tester shows the same odd input behavior (mouse+pen simultaenously), however I’m not sure if it is intended. Screenshot below.
-
-
As you can see, it’s back to smooth lines but the strokes still simultaenously count as “stylus” and “mouse press”. (Can anyone confirm if this is the case on their end? I don’t have another tablet to test this on
) A bit concerning, but moving on.
Plugins test:
- arrange, reference window, or some other utility in the dir seem to not be the culprits. At all.
Here’s what I found from that check.
The first errors thrown are from Simolette’s layer buttons, and the compact brush toggler.
After closing the errors, the input goes bonkers and that results in the mouse freaking out while I draw with my pen. HOWEVER, the same thing happens when the pair are disabled and I open any canvas.
So, three things to take away from this:
- layer buttons is the main culprit!.. of small unrelated bugs. They seem to have nothing to with this in reality.
- there’s something else going on. This is where it gets even weirder.
- It seems like the tablet tester works fine when I haven’t loaded a canvas. After I open any image or canvas, the tablet tester shows up still messed up. When I close all canvases? Back to normal.
TLDR
Plugins not at fault, the process of opening an image/ a canvas is what borks up the input.
No idea how to progress from here, but here’s all the logs I’ve gathered in 1 pastebin:
FYI, the plugins I’ve seen throw some errors were layer buttons, compact brush toggler, and PET [all 3 I got for some personal tests]. No idea if they corelate to the “crash” reports, but I know they’re not directly contributing to the problem at hand.