Lesson 13 locked your in-engine look. Lesson 14 makes that work presentable. You now build a small presentation pipeline so your environment reads clearly in screenshots, short reels, and portfolio reviews.

What You Will Build

• Three hero screenshots with intentional framing and lighting readability
• One short turntable clip showing model quality and silhouette consistency
• One annotated breakdown image highlighting reuse, texel strategy, and shader decisions

Step 1 - Define Three Portfolio Cameras

Pick three fixed cameras before you start rendering:

1. Hero wide for composition and scene mood
2. Mid shot for modular kit readability
3. Close detail for material and edge quality

Lock focal length and framing per camera. Do not keep adjusting camera position per render, or your portfolio set will feel inconsistent.

Step 2 - Run a Presentation Cleanup Pass

Before capture:

• remove placeholder props that distract from focal hierarchy
• clean clipping or z-fighting artifacts
• verify shadows and contrast still read from gameplay distance

This is not a content expansion step. It is a clarity step.

Step 3 - Capture Hero Stills with a Naming Standard

Export your stills with predictable names:

• env_hero_wide_v01
• env_mid_modular_read_v01
• env_close_material_detail_v01

Keep the same naming pattern for revisions so portfolio updates are easy to track and compare.

Step 4 - Create a Clean Turntable Clip

For the turntable:

1. Use one constant camera height.
2. Keep rotation speed steady and readable.
3. Avoid aggressive post-processing or shaky movement.

Target a short 10 to 20 second clip. The goal is readability, not cinematic complexity.

Step 5 - Build One Breakdown Overlay

Create one annotated frame that labels:

• modular kit reuse points
• texel density target
• key shader and post-processing choices

Keep annotations short. Reviewers should understand your pipeline in under 20 seconds.

Mini Challenge

Deliver this pack:

• 3 final stills
• 1 turntable clip
• 1 annotated breakdown image

Pass criteria:

• all images share coherent framing quality
• turntable shows silhouette and material behavior clearly
• annotations explain decisions without paragraph-heavy text

Common Mistakes

Mistake: Over-editing images to hide weak fundamentals

Fix: prioritize scene readability and material quality first, then apply subtle grading only.

Mistake: Using different style rules per screenshot

Fix: lock camera and color presentation rules once, then apply consistently.

Mistake: Overloaded breakdown overlays

Fix: keep 3 to 5 labels max and focus on decisions that show technical intent.

Pro Tips

• Keep one neutral-light render as a baseline for future comparisons.
• Export one 16:9 and one vertical crop of the hero shot for broader sharing.
• Save your camera rigs and render settings as reusable templates for future environments.

FAQ

Should I include wireframes in this lesson output

Only if they are clean and support your breakdown story. Do not add them by default.

How long should a portfolio turntable be

Usually 10 to 20 seconds is enough for a recruiter or client review pass.

Do I need different versions for Unity and Godot presentation

No. One consistent presentation set is enough if your shader and post intent is already matched.

Recap and Next Lesson

You now have a presentation-ready environment pack with clear stills, a concise turntable, and one readable breakdown overlay.

Next is Lesson 15, where you publish the asset pack and write a concise case study with release notes and maintenance-ready changelog structure.