FA+
Shop
A filthy rat's diary 2: Learning CSP and complete awootis...
3 years ago
So i've been hopping between digital painting software a bit. My last few pictures were in Krita, but it fails completely with big projects (eats up more RAM than google chrome). I've never really learned any single software like I think I should, so I've been mostly trying to find my way blindly in the dark.
I need to change that.
A few people recommended CSP to me so I've checked it out. Sure looks like good software, has a few interesting features. Not a massive, discouraging monolith like photoshop, that's for sure.
CSP, like most software these days, has tons of functionalities I simply do not need. I don't care about animation for now and a bunch of other stuff. I don't want to waste my time and energy to learn stuff that I don't need, and separating those functions that I need is already a problem for me. When a tool is multi-purpose and there are not very clear and very hard lines separating those purposes then you can get easily overwhelmed.
But, as usual, there are no good tutorials. And you may disagree with me, but I just HATE tutorials in video format. I cannot follow them, most of the time people keep rambling and get to the point slowly af. Sadly, the era of written tutorials is gone, and very rarely I can dig up a good written tutorial for stuff I want to learn anymore.
Usually in those cases I resort to reading the software documentation, but the CSP documentation is bad. Not abysmal, not horrible, just plain and simple bad and inconvenient to read and sift through.
So I've decided to do what I do best: solve the issue my own way, which always requires almost non or all of the work. In this case the latter. I'm sorta writing my own documentation for CSP.
I've written down all the functions and things you can open within Krita. Menus, tools, actions etc. Now I'm slowly describing them, starting with the most important (for me) parts of the program. I'm using both the documentation and other sources to do it well.
When I'm done I will definitely make this public in hopes it helps similar-minded awootists like me xD
I need to change that.
A few people recommended CSP to me so I've checked it out. Sure looks like good software, has a few interesting features. Not a massive, discouraging monolith like photoshop, that's for sure.
CSP, like most software these days, has tons of functionalities I simply do not need. I don't care about animation for now and a bunch of other stuff. I don't want to waste my time and energy to learn stuff that I don't need, and separating those functions that I need is already a problem for me. When a tool is multi-purpose and there are not very clear and very hard lines separating those purposes then you can get easily overwhelmed.
But, as usual, there are no good tutorials. And you may disagree with me, but I just HATE tutorials in video format. I cannot follow them, most of the time people keep rambling and get to the point slowly af. Sadly, the era of written tutorials is gone, and very rarely I can dig up a good written tutorial for stuff I want to learn anymore.
Usually in those cases I resort to reading the software documentation, but the CSP documentation is bad. Not abysmal, not horrible, just plain and simple bad and inconvenient to read and sift through.
So I've decided to do what I do best: solve the issue my own way, which always requires almost non or all of the work. In this case the latter. I'm sorta writing my own documentation for CSP.
I've written down all the functions and things you can open within Krita. Menus, tools, actions etc. Now I'm slowly describing them, starting with the most important (for me) parts of the program. I'm using both the documentation and other sources to do it well.
When I'm done I will definitely make this public in hopes it helps similar-minded awootists like me xD
