QtPhysics-Unofficial is an unofficial module that aims at intergrating Bullet physics engine into Qt (>5.5). Based on the Qt3D 2.x, the module offers:

• QML components to add physics properties to Qt3D Entities;
• An aspect that implements the physic simulation;
• A Qt plugin that works as wrapper around Bullet Physics;

Video at https://www.youtube.com/watch?v=KyyvVLGzN8U

Two Qml componets are provided:

• PhysicsBodyInfo
• PhysicsWorldInfo

Both components inherit from Qt3D:QComponent. The first one, PhysicsBodyInfo, allows to specify for an entity properties such as mass, restituition, friction etc; The entities belonging to the physic world are:

• Object with an abstract mesh and a PhysicsBodyInfo

PhysicsBodyInfo has two property:

• InputTransform. This matrix is used to set the original position of the object or to force the motion state. When the matrix changes the motion state of the object is updated. NB. By "matrix changes" I mean that a change is notified. For example, if you create button that set a traslation to dz:100, the matrix changes only if the prevoius value of dz was different.
• OutputTransorm: the matrix coming from the physics simulation

A body can be declered as kinematic using the kinematic flag. PhysicsBodyInfo emit a signal collided(CollitionEvent*) when a collition happens.

PhysicsWorldInfo defines general setting for the physic world, such as gravity.

##Physic aspect ##

On the backend, the module implements a Qt3D aspect. In the Bullet world, nested entities are actually single bodies with a compound shape. The relation parent-child is completly absent in the bullet world.

The aspect executes sequentially those jobs:

• Visit the scenegraph and update the physic world. For each entry, create a rigid body and/or update its properties;
• Run a simulation step
• Update the transformation of the entities.
• Update the collitions

##Bullet Plugin## The wrapper around Bullet is implemented as a plugin. It implements the interface PhysicsFactoryInterface, which defines the methods to create bodies and worlds (PhysicsAbstractRigidBody and PhysicsAbstractDynamicsWorld).

##What is missing## ;)

#Build it#

In order to build the module, you need to have Qt >5.6 with Qt3D and Bullet >2.73. Modify the dependency in the file dependecy.pri in /bullet in order to instruct the compiler about the position of the bullet folder.

Remember to add the step install to your make chain. This will put headers and libs in the default Qt directory. Since this is not an official qt module, you have to add the includepath in your project .pro file.

Bullet should be available otherwise the plugin cannot be built.

##Build and install Bullet for Desktop##

Follow the procedure at https://github.com/bulletphysics/bullet3/releases

##Build and install Bullet for Android##

It is required :

• Android NDK 10d
• Android SDK
• android.toolchain.cmake file from Opencv project

Before you compile it, you have to be sure that the shared libraries of Bullet will not have any version number. In fact, Android doesn't support library versioning. What I suggest is to modify the CMakeList.txt and add the option:

OPTION(NO_VERSION "remove the version form shared libraries" OFF)

Then for each CMakeList.txt in the subdirs of src/ add a IF: Example: In BulletSoftBody/CMakeList.txt

IF(NOT NO_VERSION)
SET_TARGET_PROPERTIES(BulletSoftBody PROPERTIES VERSION ${BULLET_VERSION})
SET_TARGET_PROPERTIES(BulletSoftBody PROPERTIES SOVERSION ${BULLET_VERSION})
ENDIF(NOT NO_VERSION)

Then in bullet directory:

• mkdir build-android and cd build-android

• ccmake .. -DANDROID_NDK=[NDK dir] -DCMAKE_TOOLCHAIN_FILE=[android.toolchain.cmake] -DANDROID_TOOLCHAIN_NAME=[TOOLChain name] -DANDROID_NDK_LAYOUT=RELEASE -DANDROID_ABI=[Your ABI] example: ccmake .. -DCMAKE_TOOLCHAIN_FILE=/home/chili/android-ndk-r13b/build/cmake/android.toolchain.cmake -DANDROID_PLATFORM=android-19 -DANDROID_ARM_MODE=arm -DANDROID_ABI=armeabi-v7a\ with\ NEON

• Disable everything except BUILD_SHARED_LIBS ,INSTALL_LIBS and NO_VERSION=true. Check also your install directory.

• make and make install

Do not forget to add your include dirs and libs enviroment if they are not in the default position.