How jondolf/avian works
Main Components Overview
a) Core Physics Components:
• Collision System
• Dynamics System
• Spatial Query System
• Debug Rendering System
• Solver System
b) Integration Layer:
• Bevy ECS Integration
• Plugin Architecture
• Transform Synchronization
Detailed Component Breakdown
TOP LAYER - Integration
[Bevy Game Engine] <---> [Avian Physics Plugin System]
MIDDLE LAYER - Core Systems
[Collision Detection] [Dynamics] [Spatial Queries]
[Broad Phase] [Rigid Bodies] [Ray Casting]
[Contact Detection] [Force Systems] [Query Filters]
BOTTOM LAYER - Implementation
[Parry Integration] [XPBD Solver] [Debug Rendering]
Key Relationships to Highlight
• Data flow between systems (→)
• Dependencies (⇢)
• Plugin integration points (⇄)
[avian2d] ─── [Common Core] ─── [avian3d]
[Core Physics] ←── [Pluggable Components]
• Custom Constraints
• Custom Collision Backend
• Custom Broad Phase
Technical Details
• Components that support f32/f64 precision
• Parallel processing capabilities
• Integration points with Bevy's ECS
• XPBD solver architecture
Implementation Notes
• ECS-driven architecture
• No separate physics world (direct ECS integration)
• Modular plugin system
• Clear separation between 2D and 3D implementations while showing shared core components