Lesson 11 made your environment cheaper to render. Lesson 12 makes it safer to hand off. You now lock a pipeline so every export lands in Unity or Godot with the right scale, pivot, and material expectations.

What You Will Build

• One reusable naming standard for meshes, collisions, and material slots
• One pivot placement rule sheet for modules, props, and hero pieces
• One export validation checklist for FBX and glTF handoff

Step 1 - Lock Naming Before Export

Set naming by asset role, not by mood or memory.

Use a simple pattern:

• env_wall_straight_a
• env_floor_corner_b
• prop_lantern_hanging_a

Keep names lowercase, consistent, and sortable. This makes prefab replacement and batch operations much easier in both engines.

For collision helpers and utility meshes, keep clear prefixes so imports remain predictable.

Step 2 - Standardize Pivots by Purpose

A clean pivot policy prevents snapping pain and broken placement scripts.

Use these defaults:

1. Modular walls/floors -> pivot on grid-friendly corner or bottom center
2. Interactive props -> pivot where rotation should happen in engine
3. Set dressing clutter -> bottom center for fast placement

Apply transforms in Blender before export (Ctrl+A) so location, rotation, and scale are stable.

Step 3 - Choose Format Intentionally (FBX vs glTF)

Both work, but choose based on your target.

• FBX: common for legacy or animation-heavy Unity/Unreal pipelines
• glTF: strong for modern PBR-friendly transfer and cleaner data flow

For this course pipeline, run a smoke export in both formats once, then pick one primary path per asset class.

Step 4 - Run a Unity and Godot Smoke Import

Import one wall, one floor tile, and one prop into each engine.

Check:

• world scale matches your intended unit size
• pivots snap and rotate as expected
• normals and shading look consistent
• material slot names map cleanly

Do not continue mass export until this triad passes.

Step 5 - Build an Export Validation Checklist

Create a short checklist you run every batch:

1. Naming matches convention
2. Transforms applied
3. Pivot reviewed
4. Export preset selected correctly
5. Engine smoke import verified

This checklist is your guardrail when deadlines get noisy.

Mini Challenge

Export three kit assets (wall, floor, hero prop) through your finalized pipeline and import into both Unity and Godot.

Pass criteria:

• snapping works without manual offsets
• no unexpected scale multipliers
• no missing material assignments

Common Mistakes

Mistake: Fixing pivots only after import

Fix: set pivots in Blender by asset role before first export, then keep them consistent.

Mistake: Mixed naming styles across lessons

Fix: keep one naming map in repo docs and enforce it on every new asset.

Mistake: Switching format mid-production without tests

Fix: if you change FBX/glTF strategy, rerun smoke tests and update presets immediately.

Pro Tips

• Save export presets in Blender and version them like code.
• Keep one reference measurement object (for example 1m cube) in test scenes.
• Add a quick import QA scene in each engine so artists can self-verify before merge.

FAQ

Should I use FBX or glTF for everything?

No. Pick per asset type and engine behavior, but keep decisions documented and consistent.

Why do pivots matter so much for environment kits?

Bad pivots break snapping, rotation logic, and placement speed, which slows every future iteration.

How often should I run smoke imports?

At minimum for each new asset class, export preset change, or engine version update.

Recap and Next Lesson

You now have a structured handoff pipeline from Blender to Unity and Godot with naming, pivot, and format checks that reduce rework.

Next is Lesson 13: in-engine shader and post setup, where you match your Blender look to runtime lighting and final presentation.