Lesson 10 added atmosphere and motion accents. Lesson 11 is where you make sure the scene still runs cleanly in real gameplay conditions.

What You Will Build

• One LOD rule set for environment modules and hero props
• One draw-call cleanup pass using shared materials and instancing
• One texture memory table for your current scene kit

Step 1 - Capture a Baseline First

Before changing anything, record:

1. Draw calls
2. Triangles in frame
3. Main memory-heavy textures

Use one fixed camera angle plus one traversal camera path so your before/after comparison is honest.

Step 2 - Define LOD Tiers

Set a simple three-tier rule:

• LOD0: close range and hero readability
• LOD1: medium range silhouette preservation
• LOD2: distance fallback for shape recognition only

Avoid micro-optimizing one prop for an hour. You are building repeatable rules for the whole kit.

Step 3 - Reduce Draw Calls Strategically

Focus on the easiest wins:

• Merge material variants when the player will not notice the difference
• Reuse one atlas across repeated prop families
• Replace duplicated meshes with instanced versions where possible

If a prop is unique and always on screen, keep quality. If it is repeated clutter, optimize aggressively.

Step 4 - Review Texture Budgets

Create a quick table with:

• Asset group
• Current texture resolution
• Proposed resolution after optimization
• Visual risk level

In stylized scenes, smart reductions often keep look intact while saving large memory cost.

Step 5 - Validate With Real Scene Movement

Static camera checks are not enough.

Run a short traversal route and watch for:

• LOD popping
• Texture blur on focal assets
• Shader complexity spikes in dense areas

Tune transitions until players cannot easily spot technical swaps.

Mini Challenge

Choose one dense environment corner and hit all three targets:

1. Lower draw calls
2. Lower texture memory
3. Preserve silhouette readability

Document your exact changes so the same method can be reused in the next level.

Common Mistakes

Mistake: Optimizing only hero shots

Fix: Always test gameplay camera routes and interaction zones.

Mistake: Over-merging materials

Fix: Keep separate materials where gameplay readability or key style contrast depends on them.

Mistake: Skipping LOD transition review

Fix: Test transitions in motion and adjust distance thresholds gradually.

Pro Tips

• Keep one "quality lock" list of assets you never aggressively downscale.
• Build an optimization checklist you can rerun every milestone.
• Track performance changes per pass so future edits do not silently undo your gains.

FAQ

Should I optimize in Blender or in engine first?

Do baseline checks in engine first, then use Blender for mesh-level cleanup and LOD prep.

How many LODs do stylized assets need?

For most indie scenes, three levels are enough if transitions are tuned carefully.

Can instancing hurt visual variety?

It can if overused without variation. Use small shader or transform variation to avoid obvious repetition.

Recap and Next Lesson

You now have a structured optimization pass that protects style while cutting technical cost.

Next is Lesson 12: Export pipeline to Unity and Godot, where you lock naming, pivots, and format sanity for clean handoff.