It might be more obvious when you soom in, but I keep getting those “cuts” of sorts, where smooth lines aren’t flowy but kind of… geometric, composed of straight lines.
I tried checking the tablet test, and this is what I got.
Honest to God I’ve no idea what to do with this anymore. I tried the wintab settings, turning smoothing on/off, changing acceleration, different canvas sizes, etc. I’ve never encountered this before so I’ve no idea how to approach this.
Let me know if I can provide any more useful logs etc.! Like I said, idk what’s the cause of all this so no idea what files I should attach.
EDIT: no idea what changed, but now I can’t use my mouse at the same time that I’m using the pen. This sucks, cause I use one to move around + for macros, while the pen stays for the eraser/brush switches and, drawing. duh.
It looks like in the midst of drawing with the stylus it suddenly gets recognition as a mouse and that makes these jumps, but I have no idea what could cause this.
Something to try would be to uninstall the driver, do a full power down restart, then install the latest driver in accordance with the Huion instructions, then do a full power down restart again.
Will try this out tonight/tomorrow, and see if that fixes things.
Will also add the version of drivers that this has happened on, as I forgot to add that info in the post (mea culpa)!
Some additional, (maybe) helpful info:
I use a dual-monitor setup, with the display tablet being marked as the “2nd” screen (otherwise some things sort of break; it’s complicated).
As of writing this, there’s no special pressure curve setting I’ve used on both Krita & the drivers.
I tried fiddling with the max speed in Krita, but no luck there.
I do use a fair share of assets & plug-ins in my workflow (could they interfere in any way?..) On top of that, I have used the Spectral build for Krita before, but in this case this is just the normal 5.3 build with 0 changes;
I can’t really check if the display has the same behavior on other machines, cause my only linux machine has 500 mb of ram
This for sure isn’t a memory issue either as I have 40 GB of ram, and Krita has a lot of wiggle room there
That’s all off the top of my head. Will edit this post with my findings post-reinstall!
Alright, gave your solution a go @AhabGreybeard and… tough tiddys. No luck.
I’ll see if maybe uninstalling the nightly and reinstalling 5.2 will do some good, since I tried PTS, CSP, and Affinity to see if anything similar happens – nope, just Krita.
Still the same issue, with the same looks. I’m genuinely bewildered, but if there’s anything else I can do to help identify what is causing this, please let me know!
As an aside, this is about the only way I can help out the dev team at the moment, so this is sort of a double whammy of me needing help and wanting to contribute in some way. Genuine apologies if this is a bit too much!
It’s the tablet position reporting rate being too slow to properly follow the details of the curve when the stylus is moved quickly.
Have you drawn rapid curves before with no problems?
Is the problem still there if you draw slowly?
I must’ve mixed something up, as I was pretty sure I saw that winink had to be ENABLED on wintab – my bad!
Although, even with it disabled and a Krita profile being set up in the config, this does not help this specific problem.
Furthermore: this isn’t a speed issue. I just used the faster loops to show precisely what happens when I do quicker, expressive strokes, but although this is much less pronounced on slower stroke, the same thing happens:
Both were done slowly, with just about my normal drawing speed. It’s more pronounced in the second pic, but I think it’s as @Takiro mentioned – the mouse and tablet inputs are overlaid over one another, with the red being pointed in the log as “mouse” and blue as “tablet”:
This is a part of the tablet tester log from the 2nd picture. The stylus movement is precise and there’s no surprises, artifacts, nor input lag/offset there – but on the mouse, there it is!
Like I said, this is my first time seeing such a thing happen which is why I’m so confused! I had a Huion 1060 before, and an old Wacom Bamboo before that, and this has never happened in any software I’ve used (which is quite a lot by now, but still – consider my mind boggled)
I don’t have a Huion and don’t know what settings the driver offers, has it something like a mouse emulation mode or do you work in relative pointer device mode or something?
But I’m pretty sure that it’s because both inputs happen simultaneously and Krita is either switching between them rapidly or can’t keep up with them, hence the strange lines.
If the mouse and stylus position are accurate on the canvas and can also be used to operate the surrounding GUI items, then I’m mystified as to what could be going wrong.
Have you done the driver uninstall then reinstall (or install new/latest) driver thing yet?
Precisely!
The GUI navigation has no problems, the mouse on itself operates just fine, but when I pop the tablet into the equation, everything goes out of wack.
Have you done the driver uninstall then reinstall (or install new/latest) driver thing yet?
The reinstall didn’t help, and I already have the latest update for my model, which is the 15.7.6 one. Going to head to bed now, but I’ve tried just about any common solution I could find for Huion tablets; but maybe I missed something and just need to clear my head first.
Things I’ve tried so far:
changing builds from 5.3 to 5.2.6
reinstalling the drivers
setting up Windows Ink
restarting my computer, with long waits in-between
about every setting in Krita’s tablet settings (except changing the speed/smoothing; I fiddled with it to try it in 10 step increments when I initially couldn’t point towards what the problem is, but gave up as it didn’t help at all)
Things to maybe try/do:
removing plugins one by one and seeing if there’s something up there
see if I can grab all the logs for documenting this properly, with the exception of the tablet tester
see if MyPaint behaves in a similar way, maybe?
What is 100% NOT the problem:
any of the settings inside Krita’s tablet section - none of them yield any results
memory, cpu - >30 GB of ram should be able to run just about anything, while I didn’t notice anything off in terms of performance in general
canvas settings - tried smaller canvases, different color spaces, depth, one layer, multiple layers… no luck there either
old tablet/ loose cords/ other hardware issue - the display is still relatively new, and I don’t have this problem in any of these: SAI, Affinity, ArtRage, Rebelle, CSP, Drawpile, MS Paint, AzPaint
Huion driver settings - tried just about any combo of settings I could, with and without admin priviledges
With this in mind, I’m heading straight to bed and will update this thread tomorrow; unless someone comes up with a better idea, for now I’ll stick to testing the plugins and grabbing all the available logs. Goodnight!
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.
Seeing two lines, red and blue is normal. I’m getting a similar log. I can’t check now, but I think it mentions the mouse as well. It’s fine.
Can you check the device on another PC, laptop? That way you could test a completely fresh install without risking breaking your configuration. It can be backed up, but just using another system will be safer.
That reminds me, I can try asking my brother for help in this. It’s gonna be a bit of a bother, but worth a try nonetheless!
still, it’s just so weird since this is only happening in Krita and specifically only when a canvas gets opened. One of the first things I tried was removing any trace of Krita from the system that I could find, then a re-install, but that didn’t solve my issue. Maybe trying another PC is the way.
I think I included all the needed info about my hardware in the pastebin, but if I missed something do let me know! I’m just a tad woozy and tired and wish I could just draw already
Also! Just spotted you’re a fellow pole. Hi there!
Krita has various configuration files and directories on the system and it may be difficult to get all of them. My expectation is that this is a problem of your settings and plugins getting out of whack, if the tablet and pen work fine in other applications.
The fact that the problem happens only with the canvas opened does not surprise me. Most plugins will activate only at that time.
From today’s updates, I’m temporarily out of luck. I don’t have the proper cables to connect to another pc [it’s complicated] so for now I’ll have to stick to other software : -((
On top of that my whole family’s sick, so I can’t really drive anywhere to get a set of cables faster. It is what it is, so for now I’ll just put this aside – temporarily.
Sorry to hear. Cables are tricky. I had very limited success trying to replace or extend a display tablet cable. Maybe it was extra difficult because it was 4K. At any rate, there’s a high chance a non original cable won’t produce output signal.
Decided on a weird workaround of the cord issue, and just made a virtual machine running win11. Already had VBox laying around. Shoddy workaround, but “it just works”.
Boom. Something’s up with my Krita installation, cause the tablet works fine on the VM. Pressure included.
So… how would one go about removing any traces of Krita for a truly clean re-install? Before this I only re-installed with the default uninstaller, and deleted the contents of the Appdata/Roaming folder. Maybe I left something over by accident or something, I’ve no idea. I’m not as well-versed in whatever happens in Windows so this has been a truly wild journey.
SMALL EDIT: I copied the contents of pykrita/all my bundles, and checked if anything inside of them is the root cause of this. Apparently: YES. It’s one of my plugins, possibly some leftover from an older installation, since this is not really a fresh and new PC. God bless you all cause I wouldn’t have any idea how to progress with this, and I’ll get to checking what it was. I’ll edit this post when I get to it. o7
Caught it.
It was nothing that I expected, and instead, it was the Custom Preview that was causing all this fuss.
My main mistake: I’d remove the plugins, instead of disabling them in Krita’s settings. Apparently plainly removing things from the pykrita dir is not the first step – my bad. At least I got to the solution. Big thanks for all of your help, genuinely. orz
Regarding the plugin, I’m not sure if it offers any additional features, but the small preview of your image is now a baseline function of Krita called the Overview docker.
I’m not super happy about how it works (it’s tuned for minimal overhead), but it’s there to use.
) A bit concerning, but moving on.
