Guys, I colorized thorugh coloring tool, I converted my colored layer to a painting layer and tried to split it (or divide, sorry my Krita is in spanish), Krita aparently is running, the bar is 100% but Krita just stays idle, no new layers, had to force shutdown, tried three times with different palettes but to no avail, I think I have a decent pc, I'm working on a paid commission, is Krita not ready to do pro work? please help!!!

UPDATE: Turns down that Krita did finish creating layers after ten or so minutes, but it turned a flat coloring of 20 colors into a 100 layers behemoth (2 GB of layer data) some layers were simply pixels, I still don't have a clue of what happened, I've been a Krita user for 3 + years, maybe it's time to finally give in to photoshop?

My rig: Windows 10, ryzen 7 3700, 32 gb ram, rtx 2060 super video card

Update to the latest beta. The default value for precision in split layers was too high which meant too many layers were created.

Thank you, I manually fixed everything, sorry if i'm being too naggy, i was desperate, you are always so helpful, good to know krita has such agreat community

boudewijn wrote:Update to the latest beta. The default value for precision in split layers was too high which meant too many layers were created.

Hi, I do have the exact same problem with version 4.4.1 and with the most recent Nightly version. Any way workaround for this?

Cheers

Just make the precision value much lower and check if it helps?

tymond wrote:Just make the precision value much lower and check if it helps?

Thanks for your reply. I appreciate it. I'm new with Krita and I don't seem to see a precision value option in the split layers menu. There's the fuzziness option that is defaulted to 20 and even if I bring it down a lot, it doesn't get the wanted resulted.

Could you please tell me where the precision value is?

cheers

Looks like the relevant commit wasn't backported to the 4.3 branch because of a conflict. I'm looking into that now.

boudewijn wrote:Looks like the relevant commit wasn't backported to the 4.3 branch because of a conflict. I'm looking into that now.

Thank you so much.