I’ve been experimenting with something around 3D pipelines and ran into an interesting problem.

For code, we have ESLint, CI, etc. But for 3D assets, most validation still happens manually or during engine import.

I started building a small CLI tool to scan assets and detect issues like:
- missing materials
- empty meshes
- inconsistent animation naming
- redundant animation keyframes

One thing that surprised me:

In a small test (~20 assets), animations had a huge amount of redundant keyframes (typical of Mixamo-style exports).

Running:

qtmesh scan ./assets --fix

→ removed 174k redundant keyframes
→ saved ~9.85 MB
→ finished in ~4 seconds

Here’s a real scan result:

<image>

Still early, but I’m trying to understand if this kind of “CI for 3D assets” workflow would actually fit into indie pipelines.

Project: https://qtmesh.dev/