ART | KJELL EMANUELSSON

[ FRONT PAGE ]  [ 2D PROJECTS ]  [ 3D PROJECTS ]  [ SCRIPTS ] 
[ KEKIT BLENDER ]  [ KEKIT MODO ]  [ IMAGE 2 MESH ]  [ WORLD TEXTURE ]  [ THEME ACCENT COLOR ] 
keKIT FAQ

keKIT [Blender] FAQ


Q: "What is it?"

A: The kit is a collection of my scripts for Blender 2.8+. For people only familiar with the Blender ecosystem & terminology; a "script" is equivalent to a single-purpose add-on, more or less, and the "kit" is a collection of these. An add-on with lots of add-ons, if that helps.
If you are still confused about what "add-ons" & "scripts" are, you should probably not be installing keKit.


Q: "But what does everything do? Where is the documentation?"

A: WIKI


Q: "Can you make voiced video tutorials on the entire kit (& your other add-ons) and suggest workflows?"

A: Probably not.


Q: "Why are you making it?"

A: The primary purpose, for me, is to optimze my workflow (a lot of "click-reduction") whilst also exploring add-on development for Blender, and doing it the way I like it. I don't focus too much on modifier-workflows, as there are already a lot of add-ons that are more focused on those areas (like Hardops, Fluent, Speedflow etc.)


Q: "Did you know this or that add-on has a similar feature?"

A: I do try to just look for other existing add-ons to use at first. Sometimes succesfully, but, sometimes it is not really what I want and I just do my own thing - Usually because the alternative is not exactly right or too complex / clicky (for me)...and sometimes I just fail to find add-ons that might have sufficed.


Q: "Why is it free/donation ware?" (ok I added this, no one ever asked ;> )

A: I'm mostly doing it for myself, but it is nice to see other people finding what you do useful. It is not a commercial project for me, and to be honest I do not want to be beholden to "customers" for the kit. That said, I do appreciate every donation I recieve - it does give me a little extra motivation.


Q: "Will you put it on Github (or similar)?"

A: When I am no longer able or willing to actively develop the add-on, I will be "Open Sourcing" it on GitHub (or similar). It is of course already "open source", but y'know, symbolically.