(Adjustments to an) Open source C++ physics engine library in 3D
Go to file
2019-02-28 17:25:37 +01:00
CMakeModules
documentation Update pdf user manual 2018-04-30 22:58:43 +02:00
src Remove mutexes and do not use static pool and single frame memory allocators 2019-02-28 17:25:37 +01:00
test Fix compilation issue of the unit tests 2018-08-05 16:10:13 +02:00
testbed Use MSAA in testbed application 2018-04-27 17:47:31 +02:00
.codecov.yml
.gitignore
.travis.yml Edit travis file 2018-05-23 10:34:15 +02:00
CHANGELOG.md Update changelog file 2019-02-18 22:04:52 +01:00
CMakeLists.txt Make possible for the user to use a custom pool memory allocator 2018-09-26 18:31:21 +02:00
GenerateNewVersion.py Add file to help generation of new library version 2018-04-30 23:00:55 +02:00
LICENSE
README.md Add credits in README file 2019-01-22 23:02:24 +01:00
VERSION

Travis Build Status Codacy Badge codecov.io

ReactPhysics3D

ReactPhysics3D is an open source C++ physics engine library that can be used in 3D simulations and games.

Website : https://www.reactphysics3d.com

Author : Daniel Chappuis

Drawing

Features

ReactPhysics3D has the following features:

  • Rigid body dynamics
  • Discrete collision detection
  • Collision shapes (Sphere, Box, Capsule, Convex Mesh, Static Concave Mesh, Height Field)
  • Multiple collision shapes per body
  • Broadphase collision detection (Dynamic AABB tree)
  • Narrowphase collision detection (SAT/GJK)
  • Collision response and friction (Sequential Impulses Solver)
  • Joints (Ball and Socket, Hinge, Slider, Fixed)
  • Collision filtering with categories
  • Ray casting
  • Sleeping technique for inactive bodies
  • Multi-platform (Windows, Linux, Mac OS X)
  • No external libraries (do not use STL containers)
  • Documentation (user manual and Doxygen API)
  • Testbed application with demos
  • Integrated Profiler
  • Logs
  • Unit tests

License

The ReactPhysics3D library is released under the open-source ZLib license.

Documentation

You can find the user manual and the Doxygen API documentation here

Branches

The "master" branch always contains the last released version of the library and some possible bug fixes. This is the most stable version. On the other side, the "develop" branch is used for development. This branch is frequently updated and can be quite unstable. Therefore, if you want to use the library in your application, it is recommended to checkout the "master" branch.

Issues

If you find any issue with the library, you can report it on the issue tracker here.

Credits

Thanks a lot to Erin Catto, Dirk Gregorius, Erwin Coumans, Pierre Terdiman and Christer Ericson for their amazing GDC presentations, their physics engines, their books or articles and their contributions on many physics engine forums.