Created attachment 129684 [details] glitch_while_painting SUMMARY There's a weird glitch that occurs with Krita's rendering engine while/after you paint a stroke. Krita version is Krita Plus and version is 4.3.0-beta2(4.3.1-alpha git 5e750f3) STEPS TO REPRODUCE Unsure but I believe steps are as follow : 1. Have a big brush(200 pixels or more) 2. Have multiple raster rectangles in a group(maybe in white color) 3. Set the group layer style to stroke(mine was center stroke mode) 4. Paint around the borders of the rectangles, where the rendered stroke is visible. OBSERVED RESULT The brush temporarily erases the stroke rendered by the layer style and sometimes, an thick intruding pixel line appears here and there. EXPECTED RESULT No glitch at all SOFTWARE/OS VERSIONS Windows 10 1909 Krita Version: 4.3.1-alpha (git 5e750f3) Languages: en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.18363 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (NVIDIA GeForce GT 640M Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 3.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true Hardware Information GPU Acceleration: angle Memory: 12126 Mb Number of Cores: 4 Swap Location: C:/Users/Yed/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/Yed/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 400 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 300 Use Backup Files: false Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: true Use Zip64: false Display Information Number of screens: 1 Screen: 0 Name: \\.\DISPLAY5 Depth: 32 Scale: 1 Resolution in pixels: 1600x900 Manufacturer: Model: Refresh Rate: 60
Does it happen in Krita 4.3.0 or just in the Krita Plus? Also what is the exact color space of that image? Would be actually best if you could provide a .kra file and maybe either a brush preset or say which one of the default ones at which size and which layer creates this issue. I, while the artifacts while painting and general performance was awful, couldn't reproduce the issue.
Setting to Needs Info.
Here's a file for inspecting the issue. By the way, it happens mostly while using Eraser mode. On Mon, Jul 27, 2020 at 10:31 PM Tymond <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=423520 > > Tymond <tamtamy.tymona@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Keywords| |triaged > Status|REPORTED |NEEDSINFO > > --- Comment #2 from Tymond <tamtamy.tymona@gmail.com> --- > Setting to Needs Info. > > -- > You are receiving this mail because: > You reported the bug.
(In reply to Tymond from comment #2) > Setting to Needs Info. (In reply to Tymond from comment #1) > Does it happen in Krita 4.3.0 or just in the Krita Plus? Also what is the > exact color space of that image? > > Would be actually best if you could provide a .kra file and maybe either a > brush preset or say which one of the default ones at which size and which > layer creates this issue. > > I, while the artifacts while painting and general performance was awful, > couldn't reproduce the issue. (In reply to stephen from comment #3) > Here's a file for inspecting the issue. > By the way, it happens mostly while using Eraser mode. > > On Mon, Jul 27, 2020 at 10:31 PM Tymond <bugzilla_noreply@kde.org> wrote: > > > https://bugs.kde.org/show_bug.cgi?id=423520 > > > > Tymond <tamtamy.tymona@gmail.com> changed: > > > > What |Removed |Added > > > > ---------------------------------------------------------------------------- > > Resolution|--- |WAITINGFORINFO > > Keywords| |triaged > > Status|REPORTED |NEEDSINFO > > > > --- Comment #2 from Tymond <tamtamy.tymona@gmail.com> --- > > Setting to Needs Info. > > > > -- > > You are receiving this mail because: > > You reported the bug. Sorry. Link to the file here : https://gofile.io/d/dBNHSm
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
I cannot reproduce it :( Does it happen with other brushes or just that one you were using? Could you please check if it happens in 4.3.0 from the website? Also could you please check if it goes away if you go to Configure Krita -> Display -> change Renderer - and restart Krita?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Tymond from comment #6) > I cannot reproduce it :( Does it happen with other brushes or just that one > you were using? Could you please check if it happens in 4.3.0 from the > website? > Also could you please check if it goes away if you go to Configure Krita -> > Display -> change Renderer - and restart Krita? Using the Krita Plus Stable Build version 4.4.0 alpha(git 7973cb6), the bug seems to be absent. I wasn't able to reproduce it in this one version. But in 4.3.0, it happens. And it happens with any type of brush. Changing the renderer didn't really fix things. And also, it happens on random ways. Some moment, the glitch occurs. Then it doesn't anymore after some time...
(In reply to Tymond from comment #6) > I cannot reproduce it :( Does it happen with other brushes or just that one > you were using? Could you please check if it happens in 4.3.0 from the > website? > Also could you please check if it goes away if you go to Configure Krita -> > Display -> change Renderer - and restart Krita? Aha ! The glitch is still there. But it appears when you apply a layer style to a group of layers instead of a layer alone... I hope you can reproduce it with these instructions : 1. Have at least two layers. One will serve as base for a clipping group: You may use a portion of pixels filled with a color using the rectangle selection tool and the fill tool. 2. Make a quick group from these two layers, and use alpha inheritance for a clipping group effect 3. Apply a layer style to the group of layers(mine was stroke of about 8 pixels weight, and set to inside; blending mode is normal and opacity at 100 %.) 4. After the style is applied, paint on the layer which inherits the alpha from the bottom most layer in the clipping group. You'll notice that the glitch occurs when you paint around the edges of the rendered stroke from the layer style. Hope this helps.
(In reply to stephen from comment #9) > (In reply to Tymond from comment #6) > > I cannot reproduce it :( Does it happen with other brushes or just that one > > you were using? Could you please check if it happens in 4.3.0 from the > > website? > > Also could you please check if it goes away if you go to Configure Krita -> > > Display -> change Renderer - and restart Krita? > > Aha ! The glitch is still there. But it appears when you apply a layer style > to a group of layers instead of a layer alone... > I hope you can reproduce it with these instructions : > 1. Have at least two layers. One will serve as base for a clipping group: > You may use a portion of pixels filled with a color using the rectangle > selection tool and the fill tool. > > 2. Make a quick group from these two layers, and use alpha inheritance for a > clipping group effect > > 3. Apply a layer style to the group of layers(mine was stroke of about 8 > pixels weight, and set to inside; blending mode is normal and opacity at 100 > %.) > > 4. After the style is applied, paint on the layer which inherits the alpha > from the bottom most layer in the clipping group. You'll notice that the > glitch occurs when you paint around the edges of the rendered stroke from > the layer style. > > Hope this helps. THE GLITCH ALSO OCCURS IN A MORE OBVIOUS MANNER WHEN THE BRUSH SIZE IS GENERALLY BIG(>=300 pixels).
a) There's no need to quote quite so extensively b) There's no need to shout
Created attachment 131101 [details] attachment-16165-0.html Sorry. On Aug 22, 2020 15:54, "Boudewijn Rempt" <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=423520 > > Boudewijn Rempt <boud@valdyas.org> changed: > > What |Removed |Added > ------------------------------------------------------------ > ---------------- > CC| |boud@valdyas.org > > --- Comment #11 from Boudewijn Rempt <boud@valdyas.org> --- > a) There's no need to quote quite so extensively > b) There's no need to shout > > -- > You are receiving this mail because: > You reported the bug.
Hi, stephen! I tried to reproduce the bug today, and it seems like it got fixed in the meantime. Actually, I did quite significant changes to the strokes style that should have fixed it.