Is it possible to make a brush to detect how fast you lift the pen off the tablet to decrease it's size? Basically when you start drawing the line thickness will be constant until you quickly lift the pen off the tablet which causes the line to get smaller and eventually have a size of 0, making the line "fade out". I was told that Photoshop has this feature in the basic brush and having that feature would be needed right now (I actually did test the brush in Photoshop (which I don't own myself) and it seemed to work as I was told).

No, but neither does photoshop as far as I know. : / (It only has pressure affecting size, but not pressure-release-speed affecting size, just like Krita)

If it does I am curious what they call it.

We do have regular pressure sensitivity, like for the fill-circle and the inking brushes.

Edit: Sorry, I am misinterepreting what you are asking because release-speed is different from just 'pressure-sensitivity', and you just mean the latter. Yes, Krita does have it. Fill_circle, and Ink_Brush_25 have it amongst others.

Well, it seems I can make a brush stroke that is what I want with the pressure alone, but I have to do really awkward motion and it rarely works. In Photoshop it worked almost every stroke :/

awkward motion? what do you mean?

there's, btw, a brush stablizer for the freehand brush that smooths brush pressure as well?(it's in the tool options)

It's kinda hard to explain. Also, I do know about the stabilizer, but it doesn't really help with the result I'm going for.
Here are some brush strokes I made (all are from left to right). The one circled with red is closest to what I want.
http://i.imgur.com/1k9KFgp.png

EDIT:
Here is a picture my friend made of what I'm trying to do. I can do pretty much everything else here except for the correct brush stroke. You can see that the brush strokes go to the direction of the fur (Yes, it's a tail, I just don't know why it's green)
http://i.imgur.com/fopjEdc.jpg

Ah!

I got it:


Basically, set the size to fade or distance. (Fade being proportional to the brush size, distance being raw pixels)

Here's the preset btw: https://share.kde.org/index.php/s/Z38I8OsqrlACOYH (and here's a super-spikey version)
And this is a manual page that shows other things you can do with fade/distance: https://docs.krita.org/Brush-tips:Fur

That works. Thanks. Even though I can't control when the "spike" comes to the end of the line like I could in Photoshop (at least not very easily as I need to adjust the length every time I want a different length spike).

Though, now I'm experiencing issue where the pointer doesn't follow the pen movement unless I draw. When the spike ends, the pointer will stay there until I start drawing again. Is there anything I can do about this as it makes drawing really difficult when you can't see where you're starting to draw?

That... is probably a problem with your drivers.

1. Did you turn on/off opengl? (settings->configure Krita->Display)
2. Which graphics card do you have?
3. Which version of windows do you use(or OSX, or Linux)?
4. Which tablet do you use?
5. which version of Krita are you using?

Like, for example, the surface pro's Ntrig wintab drivers don't update the mouse-position properly, leading to the cursor not moving. Similarly, if you have OpenGL turned off, the canvas doesn't update proper unless you draw. Then there's some graphics cards that just won't cooperate due to faulty drivers either.

1. Tried turning on and off but didn't help (It was on by default)
2. NVIDIA GeForce GT 620
3. Windows 7 Home Premium (64 Bit)
4. Wacom Intuos CTL-480
5. Version 2.9.9 (git 22f7b3b)

It's kind of weird that this issue appeared when I turned 'fade' on :/

Does it only happen with fade(so if you turn fade off, does it work normally again?)

Could you try out if 2.9.11 has it too? (We fix a bunch of bugs and make a release every month, so it may have been a fixed bug)

Yeah, when I disable fade it works normally. I tried updating too, but it still happens in the newest version :/

It then might be a windows only bug. I can't reproduce it here on Linux. You can report it at bugs.kde.org, so that we can tackle it during our bug-squashing month.