I can work normally for an hour or so with the same file, after that time I can't use the brush any more (strokes don't show in any layer whatsoever with any type of brush). I can use the brush in a new document and in the "brush setting tool", but the pressure isn't there any more, even if I try to configurate it manually. When I try to go back to the original document that I've been working with the brush still doesn't work... I reopen Krita several times, and reboot my computer...still doesn't work. But casually in one of those reboots it works again (??? :( ) and I can keep working normally... until it happens again... :( Reproducible: Always
Check if you changed anything in the layer settings. Is the layer a paint layer, is it visible and not locked. Is there a selection. If it's limited to one file only then we might need the file.
Created attachment 100369 [details] attachment-4187-0.html Hi, thanks for your answer! When it happened to me the first time I was just simply dranwing and I added a new layer with the icon provided in the menu, I did not change any the settings of the layer. To color the image I'm following a tutorial of how to use G'Mic, so after using the function "split layer" I cannot use the brush over the layers, any stroke/eraser is working over the layers. All layers are visisble and non locked, any selection apply :( . 2016-07-27 22:34 GMT+02:00 Sven Langkamp via KDE Bugzilla < bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=366183 > > Sven Langkamp <sven.langkamp@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |sven.langkamp@gmail.com > > --- Comment #1 from Sven Langkamp <sven.langkamp@gmail.com> --- > Check if you changed anything in the layer settings. Is the layer a paint > layer, is it visible and not locked. Is there a selection. > > If it's limited to one file only then we might need the file. > > -- > You are receiving this mail because: > You reported the bug. >
Check the alpha lock state of the layer after the split. Also make sure that you don't have the group layer selected.
This was also reported by Scott. I cannot find the issue anymore, but it's fixed in 3.0.1, which should be out early next month.