3D Game Development
Principles for 3D game systems.
1. Rendering Pipeline
Stages
1. Vertex Processing → Transform geometry
2. Rasterization → Convert to pixels
3. Fragment Processing → Color pixels
4. Output → To screen
Optimization Principles
| Technique |
Purpose |
| Frustum culling |
Don't render off-screen |
| Occlusion culling |
Don't render hidden |
| LOD |
Less detail at distance |
| Batching |
Combine draw calls |
2. Shader Principles
Shader Types
| Type |
Purpose |
| Vertex |
Position, normals |
| Fragment/Pixel |
Color, lighting |
| Compute |
General computation |
When to Write Custom Shaders
- Special effects (water, fire, portals)
- Stylized rendering (toon, sketch)
- Performance optimization
- Unique visual identity
3. 3D Physics
Collision Shapes
| Shape |
Use Case |
| Box |
Buildings, crates |
| Sphere |
Balls, quick checks |
| Capsule |
Characters |
| Mesh |
Terrain (expensive) |
Principles
- Simple colliders, complex visuals
- Layer-based filtering
- Raycasting for line-of-sight
4. Camera Systems
Camera Types
| Type |
Use |
| Third-person |
Action, adventure |
| First-person |
Immersive, FPS |
| Isometric |
Strategy, RPG |
| Orbital |
Inspection, editors |
Camera Feel
- Frame-rate-independent smoothing; test camera collision and teleports
- Collision avoidance
- Look-ahead for movement
- FOV changes for speed
5. Lighting
Light Types
| Type |
Use |
| Directional |
Sun, moon |
| Point |
Lamps, torches |
| Spot |
Flashlight, stage |
| Ambient |
Base illumination |
Performance Consideration
- Real-time shadows are expensive
- Bake when possible
- Shadow cascades for large worlds
6. Level of Detail (LOD)
LOD Strategy
| Distance |
Model |
| Near |
Full detail |
| Medium |
Reduced detail based on measured visual error |
| Far |
Low-detail mesh or billboard when visually appropriate |
7. Anti-Patterns
| ❌ Don't |
✅ Do |
| Mesh colliders everywhere |
Simple shapes |
| Real-time shadows on mobile |
Baked or blob shadows |
| One LOD for all distances |
Distance-based LOD |
| Unoptimized shaders |
Profile and simplify |
Remember: 3D is about illusion. Create the impression of detail, not the detail itself.
When to Use
Use when implementing or profiling a 3D rendering pipeline, shaders, colliders, cameras, lighting or level-of-detail transitions.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Verification
Treat tables as design starting points, not guarantees. Prototype the selected mechanic, test accessibility and recovery paths, and measure frame timing, memory and behavior on target hardware before claiming completion. Store submission and licensing requirements must be checked against current official platform documentation.
1---2name: 3d-games3description: 3D game development principles. Rendering, shaders, physics, cameras.4metadata:5 source: https://skillmd.com/skills/iradoweck/3d-games6 aas-risk: none7 aas-source: community8 aas-date-added: '2026-02-27'9---1011# 3D Game Development1213> Principles for 3D game systems.1415---1617## 1. Rendering Pipeline1819### Stages2021```221. Vertex Processing → Transform geometry232. Rasterization → Convert to pixels243. Fragment Processing → Color pixels254. Output → To screen26```2728### Optimization Principles2930| Technique | Purpose |31|-----------|---------|32| **Frustum culling** | Don't render off-screen |33| **Occlusion culling** | Don't render hidden |34| **LOD** | Less detail at distance |35| **Batching** | Combine draw calls |3637---3839## 2. Shader Principles4041### Shader Types4243| Type | Purpose |44|------|---------|45| **Vertex** | Position, normals |46| **Fragment/Pixel** | Color, lighting |47| **Compute** | General computation |4849### When to Write Custom Shaders5051- Special effects (water, fire, portals)52- Stylized rendering (toon, sketch)53- Performance optimization54- Unique visual identity5556---5758## 3. 3D Physics5960### Collision Shapes6162| Shape | Use Case |63|-------|----------|64| **Box** | Buildings, crates |65| **Sphere** | Balls, quick checks |66| **Capsule** | Characters |67| **Mesh** | Terrain (expensive) |6869### Principles7071- Simple colliders, complex visuals72- Layer-based filtering73- Raycasting for line-of-sight7475---7677## 4. Camera Systems7879### Camera Types8081| Type | Use |82|------|-----|83| **Third-person** | Action, adventure |84| **First-person** | Immersive, FPS |85| **Isometric** | Strategy, RPG |86| **Orbital** | Inspection, editors |8788### Camera Feel8990- Frame-rate-independent smoothing; test camera collision and teleports91- Collision avoidance92- Look-ahead for movement93- FOV changes for speed9495---9697## 5. Lighting9899### Light Types100101| Type | Use |102|------|-----|103| **Directional** | Sun, moon |104| **Point** | Lamps, torches |105| **Spot** | Flashlight, stage |106| **Ambient** | Base illumination |107108### Performance Consideration109110- Real-time shadows are expensive111- Bake when possible112- Shadow cascades for large worlds113114---115116## 6. Level of Detail (LOD)117118### LOD Strategy119120| Distance | Model |121|----------|-------|122| Near | Full detail |123| Medium | Reduced detail based on measured visual error |124| Far | Low-detail mesh or billboard when visually appropriate |125126---127128## 7. Anti-Patterns129130| ❌ Don't | ✅ Do |131|----------|-------|132| Mesh colliders everywhere | Simple shapes |133| Real-time shadows on mobile | Baked or blob shadows |134| One LOD for all distances | Distance-based LOD |135| Unoptimized shaders | Profile and simplify |136137---138139> **Remember:** 3D is about illusion. Create the impression of detail, not the detail itself.140141## When to Use142Use when implementing or profiling a 3D rendering pipeline, shaders, colliders, cameras, lighting or level-of-detail transitions.143144## Limitations145- Use this skill only when the task clearly matches the scope described above.146- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.147- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.148149## Verification150151Treat tables as design starting points, not guarantees. Prototype the selected mechanic, test accessibility and recovery paths, and measure frame timing, memory and behavior on target hardware before claiming completion. Store submission and licensing requirements must be checked against current official platform documentation.