How Tenjisoft Production Works: From Ideas to Final 3D Assets

1) Idea Generation & Planning

We begin with focused brainstorming that weighs creative ambition against production reality. Each idea is scored against factors that directly impact success and scope.

• Demand & Audience Fit: What players want right now; how the asset supports gameplay or narrative.
• Requirements: Client brief, style guides, poly/texture budgets, LOD needs, collision and lighting constraints.
• Difficulties & Risks: Complex shapes, rigging dependencies, shader constraints, tight deadlines.
• Platform Targets: PC / Console / Mobile performance budgets; engine specifics (Unreal/Unity).
• Reusability: Modular design for packs; kitbashing opportunities.

2) Reference Collection (with AI boost)

Credible references keep designs grounded. We compile moodboards from Pinterest, Google Images, ArtStation, on‑site photos, and our in‑house libraries. AI assists discovery—uncovering variations and edge cases that sharpen decisions.

• Breakdowns by silhouette, material, color, scale.
• Validation against engine constraints and art direction.
• Quick reference bibles for the entire team.

3) Concept Art: Sketches, AI Enhancements & Paintovers

With references set, our concept artists explore silhouette readability through thumbnails. We use AI to iterate on forms and materials at speed, then perform artist paintovers to lock style, proportions, and story cues. This hybrid method keeps us fast without losing authorship.

Deliverables include callouts for materials, wear, decals, and any functionality that will matter to modeling or rigging. Once approved, we greenlight production.

4) 3D Modeling & Technical Optimization

Our 3D team builds with intentional topology and engine-aware targets. We block out forms, add high‑poly detail where it sells the read, then create clean low‑poly meshes via retopology. UVs are organized to maintain consistent texel density and efficient packing.

• LOD strategy aligned with platform budgets.
• Collision, sockets, and pivot conventions set early.
• Checklist for shading issues (normals, smoothing groups, cage/bake sanity).

5) Visual Development Before Texturing

To avoid wasted time, we run look tests before texturing. Clay and greybox renders confirm silhouette readability. We light assets to representative scenarios and evaluate scale cues, secondary forms, and focal hierarchy. Any issues are solved here, not after materials are painted.

6) Texturing, QA & Final Delivery

We bake normals, AO, and curvature, then author PBR materials (Substance workflows) that mix smart masks with hand‑painted touches. A QA pass verifies performance budgets, memory footprint, and consistency across LODs. Final packages include source files and engine‑ready exports with documentation.