(Adjustments to an) Open source C++ physics engine library in 3D
Go to file
2016-01-14 21:34:30 +01:00
cmake Remove Find Freeglut CMake module 2015-03-03 21:45:58 +01:00
documentation Update documentation 2015-08-13 19:12:51 +02:00
src Add HeightFieldShape class 2016-01-14 21:34:30 +01:00
test Modifications in methods to get support point in many collision shapes 2016-01-14 21:24:21 +01:00
testbed Set the working directory of the testbed application when building with CMake for Visual Studio 2016-01-09 17:45:55 +01:00
.gitignore Add the .gitignore file 2012-08-01 02:03:56 +02:00
.travis.yml Add .travis.yml file to build on Travis 2015-07-12 11:49:25 +02:00
CMakeLists.txt Add HeightFieldShape class 2016-01-14 21:34:30 +01:00
LICENSE Modify the LICENSE file for the ZLib license 2013-03-17 16:44:52 +01:00
README.md Add Travis build status picture in README file 2015-07-12 11:59:33 +02:00
VERSION Changes for the next release 2015-02-15 21:56:45 +01: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

Features

ReactPhysics3D has the following features :

  • Rigid body dynamics
  • Discrete collision detection
  • Collision shapes (Sphere, Box, Cone, Cylinder, Capsule, Convex Mesh)
  • 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)
  • Documentation (User manual and Doxygen API)
  • Examples
  • 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.