Notre avis

Ce skill présente les principes fondamentaux du développement de jeux 3D : pipeline de rendu, shaders, physique, caméras, éclairage et niveaux de détail.

Points forts

Structure claire par thème (rendu, shaders, physique, caméras, éclairage, LOD)
Inclut des tableaux d'optimisation et des anti-patterns concrets
Met l'accent sur les compromis performance/qualité visuelle

Limites

Aucun exemple de code spécifique à un moteur ou langage
Niveau introductif, sans approfondissement des algorithmes complexes
Ne couvre pas les workflows de jeu (animation, audio, IA)

Quand l'utiliser

Lorsqu'il faut des bases solides en conception de systèmes 3D pour un nouveau projet de jeu.

Quand l'éviter

Quand on recherche des solutions implémentées ou des API propres à un moteur de jeu particulier.

Exemples

Camera follow system

I'm making a 3D action game. Help me set up a smooth third-person camera that avoids walls and includes look-ahead.

Optimizing scene rendering

My 3D scene has too many draw calls and lags. Explain how to apply frustum culling, occlusion culling, and LOD to improve performance.

Choosing collision shapes

For game characters and terrain, what collision shapes should I use and why? Provide best practices for physics.

name: 3d-games description: "3D game development principles. Rendering, shaders, physics, cameras." allowed-tools: Read, Write, Edit, Glob, Grep risk: unknown source: community

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

Smooth following (lerp)
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 | 50% triangles | | Far | 25% or billboard |

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

This skill is applicable to execute the workflow or actions described in the overview.

Développement de jeux 3D

Recommandé pour