From Human Computer Interaction Laboratory
As complexity and extent of virtual environments grows, more realistic dynamics of virtual bodies is required. PHYSICON is a high-level API for simulation of rigid body dynamics in macro world. Its engine works with an easy-to-reed XML specification of graphics and physics data. This allows fast design and implementation of virtual environments. It is built above ODE (Open Dynamics Engine), which uses implicit low order integrator that brings stability, speed and lower accuracy, so it is usable for virtual interactive environments such as computer games or collaborative applications, but not for engineering simulations.
Contents
Integration with graphics
PHYSICON is designed to use with any graphics engine. Initialization and basic setting of graphics engine is naturally matter of main program. PHYSICON manages scene loading and initialization, so it builds both graphics and physics data structure. It is able to update positions of graphics objects. The objects are rendered independently on its own framerate (mostly we need constant framerate of physics calculations, or faster framerate than graphics rendering).
Scene design
Currently designer has to design the scene only by writing its XML code. I want to develop a plug-in for 3ds max. This plug-in allows defining physics properties of objects (e.g., mass and collision approximation, surface adhesion, etc.) along with their graphics.
Data format
A complex scene definition that contains graphics and physics data is included in XML format designed for PHYSICON. For easy modification and transparency of scene a part of data is stored in XML (objects position, material definition, physics properties, etc.). Large data, such as mesh and texture definitions are stored in a binary file and XML scene definition contains only handles to this file.
Enviroment width
The engine is designed for usage of very large environments. It contains a system, which automatically removes stable bodies from physics calculations (the body becomes unstable for example after collision with another one). Due to this optimization we are able to build a virtual environment width contains thousands of objects with real physics attributes. I consider an implementation of physics LOD, too.
Additional
Because I want to design PHYSICON as the game engine too, I am going to implement a support for gas-engines simulation, for better materials adhesion and maybe for simulation rag doll.
Current state of development
The core of PHYSICON, initialization and simulations of body dynamics and loading from XML definitions is up and running. A simulation of the car dynamics and collision detection with terrain is in progress. I have released stable public version of PHYSICON and a few developers is implementing it into theirs games.
Future work
I want to add these features into PHYSICON:
- trimesh collision detection
- collision detection first phase optimalizations (probably RDC, octree)
- triggers
- breakable joints
- vehicles simulation engine
- kynematics for animated ragdoll
- interface for force-feedback devices
Links
- Czech version of this document (rtf) - maybe my English is little confusing, so I let here Czech version of this text :-)
- Faculty of Informatics, Masaryk University Brno
- www.ceskehry.cz - server for Czech and Slovak game developers (includes magazine, forums, gallery etc.)
- www.pupworx.com - an independent game-developers organization, where I act as programmer (PUPworX will use PHYSICON in racing game "1977")
- nsys.3open.com - an organization, where I act as programmer, too (PHYSICON will be used here as engine for virtual environment in Nsys)
- ode.org - Open Dynamics Engine
- www.ogre3d.org - OGRE engine