https://bugs.kde.org/show_bug.cgi?id=440740
Bug ID: 440740 Summary: Changing any attribute of a brush that uses texture patterns, can cause the brush's pattern to reset to the "01_canvas.png" pattern Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: brightpiepomegran...@protonmail.com Target Milestone: --- Created attachment 140587 --> https://bugs.kde.org/attachment.cgi?id=140587&action=edit gif that shows the bug SUMMARY When an attribute is changed on a brush that uses texture patterns, for example the brush tip size or rotation, the texture pattern can reset to the "01_canvas.png" pattern. This is also the first pattern indexed in Krita. I don't experience this bug happening with every brush that uses texture patterns. Such as the watercolor brushes or rgba brushes With texture brushes affected by this bug, opening the brush editor and opening the pattern selector shows that the "01_canvas.png" pattern is already selected. Even if the brush uses a different pattern by default. If a brush present is cloned from the affected texture brush, the new clone brush will be affected too It can go away by restarting Krita. But the next time Krita is opened it will come back. Before testing this I deleted my resource folder. The brushes I tested were default brushes. The default texture brushes that I observed were affected by this bug were 1.h)Chalk Details 2.g)Dry Brushing 3.i)wet textured soft 4.k)Blender Textured Soft 5.y)Texture Wood Fiber STEPS TO REPRODUCE 1. Select a affected texture brush like "h) Chalk Details" 2. Edit any attribute of the brush in the brush editor OBSERVED RESULT The brush will reset to the "01_canvas.png" texture pattern EXPECTED RESULT The texture doesn't change unless the user selects a new texture Experienced this bug in Windows and Linux SOFTWARE/OS VERSIONS Windows 10 Linux ADDITIONAL INFORMATION Tested with krita-nightly-x64-5.0.0-prealpha-0ac7ece6ae and a older Krita nightly from June. Krita 4.4.5 doesn't appear to have this bug. -- You are receiving this mail because: You are watching all bug changes.