How mcpar-land/bevy_fly_camera works
Main Components
• Bevy App
• DefaultPlugins (Bevy-provided core systems: rendering, input, ECS scheduler)
• FlyCameraPlugin (the plugin provided by this crate)
• User Startup System (e.g., setup() in examples)
• FlyCameraPlugin
• 2D Camera System (from src/cam2d.rs)
• 3D Camera System (from src/lib.rs / cam3d.rs)
• Utility Module (src/util.rs, e.g., input mappings, sensitivity)
• Entities & Components
• Camera Entity (Camera2dBundle or Camera3dBundle)
• FlyCamera2d or FlyCamera component (data: speed, keybinds)
• Transform component (from Bevy)
• External Services/Dependencies
• Bevy Engine (input, time, ECS)
Relationships and Data Flow
• App Initialization
→ Add DefaultPlugins
→ Add FlyCameraPlugin
→ Run startup system (spawns camera entity + attaches FlyCamera component)
• Runtime Loop (per frame):
Input Events → FlyCameraPlugin systems → Read FlyCamera & Transform components → Update Transform → Rendering pipeline
• Utility functions sit alongside systems to interpret raw input (keyboard/mouse) into movement vectors.
Architectural Patterns & Principles
• ECS (Entity‑Component‑System) pattern:
• Components: FlyCamera, Transform
• Systems: camera_move_2d, camera_move_3d, mouse_look_3d
• Plugin pattern (Bevy’s extension mechanism): registers its systems into Bevy’s scheduler
• Single Responsibility: cam2d.rs handles 2D movement, cam3d.rs handles 3D movement plus mouse, util.rs handles shared math/config
Technologies & Frameworks
• Rust (language)
• Bevy (game engine; ECS, rendering, input)
• bevy_fly_camera (this crate)
• No external services beyond local input/mouse/time
Final Checklist
• [ ] Clear labels for App modules, Plugin, Systems, Entities, Components
• [ ] Indication of file-to-system mapping (cam2d.rs, cam3d.rs, util.rs)
• [ ] Note default keybind values on the FlyCamera component