🎮 Game Art Production Pipeline

Platform-Specific Budgets

PBR Material Maps

Base Color / Albedo

• Purpose: Raw surface color without lighting information
• Resolution: Typically highest (2K-4K for heroes)
• Format: RGB, sRGB color space
• Critical Rule: NO lighting baked in! Pure surface color only

Normal Map

• Purpose: Surface detail and bump information
• Resolution: Same as albedo or half-res
• Format: RGB, Linear color space
• Channels: R=X, G=Y, B=Z (tangent space normals)

Roughness / Smoothness

• Purpose: How rough/smooth surface is (controls specular spread)
• Resolution: Can be half-res of albedo
• Format: Grayscale, Linear
• Values: 0=mirror smooth, 1=completely rough

Metallic

• Purpose: Defines if surface is metal or dielectric
• Resolution: Often lower res (512-1024)
• Format: Grayscale, Linear
• Values: Usually 0 or 1 (binary), rarely in-between

Ambient Occlusion (AO)

• Purpose: Shadows in crevices and contact points
• Resolution: Can be lower res
• Format: Grayscale
• Note: Often baked from high-poly, multiplied with albedo

Emissive

• Purpose: Self-illuminated areas (screens, lights, magic)
• Resolution: Lower res usually fine
• Format: RGB (can be very compressed)
• HDR: Can exceed 1.0 for bloom effects

🎨 Modern Game Art Workflows

Workflow 1: High-to-Low Baking (AAA Standard)

1. Sculpt high-poly model (millions of polygons)
   └── ZBrush, Blender, Mudbox
   
2. Create low-poly game model (thousands of polygons)
   └── Maya, Blender, 3ds Max
   
3. UV unwrap low-poly
   └── Optimize for minimal stretching
   
4. Bake high-poly detail to maps
   └── Normal, AO, Curvature → Substance Painter, Marmoset
   
5. Hand-paint textures in Paintstorm
   └── Use baked maps as base
   └── Add artistic detail, variation, story
   
6. Export texture set
   └── Combine maps for engine
   
7. Set up material in engine
   └── Unity, Unreal, Custom engine

Workflow 2: Pure 2D Assets (UI, Sprites, Concepts)

1. Concept sketch
   └── Paintstorm or Photoshop
   
2. Refine linework
   └── Clean, game-ready lines
   
3. Color and shade
   └── Consider lighting in-game
   
4. Export at multiple resolutions
   └── @1x, @2x, @3x for different screen densities
   
5. Create sprite sheets if animated
   └── Optimize atlas packing
   
6. Import to engine with proper settings
   └── Compression, filtering, mipmaps

Workflow 3: Tiling Textures (Environments)

1. Create seamless base pattern
   └── Paintstorm with offset preview
   
2. Add variation layers
   └── Macro detail, micro detail
   
3. Generate material maps
   └── Normal from height, roughness variation
   
4. Test tiling at scale
   └── 10x10 tiles minimum
   
5. Create trim sheets if needed
   └── Modular pieces for variety
   
6. Export and implement
   └── Test in actual game environment

Professional File Structure

GameProject/
├── Art/
│   ├── Textures/
│   │   ├── Characters/
│   │   │   ├── Hero/
│   │   │   │   ├── T_Hero_Body_BaseColor.png (4096x4096)
│   │   │   │   ├── T_Hero_Body_Normal.png (4096x4096)
│   │   │   │   ├── T_Hero_Body_ORM.png (4096x4096)
│   │   │   │   │   └── Packed: R=AO, G=Roughness, B=Metallic
│   │   │   │   └── T_Hero_Body_Emissive.png (2048x2048)
│   │   │   └── Enemy_Grunt/
│   │   │       ├── T_Grunt_Body_BaseColor.png (2048x2048)
│   │   │       └── T_Grunt_Body_Normal.png (2048x2048)
│   │   │
│   │   ├── Environment/
│   │   │   ├── Ground/
│   │   │   │   ├── T_Stone_Cobble_BC.png (1024x1024, tiling)
│   │   │   │   ├── T_Stone_Cobble_N.png
│   │   │   │   └── T_Stone_Cobble_ORM.png
│   │   │   └── Props/
│   │   │       └── Crate/
│   │   │           ├── T_Crate_Wood_BC.png (512x512)
│   │   │           └── T_Crate_Wood_N.png
│   │   │
│   │   ├── VFX/
│   │   │   ├── T_Fire_Sheet.png (1024x1024, 4x4 frames)
│   │   │   ├── T_Smoke_Atlas.png (2048x2048)
│   │   │   └── T_Magic_Sparkle.png (256x256)
│   │   │
│   │   └── UI/
│   │       ├── Icons/
│   │       ├── Buttons/
│   │       └── Backgrounds/
│   │
│   ├── Source/
│   │   ├── PSD/
│   │   │   └── Working Photoshop files
│   │   ├── Paintstorm/
│   │   │   └── .psd with layers
│   │   └── HighPoly/
│   │       └── Sculpt source files
│   │
│   └── Export/
│       └── Final game-ready assets

Naming Convention:
T_[AssetName]_[Part]_[MapType].extension

Map Type Abbreviations:
BC  = Base Color (Albedo)
N   = Normal
ORM = Packed (AO + Roughness + Metallic)
E   = Emissive
H   = Height
M   = Mask

✅ Before Marking an Asset "Done"

Technical Requirements:

• ☐ Poly count within budget
• ☐ Texture resolution appropriate for use case
• ☐ All UV islands within 0-1 space
• ☐ No UV stretching or distortion
• ☐ Proper texel density (consistent detail across model)
• ☐ Maps exported in correct format and color space
• ☐ Power-of-two dimensions (512, 1024, 2048, 4096)
• ☐ File sizes reasonable (compression settings correct)

Artistic Quality:

• ☐ Consistent with art direction
• ☐ Appropriate level of detail for viewing distance
• ☐ Clean silhouette and readable forms
• ☐ Material values physically accurate (PBR)
• ☐ Variation and interest without noise
• ☐ Story elements and wear patterns make sense

Engine Integration:

• ☐ Imports without errors or warnings
• ☐ Renders correctly in all lighting conditions
• ☐ Material setup matches intended look
• ☐ LODs transition smoothly
• ☐ Performs within frame budget
• ☐ Works on target platforms (especially low-end)

Documentation:

• ☐ Technical specs documented
• ☐ Material parameters noted
• ☐ Source files organized and backed up
• ☐ Any special requirements flagged

The Core Concept

Traditional: "This area is bright because there's a light source."
PBR: "This surface is rough metal, so it will react to light this way."

PBR separates what the surface IS (material properties) from how it's LIT (lighting calculations). This means:

• Assets look correct in any lighting scenario
• No need to repaint for different environments
• Physically accurate reflections and light interaction
• Easier for technical artists to implement

Real-World Material Values

🎨 Workflow: Creating a PBR Material Set

STEP 1: Set Up Your Canvas
─────────────────────────────
• Create new document at target resolution (2048×2048 common)
• Set color mode to RGB, 8-bit or 16-bit
• Import UV layout as reference layer
• Import baked maps if available (AO, normal, curvature)

STEP 2: Base Color (Albedo) Pass
─────────────────────────────
• Block in large material zones
  └── Use flat colors based on PBR values
  └── No lighting information!
  
• Add color variation
  └── Slight hue shifts (±10 degrees)
  └── Saturation variation in organic materials
  └── Consider surface contamination (dirt, dust)
  
• Add macro detail
  └── Large scratches, wear patterns
  └── Material transitions
  └── Decals, logos, graphics
  
• Add micro detail
  └── Small scratches, pitting
  └── Subtle noise for realism
  └── DON'T overdo it - less is more!

STEP 3: Roughness Map Creation
─────────────────────────────
• Start with base material roughness value
  └── Flat fill based on material type
  
• Add variation based on wear
  └── Worn areas = smoother (darker in roughness map)
  └── Dirty areas = rougher (lighter in roughness map)
  └── Wet areas = much smoother
  
• Detail work
  └── Scratches are usually smoother
  └── Edges get worn = smoother
  └── Cavities collect dirt = rougher
  
• Use curvature map as guide
  └── Exposed edges = wear = smoother
  └── Crevices = protection = original roughness

STEP 4: Metallic Map (if needed)
─────────────────────────────
• Usually binary: 0 for dielectric, 1 for metal
• Paint solid values based on material
• Sharp transitions OK - metals don't gradually appear
• Consider only at material boundaries
• Rare: 0.04 for specular adjustment on dielectrics

STEP 5: Normal Map Enhancement
─────────────────────────────
• If you baked from high-poly: Start there
• If creating from scratch: Use height-to-normal tools
  
• Paint height information in grayscale
  └── White = raised, Black = recessed
  
• Add details:
  └── Panel lines, rivets, bolts
  └── Fabric weave, leather grain
  └── Fine scratches (perpendicular to surface)
  └── Damage, dents, impacts
  
• Convert to normal map
  └── Use Photoshop filter or external tool
  └── Adjust strength as needed

STEP 6: Ambient Occlusion
─────────────────────────────
• If baked: Use as base
• If not: Paint contact shadows manually
  
• Darken:
  └── Crevices and gaps
  └── Where objects touch
  └── Panel intersections
  └── Deep wrinkles/folds
  
• Keep it subtle - strong AO can look baked-in

STEP 7: Emissive (Optional)
─────────────────────────────
• Only for self-illuminating areas
• Can use full RGB color
• Can exceed 1.0 for bloom effect
• Common uses:
  └── Screens, displays
  └── Lights, LEDs
  └── Magical effects
  └── Energy fields

STEP 8: Quality Check
─────────────────────────────
• View each map individually
• Check in 3D viewer with different lighting
• Ensure no baked lighting in base color
• Verify PBR value ranges
• Test with rough and smooth lighting
• Export and test in actual game engine

Setting Up for PBR Painting

Layer Organization:
└── TextureSet_2K.psd
    ├── [Group] BaseColor
    │   ├── Details
    │   ├── Wear
    │   ├── Variation
    │   └── Base Material
    │
    ├── [Group] Roughness
    │   ├── Wear Pattern
    │   ├── Edge Smoothing
    │   └── Base Roughness (fill layer)
    │
    ├── [Group] Metallic
    │   └── Metal Mask (usually simple)
    │
    ├── [Group] Normal (if painting)
    │   ├── Fine Details
    │   └── Height Base
    │
    ├── [Group] AO (if needed)
    │   └── Contact Shadows
    │
    └── [Reference] UV Layout

Brush Settings for Material Painting

// For Base Color Detail Work
Brush: Textured Round
Size: 20-50 pixels
Opacity: 20-40% (build up gradually)
Flow: 60-80%
Spacing: 15-25%
Texture: Subtle noise or surface pattern
Color Dynamics: Slight hue jitter (±5 degrees)

// For Roughness Variation
Brush: Soft Round with Scatter
Size: Larger (50-150 pixels)
Opacity: 10-30% (very subtle)
Flow: 40-60%
Texture: Organic noise
Pressure: Controls opacity for build-up

// For Edge Wear
Brush: Edge Detect + Scatter
Size: 3-10 pixels
Opacity: 100% (hard edges OK for wear)
Scatter: Moderate
Use With: Curvature map as guide
Effect: Paint lighter roughness on exposed edges

// For Scratches
Brush: Thin line with angle jitter
Size: 1-3 pixels
Opacity: 60-100%
Angle Jitter: Slight
Length: Stroke-dependent
Apply To: Base color (subtle), roughness (visible), normal (if needed)

❌ Don't Do This!

Mistake 1: Baked Lighting in Albedo

• ❌ BAD: Painting shadows and highlights in base color
• ✅ GOOD: Pure surface color only, let engine handle lighting
• Why: Baked lighting breaks under different light conditions

Mistake 2: Unrealistic Base Color Values

• ❌ BAD: RGB(0,0,0) black or RGB(255,255,255) white dielectrics
• ✅ GOOD: Stay in RGB(50-240) range for realistic materials
• Why: Real materials don't reflect 0% or 100% light

Mistake 3: Wrong Metallic Values

• ❌ BAD: 0.5 metallic "to make it shiny"
• ✅ GOOD: 0.0 or 1.0 only (materials are metal or not)
• Why: There's no such thing as "half metal" in nature

Mistake 4: Confusing Roughness with Brightness

• ❌ BAD: Using roughness to make materials look darker
• ✅ GOOD: Roughness only controls specular spread, not brightness
• Why: Brightness comes from base color, not roughness

Mistake 5: Overdetailing

• ❌ BAD: Every pixel has unique detail, pure noise
• ✅ GOOD: Strategic detail with clean areas for visual rest
• Why: Too much detail = visual mud, hard to read

Mistake 6: Inconsistent Wear Patterns

• ❌ BAD: Random scratches everywhere with no logic
• ✅ GOOD: Wear appears where it would naturally occur
• Why: Believable wear tells a story

Mistake 7: Matching Roughness to Base Color

• ❌ BAD: Dark areas in base color = dark in roughness
• ✅ GOOD: Roughness is independent of color
• Why: Black rubber is rough, black plastic is smooth - color ≠ roughness

Technique 1: Wear and Tear Pattern Logic

WHERE Wear Appears:
────────────────────
✓ High-traffic areas (handles, edges, corners)
✓ Areas that get gripped or touched
✓ Exposed edges that catch on things
✓ Areas subject to friction or impact
✗ Protected crevices and gaps
✗ Rarely-touched areas
✗ Newly added components

HOW to Paint Wear:
────────────────────
Base Color Layer:
  • Slightly lighter color (metal showing through)
  • Or dirt/grime buildup in protected areas
  • Edge highlights where paint chips

Roughness Layer:
  • SMOOTHER (darker value) on worn areas
  • Polished by friction
  • Especially on metal edges

Normal Map:
  • Subtle rounding of sharp edges
  • Small dents and impacts
  • Directional scratches

Example: Worn Leather Boot
────────────────────
Base Color:
  • Fresh leather: RGB(110, 70, 45)
  • Worn areas: Slightly lighter, desaturated
  • Creases: Darker accumulation
  
Roughness:
  • New leather: 0.65
  • Worn smooth areas: 0.45
  • Scuffed areas: 0.75
  
Normal:
  • Deep creases in bend areas
  • Scratches parallel to use direction
  • Scuff marks with height variation

Technique 2: Material Blending Zones

When Different Materials Meet:
────────────────────
Example: Metal plate on leather

Transition Zone (2-5 pixels):
  Base Color:
    • Metal: Proper metal color
    • Leather: Proper leather color
    • Edge: Slight color bleed (oxidation on metal, staining on leather)
  
  Roughness:
    • Sharp transition OK
    • Maybe slight smoothing at contact point (friction)
  
  Metallic:
    • HARD transition - either metal or not
    • No gradient between materials
  
  Normal:
    • Small gap/crack at interface
    • Contact wear on both materials
  
  AO:
    • Darken the crevice/contact area
    • Simulate light occlusion

Technique 3: Tri-Planar Detail Projection

For organic or complex models without clean UVs:

1. Paint detail maps in world space
   └── Top-down, side, front views
   
2. Use tri-planar projection in shader
   └── Blend based on surface normal
   
3. Benefits:
   ✓ No UV stretching artifacts
   ✓ Consistent detail density
   ✓ Easy to add/modify
   
4. Drawbacks:
   ✗ Slightly more expensive to render
   ✗ Less precise control
   
Best For:
  • Rocks, cliffs, terrain
  • Organic characters (when combined with UV)
  • Background props

Technique 4: Color ID Masking

Workflow for Complex Assets:

1. Create Color ID Map
   └── Flat colors per material zone
   └── R=255 for metal parts
   └── G=255 for leather parts
   └── B=255 for fabric parts
   └── etc.

2. In Paintstorm, use Color Range selection
   └── Select specific ID color
   └── Paint details only in that zone
   └── Ensures clean material separation

3. Benefits:
   ✓ Easy to isolate areas
   ✓ Quick selection of material zones
   ✓ No edge bleeding between materials
   ✓ Can automate with actions/scripts

4. Export final maps without ID layer
   └── ID map is workflow tool only

Texture Set Organization

🎨 Painting Realistic Skin

Step 1: Base Skin Tone

Color Values for Different Skin Tones:
────────────────────────────────────
Fair Caucasian:   RGB(240, 210, 195) + variations
Medium Caucasian: RGB(232, 190, 172)
Olive/Tan:        RGB(205, 164, 133)
Light Brown:      RGB(165, 126, 100)
Medium Brown:     RGB(130, 92, 67)
Dark Brown:       RGB(90, 60, 45)
Very Dark:        RGB(55, 40, 30)

IMPORTANT: These are starting points!
• Add color variation (±15 degrees hue)
• Adjust saturation per area
• Never use pure grayscale for "white" skin
• All skin has color - reds, yellows, blues

Step 2: Subsurface Scattering Zones

Areas with More Blood Flow (redder):
✓ Nose tip
✓ Cheeks
✓ Ears (very red!)
✓ Lips (much redder)
✓ Fingertips
✓ Elbows, knees (if visible)

Areas with Less Blood (more yellow/olive):
✓ Forehead
✓ Chin
✓ Neck
✓ Chest

Areas with Blue Undertones:
✓ Around eyes (thin skin, veins visible)
✓ Temples
✓ Under cheekbones (sometimes)

Technique:
1. Block in base skin tone
2. Add subtle red layer on blood-rich areas (5-15% opacity)
3. Add subtle blue/green on areas with thin skin
4. Blend smoothly - no harsh transitions
5. More contrast = more vibrant and alive
6. Less contrast = more pale/sickly/dead

Step 3: Skin Detail Layers

Layer Order (Bottom to Top):
────────────────────────────
1. Base Skin Tone (flat color)
2. Subsurface Color Variation (red/yellow/blue zones)
3. Large Pores/Texture (10-20% opacity, subtle)
4. Fine Pores (5-10% opacity, very subtle)
5. Wrinkles and Creases (painted with care)
6. Freckles/Beauty Marks (if applicable)
7. Scars and Blemishes
8. Facial Hair/Stubble (if applicable)
9. Makeup (if applicable)
10. Dirt/Grime (environment-dependent)

Painting Each Layer:
────────────────────
Large Pores:
  • Use textured brush, 10-30 pixel size
  • Very low opacity (10-20%)
  • Slightly darker than base skin
  • More visible on nose, cheeks, forehead
  • Less visible on smooth areas (under eyes)

Wrinkles:
  • Paint in Base Color: Subtle darkening in crease
  • Paint in Normal Map: Define depth
  • Paint in Roughness: Creases are slightly rougher
  • Direction matters: Follow muscle structure
  • Depth varies: Smile lines deeper than crow's feet

Scars:
  • Base Color: Lighter, less pigmented (or darker if fresh)
  • Normal: Raised if fresh, flat if old
  • Roughness: Smoother than surrounding skin (scar tissue)
  • Placement tells story: Where would they get hurt?

Fabric Material Properties

Clothing Wear Patterns

Realistic Wear Locations:
────────────────────────────

Shirts/Tops:
✓ Collar edge (friction from neck/hair)
✓ Elbows (constant bending)
✓ Cuffs (friction from surfaces)
✓ Button areas (stress points)
✓ Underarms (sweat, friction)
✓ Shoulders (bag straps if carried)

Pants:
✓ Knees (kneeling, bending)
✓ Pockets (items carried, hands in pockets)
✓ Seat (sitting)
✓ Cuffs (ground contact)
✓ Belt loops (stress from belt)
✓ Thighs (friction when walking)

Shoes/Boots:
✓ Toe caps (kicking, walking)
✓ Heels (wear from walking)
✓ Sides (scuffing against surfaces)
✓ Soles (ground contact - model if visible)
✓ Laces (fraying, color fade)

Armor/Gear:
✓ Straps (stretching, color fade)
✓ Buckles (scratching, tarnish)
✓ Edges and corners (impact damage)
✓ Joints (articulation wear)
✓ Weapons contact points

How to Paint Wear:
────────────────────────────
1. Identify wear type:
   • Friction wear = smoothing, lightening
   • Impact wear = scratches, dents
   • Age wear = color fade, UV damage
   • Use wear = pattern marks (pocket shapes)

2. Base Color Changes:
   • Fade color (reduce saturation)
   • Lighten slightly (UV bleaching)
   • Add dirt in protected areas
   • Stains where liquids collect

3. Roughness Changes:
   • Worn areas SMOOTHER (polished by friction)
   • Damaged areas ROUGHER (torn, pilled)

4. Normal Map:
   • Thinning fabric (less height)
   • Tears and holes (sharp transitions)
   • Bunching and wrinkles (stress areas)

💭 Texture as Narrative

Every mark on a character tells their story. Think about WHO they are when deciding WHAT to paint:

Warrior Character:

• Scars: Placement indicates combat style (frontal scars = aggressor, back scars = survivor)
• Armor wear: Battle damage on front, clean on back = confident fighter
• Weapon calluses: Specific hand areas roughened by weapon grip
• Dirt patterns: Recent battle vs. long campaign

Scholar Character:

• Ink stains: Fingers, cuffs (writing a lot)
• Fabric wear: Elbows from leaning on desks, not knees
• Calluses: From pen, not sword
• Clean areas: Not exposed to harsh environments

Traveler/Adventurer:

• Sun damage: Uneven tan, weathered skin on exposed areas
• Dust accumulation: Everywhere, lighter colors
• Repairs: Patches, stitching (maintains gear on road)
• Wear: Even distribution (constant movement)

Mechanic/Engineer:

• Oil stains: Hands, clothes (impossible to remove)
• Burns: Small marks from hot equipment
• Worn fingertips: From tool use
• Practical clothing: Less decorative wear, more functional damage

The Three Distance Rules

Rule 1: Detail by Distance

Far Distance (50+ meters):
────────────────────────────
• Silhouette is everything
• Large shapes and color blocks
• Minimal texture detail needed
• Focus on atmospheric perspective
• LOD0 or LOD1 (lowest detail)

Example: Distant mountain
  Resolution: 512×512 or less
  Details: Large rock formations only
  Normal Map: Broad shapes
  Performance: Very cheap

Mid Distance (10-50 meters):
────────────────────────────
• Medium detail visible
• Material types should read clearly
• Texture can be lower res
• LOD1 or LOD2

Example: Building across street
  Resolution: 1024×1024
  Details: Windows, doors, general wear
  Normal Map: Medium detail
  Performance: Moderate

Close Distance (0-10 meters):
────────────────────────────
• High detail necessary
• Texture imperfections visible
• Player can inspect
• LOD2 or LOD3 (highest detail)

Example: Interactive door
  Resolution: 2048×2048 or higher
  Details: Scratches, dirt, grain
  Normal Map: Fine detail
  Performance: More expensive

Rule 2: Modularity Over Uniqueness

Create Reusable Pieces:
────────────────────────────
Instead of: 100 unique rocks
Do: 10 rock types × 10 variations each
    = Same visual variety, 90% less work

Building a Wall:
❌ Bad: One huge unique texture for entire wall
✅ Good: Modular pieces that combine:
  • Base brick tileable (repeats)
  • Trim pieces (corners, edges)
  • Detail decals (cracks, graffiti)
  • Vertex color for variation

Benefits:
✓ Faster creation
✓ Easier to modify
✓ Better performance (texture reuse)
✓ More variety possible
✓ Easier QA and bug fixing

Rule 3: Performance Budget Awareness

Asset Budget Guidelines:
────────────────────────────
Hero Props (player interacts):
  • Triangles: 5k-15k
  • Texture: 2048×2048
  • Unique materials: 1-2

Standard Props (common objects):
  • Triangles: 1k-5k
  • Texture: 1024×1024
  • Shared materials: Yes

Background Props (filler):
  • Triangles: 300-1k
  • Texture: 512×512
  • Highly shared materials

Landscape (terrain, large surfaces):
  • Tiling textures: 1024-2048
  • Repeated infinitely
  • Blend multiple materials

🔄 Making Perfect Seamless Textures

Method 1: Offset Method (Most Common)

In Paintstorm Studio:

1. Create Your Texture
   └── Paint naturally, don't worry about seams yet
   └── Keep detail in center
   └── Leave edges relatively clean

2. Apply Offset
   └── Filter > Other > Offset
   └── X: 50% of width
   └── Y: 50% of height
   └── This moves the seams to the center

3. Fix the Seam
   └── Use Clone Stamp tool
   └── Paint over visible seam
   └── Match texture patterns
   └── Blend carefully

4. Repeat if Needed
   └── Offset again to check other seam
   └── Fix any remaining issues

5. Test Tiling
   └── Create large canvas (4x4 tiles)
   └── Fill with pattern
   └── Look for repetition artifacts
   └── No obvious grid or crosses = success!

Method 2: Edge Blending

For organic textures (ground, rock, etc.):

1. Paint texture normally

2. Select edge regions (50-100 pixels)
   └── Top edge
   └── Copy and flip vertically
   └── Paste at bottom edge
   └── Blend at 50% opacity

3. Repeat for sides
   └── Left edge
   └── Copy and flip horizontally
   └── Paste at right edge
   └── Blend at 50% opacity

4. Fix corners
   └── Clone stamp from nearby areas
   └── Blend carefully

5. Add variation across entire tile
   └── Prevents obvious repeating pattern

Method 3: Procedural Noise Base

For natural materials (dirt, stone, etc.):

1. Start with tileable noise
   └── Generate Perlin/Simplex noise
   └── These are naturally tileable
   └── Multiple octaves for detail

2. Add color variation
   └── Color layers with blend modes
   └── Hue/saturation adjustments
   └── Keep subtle

3. Paint details on top
   └── Cracks, features
   └── These can cross seams (will still tile)
   └── Use offset method to check

4. Add final touches
   └── Highlights, shadows
   └── Wear patterns
   └── Localized color variation

Result: Tileable base that looks organic!

Avoiding Repetition Artifacts

Common Tiling Problems:
────────────────────────────

Problem 1: The "Cross" Pattern
Symptom: X-shaped pattern appears when tiled
Cause: Too much contrast at seams
Fix: Reduce contrast near edges, add variation

Problem 2: Obvious Grid
Symptom: Can see individual tile boundaries
Cause: Features too centered or regular
Fix: Break up symmetry, add random elements

Problem 3: Directional Flow
Symptom: Clear diagonal or vertical lines
Cause: Brush strokes too uniform
Fix: Vary brush direction, add perpendicular detail

Problem 4: High-Contrast Feature
Symptom: One bright/dark spot draws eye
Cause: Feature too unique, repeated obviously
Fix: Duplicate and vary the feature elsewhere

Solutions:
────────────────────────────
✓ Add macro variation (large-scale noise)
✓ Add micro variation (small-scale detail)
✓ Break symmetry
✓ Use multiple textures blended
✓ Add vertex color variation
✓ Use decals over tileable base
✓ Rotate/flip textures randomly in engine

Common Environment Materials

Natural Terrain Materials

Man-Made Materials

🎬 Creating Lived-In Worlds

Principle: Everything Has a History

• New vs. Old: Age tells story (maintained building = cared for, decay = abandoned)
• Clean vs. Dirty: Usage frequency (clean door handle = often used)
• Worn vs. Protected: Exposed edges wear first, protected areas stay pristine
• Repaired vs. Broken: Repairs show someone cares, neglect shows abandon

Environmental Narrative Examples:

Example 1: Abandoned Factory

Visual Story Elements:
• Rust: Advanced, spreading from water damage
• Broken Windows: Nature reclaiming space
• Graffiti: Recent, over older layers
• Vegetation: Growing through cracks
• Equipment: Still in place, left behind hastily
• Dirt: Years of accumulation, undisturbed
• Paint: Peeling, faded by UV exposure
• Floor Wear: Paths still visible from past foot traffic

Texture Decisions:
✓ Heavy rust on metal (0.70-0.85 roughness)
✓ Faded paint, exposed primer
✓ Green/brown moss on north sides
✓ Bird droppings near high perches
✓ Dust accumulation in protected corners

Example 2: Active Medieval Village

Visual Story Elements:
• Doors: Worn at handles, clean from use
• Streets: Center worn smooth, edges muddy
• Wells: Rope-worn grooves in stone
• Signs: Recently repainted, maintained
• Windows: Clean, curtains visible
• Chimneys: Active soot patterns
• Gardens: Tended, living plants

Texture Decisions:
✓ Stone worn smooth on high-traffic areas
✓ Wood shows maintenance (some new boards)
✓ Thatch roofs recently repaired
✓ Mud patterns show recent rain
✓ Market areas show stains from goods

Example 3: Sci-Fi Space Station

Visual Story Elements:
• Panels: Scratched at edges from opening
• Floors: Worn paths show main routes
• Labels: Faded but still legible
• Screens: Active, some glitching
• Cables: Organized but showing age
• Lighting: Some panels failed/replaced
• Maintenance: Some areas pristine, others neglected

Texture Decisions:
✓ Metal panels scratched at joints
✓ Rubber seals degrading, color fade
✓ Display screens with dead pixels
✓ Hand-holds worn smooth from use
✓ Warning labels partially scraped off

Trim Sheets and Atlases

What is a Trim Sheet?

A trim sheet is a texture atlas containing:
• Horizontal trims (molding, edges)
• Vertical trims (corners, columns)
• Tileable sections (walls, floors)
• Unique details (decals, features)

All designed to work together modularly!

Example 1024×1024 Trim Sheet Layout:
┌─────────────────────────────────────┐
│ Horizontal Trim A (256×64)          │ ← Window sill
├─────────────────────────────────────┤
│ Horizontal Trim B (256×64)          │ ← Crown molding
├─────────────────────────────────────┤
│ Horizontal Trim C (256×64)          │ ← Baseboard
├──────────┬──────────┬───────────────┤
│ Vertical │ Vertical │               │
│ Trim A   │ Trim B   │  Tileable     │
│ 64×256   │ 64×256   │  Wall Section │
│          │          │  512×512      │
│ Corner   │ Column   │               │
├──────────┴──────────┼───────────────┤
│ Detail Decals       │ Unique Detail │
│ 256×256             │ 256×256       │
└─────────────────────┴───────────────┘

Benefits:
✓ One texture = entire building interior
✓ Flexible combinations = variety
✓ Memory efficient = more detail possible
✓ Artist-friendly = modular workflow

Creating a Trim Sheet

Step 1: Plan Your Modules
──────────────────────────
• List all architectural elements needed
• Group by similarity (all horizontal trims together)
• Calculate how many variations needed
• Allocate texture space proportionally

Step 2: Create Base Modules
──────────────────────────
• Each trim must tile in its direction
  └── Horizontal trims tile horizontally
  └── Vertical trims tile vertically
  └── Corners must work with both

• Test each piece individually
• Ensure correct texel density (consistent detail)

Step 3: Add Details
──────────────────────────
• Unique features that don't need to tile
• Decals (cracks, stains, graffiti)
• Variations of trim pieces
• Special elements (doorframes, windows)

Step 4: Material Maps
──────────────────────────
• Create matching normal map
• Create matching roughness map
• Keep PBR principles consistent
• Test full sheet with lighting

Step 5: UV Mapping Models
──────────────────────────
• Model geometry matches trim layout
• UVs precisely align to trim edges
• Test in engine with actual lighting

🎨 Multi-Material Blending

Technique 1: Vertex Painting

Blend multiple tileable textures using vertex colors:

Setup:
• 4 tileable textures (RGBA channels)
  R = Grass
  G = Dirt  
  B = Stone
  A = Sand (or use Alpha for blending)

In Engine Material:
• Sample all 4 textures
• Multiply each by vertex color channel
• Add results together

Advantages:
✓ Runtime control (artists can paint in engine)
✓ Smooth transitions
✓ Infinite detail (textures tile)
✓ Very memory efficient

Disadvantages:
✗ Need sufficient vertex density
✗ Can't have hard transitions
✗ Limited to 4 materials per shader

Best For:
• Terrain
• Large outdoor environments
• Organic transitions

Technique 2: Mask-Based Blending

Use texture masks to control blending:

Setup:
• Base tileable textures (2-8 materials)
• Blend mask texture (RGBA = 4 masks)
  R channel = Where Material A shows
  G channel = Where Material B shows
  B channel = Where Material C shows
  A channel = Where Material D shows

Advantages:
✓ Pixel-perfect control
✓ Can have sharp transitions
✓ More than 4 materials possible (multi-layer)
✓ Can be painted in Paintstorm

Disadvantages:
✗ Requires UV space for mask
✗ Additional texture memory
✗ Less runtime control

Best For:
• Hero props with multiple materials
• Precise material placement needed
• Stylized looks with sharp transitions

Technique 3: Height-Based Blending

Blend based on height/normal information:

Material Shader Logic:
1. Sample height from both materials
2. Compare heights at blend boundary
3. Higher material "wins" at boundary
4. Creates natural stacking effect

Example: Snow on Rock
• Rock height: 0.5 (base)
• Snow height: 0.8 (accumulates on top)
• At blend zone: Snow appears on top of rock peaks
• Result: Natural accumulation pattern

Code Concept:
height_blend = height_A - height_B + blend_factor
blend_mask = saturate(height_blend / sharpness)
final_color = lerp(material_B, material_A, blend_mask)

Advantages:
✓ Physically realistic
✓ Natural accumulation patterns
✓ Works great for snow, moss, rust
✓ Automatic detail in transitions

Disadvantages:
✗ More expensive computationally
✗ Requires height maps for materials
✗ Can be hard to art-direct precisely

Best For:
• Natural accumulation (snow, dust, moss)
• Weathering effects
• Realistic material layering

Compression and Memory

Texture Compression Guidelines:
────────────────────────────────

Base Color (Albedo):
Format: BC1/DXT1 (no alpha) or BC3/DXT5 (with alpha)
Quality: Can use moderate compression
Note: sRGB color space

Normal Maps:
Format: BC5/3Dc (two channel)
Quality: Higher quality needed
Note: Store only XY, reconstruct Z
      Linear color space

Roughness/Metallic/AO (Packed):
Format: BC1/DXT1 or BC7 for better quality
Quality: Roughness needs good quality
      Metallic can be more compressed
      AO can be heavily compressed
Note: Pack in RGB channels
      R = AO, G = Roughness, B = Metallic

Memory Calculation:
────────────────────────────────
1024×1024 texture memory:
• Uncompressed: 4MB (RGBA8)
• BC1: 0.5MB (8:1 compression)
• BC5: 1MB (4:1 compression)
• BC7: 1MB (4:1 compression, better quality)

Tileable Texture Strategy:
• Use higher resolution (more detail)
• Use good compression (less memory)
• Result: Better quality than unique lower-res textures!

Example Budget:
10 tileable textures at 1024×1024 BC1:
= 5MB total texture memory
Can cover entire level!

vs.

100 unique textures at 512×512 uncompressed:
= 100MB total texture memory
Only covers small area!

Essential VFX Texture Categories

1. Sprite Sheets (Frame Animation)

Layout: Grid of animation frames
Common: 4×4 (16 frames) or 8×8 (64 frames)

Example: Fire Sprite Sheet (1024×1024, 4×4)
┌────┬────┬────┬────┐
│ F1 │ F2 │ F3 │ F4 │  ← Frames 1-4
├────┼────┼────┼────┤
│ F5 │ F6 │ F7 │ F8 │  ← Frames 5-8
├────┼────┼────┼────┤
│ F9 │F10 │F11 │F12 │  ← Frames 9-12
├────┼────┼────┼────┤
│F13 │F14 │F15 │F16 │  ← Frames 13-16
└────┴────┴────┴────┘

Each frame: 256×256 pixels

Painting Tips:
• Plan animation before painting
• Consistent timing between frames
• Exaggerate motion (reads better)
• First frame = spawn state
• Last frame = dissipate state
• Consider looping vs one-shot

2. Texture Atlases (Multiple Elements)

Layout: Various elements in one texture
Purpose: Random particle variation

Example: Spark Atlas (2048×2048)
┌──────────────┬──────────────┐
│ Spark Type A │ Spark Type B │
│              │              │
├──────────────┼──────────────┤
│ Spark Type C │ Spark Type D │
│              │              │
├──────────────┴──────────────┤
│ Streak Type A │ Streak Type B│
├───────────────┴─────────────┤
│  Glow shapes various sizes  │
└─────────────────────────────┘

System randomly picks element per particle
Result: Organic variation without CPU cost

3. Flow Maps (Distortion)

Layout: RG channels = XY flow direction
Purpose: Animate scrolling/distortion

Color meaning:
R channel: X direction (0=left, 128=none, 255=right)
G channel: Y direction (0=down, 128=none, 255=up)

Use: 
• Distort other textures over time
• Create flowing water
• Energy field movement
• Smoke swirl patterns

Painting:
• Think of flow as vectors
• Paint direction arrows conceptually
• Red = horizontal flow
• Green = vertical flow
• Middle gray (128) = no movement

4. Noise Textures (Organic Variation)

Types:
• Perlin Noise: Smooth, cloud-like
• Worley/Cellular: Organic cells
• Voronoi: Crystalline, technical
• Turbulence: Chaotic, energetic

Uses:
• Dissolve effects (sprite appears/disappears)
• Opacity variation (non-uniform transparency)
• Color variation (random hue shifts)
• Distortion (warp other effects)
• Mask generation (procedural shapes)

Often generated procedurally, but can paint for control

🔥 Painting Effects Elements

Fire Effect

Approach: Additive blending, animate from bottom

Base Color:
• Core: Bright yellow-white (RGB: 255, 240, 200)
• Mid: Orange (RGB: 255, 160, 0)
• Edge: Red fading to transparent (RGB: 255, 60, 0 → 0)
• NO black - fire is additive!

Shape:
• Bottom: Narrower, denser
• Middle: Wider, most intense
• Top: Wispy, breaking apart
• Edges: Feathered softly

Alpha Channel:
• Core: 100% opaque
• Edges: Gradient to transparent
• Wispy tendrils: Low opacity
• Creates soft blending

Animation Frames:
1-4: Ignition (small, building)
5-8: Build-up (growing, brightening)
9-12: Peak (largest, brightest)
13-16: Flicker (slight size variation)

Smoke Effect

Approach: Alpha blended, animate upward

Base Color:
• Dark smoke: RGB(40, 40, 40) light smoke: RGB(200, 200, 200)
• Slight color tint OK (brown, blue)
• Subtle color variation within plume

Shape:
• Bottom: Denser, more defined
• Rising: Expands, diffuses
• Top: Very soft, dissipating
• Turbulent edges (use noise)

Alpha Channel:
• Bottom: 60-80% opacity
• Middle: 40-60% opacity  
• Top: Fading to 0%
• Variation: Use noise for organic density

Animation Frames:
1-4: Dense, small
5-8: Expanding, thinning
9-12: Large, diffuse
13-16: Dissipating, breaking apart

Magic/Energy Effect

Approach: Additive, saturated colors, glow

Base Color:
• Core: Super bright (RGB: 255, 255, 255)
• Primary: Saturated hue (RGB: 100, 200, 255 for blue)
• Secondary: Complementary hints
• Edges: Color fade to transparency

HDR Values:
• Center can exceed 255 for bloom effect
• In Paintstorm: Paint white, will be multiplied in engine
• Creates "impossibly bright" magical look

Shape:
• Geometric or organic based on type
• Sharp edges = arcane/technical magic
• Soft edges = natural/wild magic
• Swirls and tendrils common

Alpha Channel:
• High opacity at core
• Sharp falloff to transparent
• Can have hard shapes (runes, symbols)

Animation:
• Pulse (scale variation)
• Shimmer (opacity flicker)
• Rotation (spiral patterns)
• Flow (moving tendrils)

Impact/Explosion Effect

Approach: Multiple layers, quick animation

Initial Flash (Frame 1-2):
• Pure white or bright color
• Large, round, soft
• Very high opacity
• Quick (1-2 frames only)

Shockwave (Frame 2-5):
• Ring expanding outward
• Starts opaque, fades fast
• Color based on effect type
• Can be just alpha (distortion)

Debris (Frame 3-10):
• Particles flying outward
• Various sizes and shapes
• Color based on material
• Trails and motion blur

Smoke/Dust (Frame 5-16):
• Rising after impact
• Dissipating
• Larger over time
• Fading opacity

Layering:
Flash → Shockwave → Debris → Smoke
All on separate particle systems

⚡ Performance & Best Practices

Overdraw is the Enemy

Overdraw = How many times a pixel is drawn

Problem:
• 10 particles overlap at one pixel
• GPU draws that pixel 10 times
• 9 are wasted (covered by later ones)

Solutions:
✓ Reduce particle count
✓ Smaller particles where possible
✓ Don't overlap unnecessarily  
✓ Use LOD (fewer particles at distance)
✓ Clip/cull particles behind camera
✓ Use additive where appropriate (cheaper)

Alpha Blending Costs:
Cheapest → Most Expensive
1. Opaque (no alpha)
2. Alpha Test (cutout, binary)
3. Additive (blend, but doesn't need sorting)
4. Alpha Blend (requires sorting, expensive)

Texture Budget for VFX

VFX Texture Guidelines:
────────────────────────────

Sprite Sheets:
• 1024×1024 maximum usually
• 512×512 for simple effects
• BC3/DXT5 compression (need alpha)
• One texture = one effect usually

Atlases:
• 2048×2048 for variety pack
• Multiple effects share
• Good for sparks, debris, etc.

Particle Counts:
Mobile: 10-50 particles max per effect
Console: 50-500 particles  
PC: 500-5000 particles (with LOD)

Memory Example:
20 VFX textures at 1024×1024 BC3
= 20MB total VFX texture budget
Reasonable for most games

Alpha Channel Best Practices

Critical for VFX:
────────────────────────────

✓ Use soft edges (gradients)
✓ Pre-multiply alpha when possible
✓ Avoid hard edges (aliasing)
✓ Test with dark backgrounds
✓ Test with light backgrounds
✓ Consider alpha erosion (slight shrink)

Common Mistake:
❌ White core with black edge in alpha
Result: Dark halo around effect

Fix:
✅ White core with gradient to transparent
✅ Match color to expected background
✅ Or use additive blending (no halo possible)

Understanding LOD Systems

LOD Philosophy:
────────────────────────────
Only render detail the player can actually see!

LOD Levels Standard:
────────────────────────────
LOD0 (Highest Detail):
  Distance: 0-5 meters
  Triangles: 100% of budget
  Textures: Full resolution
  Materials: All details active
  Use: Player can inspect closely

LOD1 (High Detail):
  Distance: 5-15 meters
  Triangles: 40-60% of LOD0
  Textures: Full or half resolution
  Materials: All details, maybe simplified
  Use: Nearby, visible but not inspected

LOD2 (Medium Detail):
  Distance: 15-40 meters
  Triangles: 20-40% of LOD0
  Textures: Half resolution
  Materials: Simplified, fewer maps
  Use: Background objects, still clearly visible

LOD3 (Low Detail):
  Distance: 40-100 meters
  Triangles: 5-15% of LOD0
  Textures: Quarter resolution
  Materials: Basic, single texture often
  Use: Far background, silhouette visible

LOD4+ (Imposters/Billboards):
  Distance: 100+ meters
  Triangles: 2 (single quad)
  Textures: Baked image of object
  Materials: Simple textured quad
  Use: Very far, just needs to exist

Example: Tree Asset
────────────────────────────
LOD0: 15,000 triangles, 2048×2048 textures
  Individual leaves, branches, bark detail
  
LOD1: 6,000 triangles, 2048×2048 textures
  Leaf clusters, simplified branches
  
LOD2: 2,000 triangles, 1024×1024 textures
  Simple crown, basic trunk
  
LOD3: 500 triangles, 512×512 textures
  Cone shape, flat leaf cards
  
LOD4: 2 triangles, 256×256 texture
  Flat billboard with tree image

🎨 Maximizing Quality, Minimizing Memory

Strategy 1: Texture Atlasing

Combine Multiple Textures:
────────────────────────────

Instead of:
❌ 10 textures × 512×512 = 10 draw calls + 10MB
   Each is its own material

Do:
✅ 1 atlas × 2048×2048 = 1 draw call + 4MB (compressed)
   All share one material
   
Savings:
• 90% fewer draw calls
• 60% less memory
• Faster rendering

When to Atlas:
✓ Small props that appear together
✓ UI elements
✓ Character accessories
✓ Particle effects
✓ VFX elements

When NOT to Atlas:
✗ Need mipmaps per texture
✗ Different tiling rates needed
✗ Different material properties
✗ Very large individual textures

Strategy 2: Channel Packing

Pack Multiple Maps into One Texture:
────────────────────────────────────

Standard Packing: ORM Map
R channel = Ambient Occlusion (or nothing)
G channel = Roughness
B channel = Metallic
A channel = (unused or other mask)

Benefits:
• 3 textures → 1 texture
• 66% memory savings
• Fewer texture samples in shader
• Industry standard practice

Alternative Packings:
────────────────────────────
RMA Pack:
R = Roughness
G = Metallic  
B = AO
A = Emissive mask (or height)

MRAE Pack (if needed):
R = Metallic
G = Roughness
B = AO
A = Emissive

Rules:
✓ Pack maps with similar importance
✓ Don't pack maps needing different compression
✓ Normal maps stay separate (need BC5 compression)
✓ Base color stays separate (needs sRGB color space)

Strategy 3: Intelligent Resolution

Not Everything Needs 4K!
────────────────────────────

Resolution Guidelines:
Hero Character Face: 4096×4096 (close-up cutscenes)
Hero Character Body: 2048×2048 (visible but not as close)
Hero Character Hands: 1024×1024 (sometimes close in first-person)
Hero Props/Weapons: 2048×2048 (inspected in inventory)

Common Enemy: 2048×2048 (body + head combined)
Common Props: 1024×1024 or shared atlas
Background Props: 512×512 or shared atlas

Environment Tileables: 1024×1024 or 2048×2048
  (High res OK because they tile infinitely)

UI Elements: 512×512 or less (screen-space, not world-space)
Icons: 256×256 or 128×128

VFX: 512×512 to 1024×1024 (usually far and fast-moving)

Calculation Example:
────────────────────────────
Bad Allocation:
Background crate: 2048×2048 = 16MB uncompressed
Player weapon: 512×512 = 1MB uncompressed
Result: Wasted memory on thing player rarely sees

Good Allocation:
Background crate: 512×512 = 1MB uncompressed  
Player weapon: 2048×2048 = 16MB uncompressed
Result: Detail where player actually looks!

Strategy 4: Compression Settings

Choose the Right Compression:
────────────────────────────

BC1/DXT1 (6:1 compression):
✓ Base color without alpha
✓ Roughness/metallic/AO packed
✗ Visible artifacts in gradients
Use: Most diffuse textures

BC3/DXT5 (4:1 compression):
✓ Base color with alpha
✓ Masked textures (foliage)
✗ Artifacts in alpha gradients
Use: Textures needing transparency

BC5/3Dc (4:1 compression):
✓ Normal maps (two-channel)
✓ Best quality for normals
✓ Reconstruct Z in shader
Use: ONLY for normal maps

BC7 (4:1 compression):
✓ High quality color
✓ High quality alpha
✓ Best general-purpose
✗ Slower to compress
✗ Not supported everywhere
Use: Hero assets on modern platforms

Mobile:
• Use ASTC compression (better quality than DXT)
• Adjust block size based on importance
• 4×4 blocks = higher quality
• 8×8 blocks = lower quality, smaller size

Strategy 5: Mipmap Optimization

Mipmaps = Pre-filtered smaller versions
────────────────────────────────────

Without Mipmaps:
❌ Texture shimmering at distance
❌ Performance hit (sampling too many texels)
❌ Moiré patterns

With Mipmaps:
✅ Smooth appearance at all distances
✅ Better performance (cache friendly)
✅ +33% memory cost (worth it!)

Mipmap Chain:
2048×2048 → 1024×1024 → 512×512 → 256×256 
  → 128×128 → 64×64 → 32×32 → 16×16 
  → 8×8 → 4×4 → 2×2 → 1×1

GPU automatically picks appropriate level based on distance

Optimization:
• Last few mips (16×16 and below): Replace with solid color
• Tint the mips to verify they're being used (debugging)
• Consider sharpening mips for better distance clarity

Reducing Draw Calls

Draw Calls = Major Performance Cost
────────────────────────────────────

What is a Draw Call?
CPU tells GPU: "Draw this object with this material"

Cost Breakdown:
• CPU overhead: Preparing command
• State changes: Switching textures/shaders
• GPU overhead: Starting new draw

Target Draw Calls (per frame):
Mobile: 50-100
Console: 500-1000  
PC: 1000-2000+

Optimization Strategies:
────────────────────────────────────

1. Texture Atlasing
   • Multiple objects, one texture, one material
   • 100 objects with individual textures = 100 draw calls
   • 100 objects with shared atlas = 1 draw call

2. Material Sharing
   • Different objects can share same material
   • Vary through vertex colors, secondary UVs
   • All "stone" props use one stone material

3. Static Batching
   • Combine static meshes at build time
   • 50 rocks → 1 combined mesh
   • Single draw call for entire group

4. Dynamic Batching (real-time)
   • Engine combines similar objects per frame
   • Works for small objects (< 300 verts usually)
   • Must share material

5. Instancing
   • Draw same mesh multiple times efficiently
   • One draw call for 1000 trees
   • Each can have different position/rotation
   • Requires instancing support in engine

6. LOD Reduces Active Objects
   • Distant objects swap to simpler versions
   • Or cull entirely beyond distance
   • Fewer active objects = fewer draw calls

📊 Professional Budget Tracking

Example Memory Budget (Console Game):
────────────────────────────────────

Total Texture Memory Available: 2GB
Reserved for System: 200MB
Available for Game: 1.8GB

Allocation:
─────────────────────────
Characters: 400MB (22%)
  • Player: 100MB
  • Enemies: 200MB
  • NPCs: 100MB

Environments: 800MB (44%)
  • Tileables: 200MB
  • Props: 300MB
  • Terrain: 200MB
  • Sky/Atmosphere: 100MB

Effects: 200MB (11%)
  • Particles: 100MB
  • Post-processing: 50MB
  • UI Effects: 50MB

UI: 200MB (11%)
  • Menus: 100MB
  • HUD: 50MB
  • Icons: 50MB

Streaming Buffer: 200MB (11%)
  • For loading next area
  • Prevents hitches

Budget Tracking Spreadsheet:
────────────────────────────
| Asset Name | Resolution | Format | Memory | Category |
|------------|-----------|--------|--------|----------|
| Hero_Body  | 2048×2048 | BC1    | 4MB    | Char     |
| Hero_Face  | 4096×4096 | BC3    | 16MB   | Char     |
| Stone_Tile | 1024×1024 | BC1    | 1MB    | Env      |
| ...        | ...       | ...    | ...    | ...      |
| TOTAL      |           |        | 385MB  |          |

At any time, know:
• Current usage vs budget
• Largest offenders
• Where to optimize if needed

What to Submit

1. Final Assets

AssetPackage_[YourTheme]/
├── Characters/
│   ├── Hero_LOD0.fbx
│   ├── Hero_LOD1.fbx
│   ├── Hero_LOD2.fbx
│   └── Textures/
│       ├── Hero_Head_BC.png
│       ├── Hero_Head_N.png
│       ├── Hero_Head_ORM.png
│       ├── Hero_Body_BC.png
│       ├── Hero_Body_N.png
│       └── Hero_Body_ORM.png
│
├── Props/
│   ├── [PropName]_LOD0.fbx
│   ├── [PropName]_LOD1.fbx
│   └── Textures/
│       ├── Props_Atlas_BC.png
│       ├── Props_Atlas_N.png
│       └── Props_Atlas_ORM.png
│
├── Materials/
│   ├── Tileable_Floor/
│   │   ├── Floor_BC.png
│   │   ├── Floor_N.png
│   │   └── Floor_ORM.png
│   └── Tileable_Wall/
│       ├── Wall_BC.png
│       ├── Wall_N.png
│       └── Wall_ORM.png
│
├── VFX/
│   ├── Effect01_SpriteSheet.png
│   ├── Effect02_SpriteSheet.png
│   └── VFX_Atlas.png
│
└── Documentation/
    ├── TechnicalSpecs.pdf
    ├── MemoryBudget.xlsx
    └── README.txt

2. Technical Documentation

• Complete technical specifications for each asset
• Triangle counts per LOD level
• Texture memory breakdown
• Material setup instructions
• Known limitations or requirements
• Performance metrics (draw calls, etc.)

3. Engine Implementation

• All assets imported to game engine (Unity or Unreal)
• Materials properly set up
• LODs configured and tested
• Simple scene showcasing all assets
• Screenshots from engine

4. Presentation Materials

• Beauty renders (4-6 high-quality images)
• Wireframe views showing topology
• Texture sheets (showing all maps)
• Turntable video of character (30-60 seconds)
• Brief description of creative process

💡 Success Tips

• Start with references: Gather real-world photo references for your theme
• Plan before painting: Sketch your UV layouts and texture maps first
• Test early, test often: Import to engine frequently to catch issues
• Iterate on feedback: Show work-in-progress to others
• Stay within budget: Track memory usage as you go
• Polish counts: Final 10% of polish makes it portfolio-worthy
• Document everything: Future employers will ask technical questions
• Think modular: Assets that combine create more value

🎯 Game Art Mastery Achieved!

You've completed professional game art training! You now understand:

• ✅ Complete game art pipeline
• ✅ PBR texture painting
• ✅ Character texturing workflows
• ✅ Environment asset creation
• ✅ Tileable texture systems
• ✅ VFX and particle textures
• ✅ Performance optimization
• ✅ LOD strategies
• ✅ Memory budget management
• ✅ Technical constraints
• ✅ Production workflows
• ✅ Portfolio presentation

🎮 The Professional Game Artist Mindset

"Game art is the balance between beauty and performance. Every texture is a budget decision. Every polygon is a performance consideration. Master this balance, and you're invaluable to any studio."

Core Principles to Remember:

1. PBR is not optional: Modern games require physically accurate materials
2. Optimization is art: Making beautiful art run at 60 FPS is creative problem-solving
3. Budget consciousness: Always know your memory and performance costs
4. Modularity creates value: Reusable assets are worth more than unique ones
5. LOD is essential: Detail where it matters, optimize elsewhere
6. Technical documentation matters: Studios need to understand your work
7. Engine integration is part of the job: Art isn't done until it's in-game

📚 Essential Learning

PBR Theory:

• "PBR Guide" by Allegorithmic (free PDF)
• Marmoset Toolbag PBR documentation
• "Physically Based Rendering" by Matt Pharr et al.

Game Art Techniques:

• "The Art of Game Design" by Jesse Schell
• "Digital Texturing and Painting" by Owen Demers
• 80 Level - Game art interviews and breakdowns
• ArtStation Learning - Professional game art courses

Technical Art:

• "Real-Time Rendering" by Tomas Akenine-Möller
• GPU Gems series (free online)
• Technical Art blogs (Ben Cloward, Harry Alisavakis)

🔗 Professional Tools & Communities

Essential Software:

• Substance 3D Painter - Industry standard for texture painting
• Marmoset Toolbag - Real-time rendering and baking
• ZBrush - High-poly sculpting
• Maya/Blender - 3D modeling and UV unwrapping
• Unity/Unreal Engine - Game engines

Communities:

• Polycount - The game art forum
• ArtStation - Portfolio and inspiration
• GameArtists.org - Tutorials and discussion
• r/gamedev, r/gameassets - Reddit communities
• Tech-Artists.org - Technical art focused

🚀 Next Steps in Your Career

Build Your Portfolio:

• Complete the asset package project
• Create 3-5 more portfolio pieces in different styles
• Include technical breakdowns (wireframes, maps)
• Show process, not just final renders
• Demonstrate range and specialization

Specialize or Generalize:

• Character Artist: Focus on organic forms, anatomy, cloth
• Environment Artist: Master world-building, modularity
• Technical Artist: Deepen shader, tool, and pipeline knowledge
• VFX Artist: Specialize in particles, shaders, animation
• Generalist: Stay broad, valuable for indie and small studios

Keep Learning:

• Follow industry trends (ray tracing, Nanite, virtual texturing)
• Learn new tools as they emerge
• Study shipped games' art techniques
• Participate in art challenges (Artstation, Polycount)
• Network with professionals online and at events

🎓 Professional Game Artist Status

You've mastered the complete game art production pipeline. You understand not just how to make beautiful art, but how to make shippable game art - optimized, professional, and production-ready. This knowledge separates hobbyists from professionals.

The games industry needs artists who understand both aesthetics AND technology. You're now equipped to contribute to AAA studios, indie teams, or create your own projects. Go build incredible game worlds!

🌟 Share Your Game Assets!

When you complete your asset package, share it with the community! Tag with #GameArt and #IndieGameDev

Studios are always looking for talented artists - your portfolio is your best resume!