Manual processes that work fine for ten assets start failing silently at a hundred. Here is where scale exposes the cracks.
When Manual Works
Manual texturing is the right call when the asset count is low and the assets are mostly hero props, a handful of unique sets, anything where the craft is the point and you'd never want a script flattening your artistic intentions. At ten assets you can hold the whole set in your head, hand-fix an outlier, and re-export without it eating your week. The processes that serve you in the simple situations are also the ones that fail at a hundred.
Where It Breaks Down
Reworking textures at large scale is expensive, and not just the first time you author them. The real cost lands every time something upstream changes. If you switch the method you use to generate AO or normals and, for consistency's sake, you now have to revisit every asset, update it, re-export, and re-validate in-game. Same story if you need to alter the art-style. Do that by hand across a hundred assets and you're not spending an afternoon, you're spending months updating and iterating.
It is easy to miss a few assets here and there. A few assets quietly get missed, bake slightly differently, or drift out of spec, and nobody notices until it shows up in-engine in context, usually next to a correct one where the inconsistency is obvious. Manual work doesn't fail loudly at scale; it just gets a little bit wrong in a hundred places.
What Consistent Scale Actually Requires
The fix isn't "automate everything", that's its own trap (more on that in Day 30 - 💬 Take - Automation). It's consistency first: a defined process where every asset is authored, packed, and validated the same way, so a global change becomes one deterministic operation instead of a hundred manual ones. Only once the pipeline is defined and the edge cases are known is the repetitive part worth scripting.
You can try to 'speedrun' the iteration process but it will catch up to you later, because you simply missed catching the edge cases and how to solve them.
Example
On these bunker environment kits, my tech art director and I spent a few days defining the pipeline: getting the mesh bakes right, testing the system on four assets, locking down the edge cases. Once that was done, we processed 40 asset sets in two-weeks. The consistency we got out of it wasn't just faster than doing it by hand: it was more consistent than hand-authoring would have produced at all.
© 2026 Stefan Groenewoud - All views are my own, not those of my employer.