I prefer “Textured Flat”, not dappled or mottled, since it is only brush with Pattern\texture effect, which is unique things for digital painting – painting with texture (rock, wood, canvas, dirt and any other similar things), but not a solid paint.
3 Likes
All the brushes in the set are textured though. 
How about “Flat Rough”?
Personally, I would condense the ‘memileo Impasto’ part down as much as possible. Keep the full version to the tag and just use an abbreviation for the individual presets e.g. mem 01 Brush - Flat Tip
I mean; It’s not needed at all if the user is within the tag set, but a unique header does help maintain grouping when in the full brush list, or a user curated set.
My reasoning is that the most important part is at the end of the description, but would be cut off in many setups due to limited docker width.
4 Likes
I meant visually distinct nonuniform texture. Almost all other brush at previews tends to solid stroke.
Actually it doesn’t much matter since any user can rename brush for they convenience.
Also agree with Mythmaker - first part is too long.
1 Like
@Mythmaker Good point. I’ll remove the ’Impasto’ part but think I’ll keep ‘memileo’ in full to have it consistent with my previous bundle. (Otherwise ‘memil’ or ‘leo’ would work.) Is 33 characters short enough for your setup?
My bad. Here’s what the brushes look like with light pressure:
11 Likes
12 Likes
1 Like
Beautiful work, @Lonkom. Welcome to the community.
1 Like
Thanks
1 Like
“Fallen Angels”, a beautiful movie.
1 Like
these look so awesome, can’t wait to use em
1 Like
It’s a good brush pack, but there is a problem when using them: as you select and use them, they generate an uncontrolled accumulation of memory, and even when you deselect them, the software doesn’t seem to be able to properly free up the memory. Some are worse than others in this regard. Notably, this correlates with the texture complexity of each brush, and on a more technical level, I suppose this is related to poor or non-existent optimization for older drivers and devices, whether GPU or onboard graphics chipsets. I assume that for certain more modern drivers or types of GPUs—depending on how or which resources, scripts, and libraries the pack uses (assuming some programming was done, perhaps in Python)—the problem may not occur. However, I also believe there is a non-zero probability that similar issues could occur even on computers with newer hardware that don’t meet the exact driver conditions. I don’t know who the creator or developer of this pack is, nor how much time or resources they have available to create or fix this pack, but I believe it’s important to inform them that this condition is real and exists as incorrect memory allocation behavior. This is not behavior I observe in any other brush pack available for Krita, even packs considered heavy, such as those involving impasto like the Krita RGB Brushes, etc. So I believe the community should simply be aware that this happens. I suggest this be fixed in some way.
The older and the newer versions of these brushes all crash my computer (Ubuntu studio desktop on a 5 year old Intel Core I5 using KDE and Wayland). I don’t know how to tell if it is the memory error that @Amon_Ra refers to, but the behavior is consistent with that.
I love the brushes and wish this could be fixed. I hate losing my art-in-progress so I don’t use them.
Did you try the lighter version of the bundle that I referred to (above your post)? Just wondering if it would work in your case. 
I have tried three versions and they all caused my computer (not just the krita app) to stop responding, requiring a reboot. I think there were two from an earlier release: a regular version and a performance version. I also tried the latest. I know they work for some people, but my hardware and os are not the most common
The one I was referring to is called “memileo_360light_06_Performance_01.bundle”. I guess you did try this one. Sad that it hadn’t worked for you. 
There are other impasto brushes to use though. Hopefully, you can do that.