(Adjustments to an) Open source C++ physics engine library in 3D
Go to file
2017-01-19 20:29:40 +01:00
cmake Remove Find Freeglut CMake module 2015-03-03 21:45:58 +01:00
documentation Modify documentation 2016-04-14 22:11:19 +02:00
src Fix issue in GJK algorithm 2017-01-19 20:29:40 +01:00
test Update tests of collision world according to changes in collision detection 2017-01-09 21:34:31 +01:00
testbed Fix merge conflicts 2016-08-21 11:47:22 +02:00
.gitignore Modify .gitignore file 2015-08-27 22:47:40 +02:00
.travis.yml Modify .travis.yml file 2016-04-15 21:45:55 +02:00
CMakeLists.txt Refactor collision detection 2017-01-08 19:56:59 +01:00
LICENSE Change version number of the library 2016-04-11 20:15:20 +02:00
README.md Update Readme file 2016-04-15 22:00:43 +02:00
VERSION Change version number of the library 2016-04-11 20:15:20 +02:00

Travis Build Status

ReactPhysics3D

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

Website : http://www.reactphysics3d.com

Author : Daniel Chappuis

Drawing

Features

ReactPhysics3D has the following features :

  • Rigid body dynamics
  • Discrete collision detection
  • Collision shapes (Sphere, Box, Cone, Cylinder, Capsule, Convex Mesh, static Concave Mesh, Height Field)
  • Multiple collision shapes per body
  • Broadphase collision detection (Dynamic AABB tree)
  • Narrowphase collision detection (GJK/EPA)
  • 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
  • Integrated Profiler
  • Multi-platform (Windows, Linux, Mac OS X)
  • No dependencies (only OpenGL for the testbed application)
  • Documentation (User manual and Doxygen API)
  • Testbed application with demo scenes
  • 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.