---
Five years ago, I started every character model from scratch. Every single one. A cube, some extrusions, hours of modeling.
Now I can create a unique character in a quarter of the time. Not because I got faster at modeling. Because I built a library.
My base mesh library has saved me literally thousands of hours. But building it the right way took patience and strategy I didn't have when I started.
Start With One Perfect Mesh
The mistake most people make: they try to build their entire library at once.
They model ten different base meshes in a week, each one rushed, none of them properly tested.
Then they discover all ten have problems, and they don't know which ones are actually useful.
Start with one mesh. Make it perfect. Use it on real projects. Find its limits. Fix its problems.
My first library base mesh took me three full days to build and another week of testing and refinement.
That one mesh became the foundation for dozens of successful projects and eventually led to building the rest of my library intelligently.
The Essential First Three
If you're starting a base mesh library, these are the three I recommend building first:
**Average Male:** Medium build, neutral proportions. This covers probably 40% of all character needs.
**Average Female:** Medium build, neutral proportions. Another 40% of character work.
**Child:** Gender-neutral, age 8-10. The remaining character types you can often modify from the first two, but children need their own structure.
With these three meshes properly built and tested, you can handle most character modeling jobs.
Everything else—athletic builds, elderly characters, stylized proportions—can come later as you identify specific needs.
Test Before Adding to Library
A mesh doesn't go in my library until it passes these tests:
**Deformation Test:** Full rig with all major joints. Test fifty different poses. If anything deforms badly, fix it.
**Subdivision Test:** Apply subdivision at levels 1, 2, and 3. Should maintain good form at all levels.
**Project Test:** Actually use it on a real project. Until a mesh has been through production work, you don't know if it actually works.
**Time Test:** Use it for at least three different characters. If it saves time consistently, it earns its place in the library.
I have meshes I modeled that looked great but failed the project test. They're in an "archive" folder, not my library.
Organization That Actually Works
I've tried complicated organization systems. They all failed because I never maintained them.
What works: Simple naming, simple folders.
```
BaseMeshes/
Male_Average.blend
Male_Athletic.blend
Female_Average.blend
Female_Athletic.blend
Child_Neutral.blend
```
Each file name tells me exactly what's inside. No guessing, no opening files to check.
Inside each file, the mesh is named "Base" and positioned at origin. Consistent naming makes appending predictable.
Version Control Matters
When I improve a base mesh, I save it as a new version:
```
Male_Average_v01.blend
Male_Average_v02.blend
Male_Average_v03.blend
```
Why keep old versions? Because I sometimes have projects in progress using older versions. I need to be able to go back if I need to make revisions.
Also, sometimes an "improvement" turns out to not be better. Having the previous version lets me roll back.
Documentation Saves Time
Inside each base mesh file, I include notes:
- Polygon count
- Optimized for what use (games, film, etc.)
- Known limitations
- Date created and version history
This takes five minutes to write but saves confusion months later when I'm trying to remember which mesh is optimized for what purpose.
The Modification Range
Every base mesh has a modification range—how far you can push it before the topology breaks.
My average male mesh can be scaled taller or shorter by about 20%. Beyond that, the proportions look wrong and the topology starts having problems.
I document this range for each base mesh. It helps me choose the right starting point for new characters.
When to Build a New Base
I add new base meshes to my library when I encounter specific needs repeatedly.
After I modeled my third elderly character from scratch, I built an elderly base mesh.
After I modeled my fourth muscular character, I built a muscular base mesh.
I don't build bases speculatively. I build them in response to actual project patterns.
This keeps my library practical and prevents it from bloating with meshes I never use.
The Append Workflow
I don't "Save As" my base mesh files. I append the mesh into new project files.
This keeps the original base mesh clean and untouched. It's always available in its pure form for the next project.
Blender's append system makes this easy. File > Append > Navigate to base mesh > Select mesh > Done.
Library Maintenance
Every six months, I review my library:
Which meshes did I actually use?
Which meshes have I never touched?
Which meshes need updates based on what I've learned?
Meshes I haven't used in a year get moved to an archive folder. They're not deleted, but they're not cluttering my active library.
The Real Time Savings
With a good base mesh library:
- Character modeling time drops by 50-75%
- Consistency across projects improves dramatically
- Rigging goes faster because topology is proven
- Client revisions are quicker because the foundation is solid
The time invested in building the library pays back within months of use.
Starting Your Library Today
If you're reading this and don't have a base mesh library, start now.
Don't try to build ten meshes this week. Build one really good one.
Test it thoroughly. Use it on a project. Refine it based on what you learn.
Then build your second mesh.
In a year, you'll have a library that transforms your workflow. But only if you build it right, one quality mesh at a time.
---