This looks good but again this is a Smear not a blur
This is a Blur brush
Even the Filter Brush Engine krita has does a better job but it is so slow that is not wroth it
This looks good but again this is a Smear not a blur
We are going round and round. It’s already the base behavior of the brush I pointed first:
This is the default behavior.
1 Like
Default Blend Blur
With your shared settings
And we aren’t going round and round, you’re not understanding what im saying when i already explained what the blur brush is here.
And why the color smudge engine isn’t fit for this kind of brush here
There is nothing wrong with the Color smudge engine, its just that it can’t create blur brushes, it is not designed to do that.
1 Like
I’m getting confused by what your definition of blur brush is, by reading this topic. From your first example I’d say Krita is doing a better job than CSP.
2 Likes
@Takiro (sorry I forgot to directly reply to you)
Okay so from what my understanding the blur brush in CSP is basically a brush that applies a gaussian blur to anything under it and the strength of the blur is dependent on the pen pressure.
That’s how I would break down how CSP makes their blur brush
The blend blue in Krita is more like a smear, it drags the color instead of blurring it, it feels more like a liquify push/drag tool now that I’m thinking about it
1 Like
Boro made good videos because of blending brushes are implemented differently. In this video he explains how blending is implemented in krita. Maybe that helps?
2 Likes
Note that I renamed this to just blur engine, as the blending in Krita is better than CSP after I did some tests and pretty much behaves the exact same
Also reminder that blur and blending are different things.
1 Like
Please change it to “Gausian blur brush engine” proper is inappropriate 
2 Likes
Actually yeah that might be better
I agree with this request. There are times when I want a simple gradient that is not affected by unnecessary strokes. That’s what I understood you were saying.
2 Likes
Thank you
I also updated my post to be clearer on what I meant
2 Likes
Refer to this MR: Draft: Add Blurring mode to Smudge Engine (!1460) · Merge requests · Graphics / Krita · GitLab (kde.org)
It is worth mentioning that the mode of CSP is the same as the blurring of paintstorm. They do not blur all dab, but only the first dab.
The remaining behavior is consistent with Krita’s smearing. Therefore, by making some modifications to ‘smearing’, a similar effect to CSP can be achieved.
4 Likes
last update was 3 months ago would be nice to see more updates or have this thing merged before 5.3 
If you need gaussian blur brush then there is already one with exactly that as an option. Have you tried the Filter brush engine? in this brush engine you can paint with any filter of your choice. See for example I am using the guassian blur filter as the brush effect
The brush is called “Filter blur” . I think there should be a request to have values larger than 100 for this filter in the brush settings
4 Likes
No that is not a viable fix, it is extremely slow and not viable for art creation. Krita needs this done proper and this MR seems
to be a proper fix to this. HOPEFULLY, I’m genuinely praying for this to get merged before 5.3 because it is literally ready for merging. Because to be honest the blur brushes in Krita rn don’t suit me and I’m tired of that, Krita doesn’t need to be different, sometimes it needs to be like Photoshop or ClipStudio, I don’t know why that other user insisted on just tweaking the Color Smudge Engine, that won’t achieve the proper blur effect because CSE rn is not designed to handle this kind of brush
I just want a blurring brush that is like the ones seen in ClipStudio paint, clean smooth blur not a smudgy mess
(edited by moderator to remove objectionable word)
2 Likes
look nice but lemme guess, guass filter layer and you are just painting the mask
it looks good but still not ideal
To me, this is closer to ideal than adding a brush engine everytime someone wants a kind of effect on the tip of his brush. Not only that, but I can edit the blur later (value and map), merge it, edit it with curves…
Yeah and it does not go out of the way to be different. For example you can see the shortcuts they are similar to photoshop, see the layer style it is literally copy of photoshop. So it is not that krita tries to be different on purpose. It is different in some areas because of variety of reasons. And many time we have some users coming and telling that krita needs to be a copy just because of that one feature (ignoring all others which the devs worked hard to implement) otherwise it is no good. For you this is the topmost priority for some other something else like clipping mask or text tool may be priority. So whose priority should the devs consider right now considering there are only a handful of them working on krita with very less money? Every one thinks their own request should be top priority.
And nobody is denying your observation or use case. People are trying to help you to achieve what you want right now with what krita has by suggesting a workaround. This is not marked as a solution. You can see your feature request is not closed and has 3 votes which is acknowledgement that this is a feature that is good and needs to be implemented. I do not know who sold you this narrative, but giving a workaround does not mean closing your request and you do not need to convince other people here, they are just users like you, they are not going to implement the feature for you. So stop giving importance to disagreement or suggestions or advice of an internet stranger. Meanwhile some volunteer or dev can take a look at this feature request and may be implement it.
So I get your frustration for this missing feature or behavior but I am frankly tired of this type of posts. You basically want corporate level of paid support for free. Keep in mind krita does not have the resources both monetarily and in terms of manpower of the software you are used to use. So the development is really really slow. You have to take that into account. If you want something right now, you should invest money or effort in it like you invested money and effort for the proprietary software which you used earlier. Or use the proprietary software which gives you all the features you want. At the end of the day why go through frustration and inconvenience.
Even in the MR it only moves forward when the person contributing shows up and asks for updates or is pushing it. They can engage with the developers and push the MR you linked to completion by solving the remaining issue with it. Try to contact them may be pay them to complete this MR
Then pay a developer to implement it. We too want it so it would be great if you act on this urgency.
8 Likes
Excellent response, thank you!
As for getting the new features, that is unfortunately a bit slow. At this point there are many great new additions to Krita that are staged for the 5.3 update, and these major updates don’t happen too frequently.
However, Krita offers two pre-release builds, Plus and Nightly, the last one being the most bleeding edge, a preview of would-be 5.3 (at this time). If there’s a killer feature that you really want, you can use the nightly build, but the catch is that it may be less stable than the current release (some functionality may be broken due to a regression).
If you have the ability yourself, or have an able friend, they could help you create a stable build with a feature back ported, or just they can help pick a good build from the master branch at a time where things are the most stable.
That’s the beauty of open source. At least there is a possibility to solve a problem 
3 Likes