avianphysics/avian
Avian
Avian is a 2D physics engine and rigid body dynamics simulator designed to calculate physical motion using mass, forces, and velocity. It provides a framework for simulating rigid body dynamics, collision detection, and joint constraints for games and applications.
The engine utilizes a modular physics pipeline with a plugin-based architecture, allowing for the customization of simulation fidelity settings and the extension of collision backends. It includes a specialized kinematic character controller for implementing entity movement and sliding behavior against physical geometry.
The system covers several core capability areas, including spatial query processing via raycasting and shapecasting, mechanical constraint modeling through various joint types, and real-time physics debugging and visualization of colliders and joints.
Features
- 2D Rigid Body Physics Engines - Implements a 2D physics engine for calculating realistic physical interactions, collisions, and rigid body dynamics.
- Continuous Collision Detection - Prevents fast-moving objects from tunneling through geometry by calculating the exact time of impact.
- Skeletal Movement Constraints - Restricts the relative motion of physical bodies using spherical, prismatic, and other joint constraints.
- Physics Body Configurations - Links physical bodies using specific joint types to restrict their relative movement and interaction.
- Collision Detection - Identifies intersections between colliders using layers and sensors to trigger physical interaction events.
- Spatial Querying Systems - Provides spatial querying systems for detecting proximity and intersections via raycasting and region tests.
- Mechanical Constraints - Provides tools for linking and constraining the movement of physical bodies through mechanical joints.
- Mechanical Joint Constraints - Implements mechanical joint constraints such as fixed, distance, prismatic, and revolute joints to link physical bodies.
- Physics World Queries - Supports spatial queries including raycasting and shapecasting to locate geometry within the physics world.
- Kinematic Body Locomotion - Provides a kinematic character controller that handles movement and sliding behavior against physical geometry.
- Physics and Simulation - Adjusts simulation speed, gravity, and substeps to balance physical accuracy and performance.
- Fidelity Configuration - Provides global settings for gravity, speed, and substeps to tune the precision of physics calculations.
- Character Controllers - Provides a specialized kinematic character controller for managing player movement and physics interactions.
- Sleep-State Optimizations - Optimizes CPU overhead by disabling physics calculations for rigid bodies that have come to a complete rest.
- Inverse Kinematics Character Animations - Provides kinematic body locomotion for calculating velocity and handling obstacle sliding for game characters.
- Collision Optimization - Optimizes collision detection by dividing the simulation world into regions to reduce intersection tests.
- Simulation State Integration - Increases simulation stability and precision by dividing frames into smaller time increments for integration.
- Physics Debug Rendering - Visualizes physical bodies and colliders through debug rendering to analyze simulation behavior.
- Physics Visualizers - Visualizes colliders, bounding boxes, and joints in a debug view to verify physical interactions.
- Pipeline Extenders - Extends the simulation pipeline through a modular plugin architecture to support custom collision backends.
- Physics Pipeline Plugins - Utilizes a plugin-based architecture to extend collision backends and customize simulation fidelity.
- Plugin-Based Architectures - Utilizes a modular plugin-based architecture to allow customization of the simulation pipeline and collision backends.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
