An AABR is a rectangle with 2 sides parallel to the world x-axis and the other 2 parallel to the world y-axis.

NOTE: the abstract classes cannot be instantiated

NOTE: you should not instantiate this class

A bungee will only exert a pulling force if the spring is extended further than its restlength

This type is intimately tied to SAT collision detection.

This class with its lone static method is used by the PhysicsEngine to resolve all found collisions for each iteration in its step.

To resolve collisions, the CollisionResolver needs to know both bodies involved, the point of contact in world coordinates, and the collision normal (points outward from incident edge).

NOTE: the class is not yet implemented

This solver simply finds the derivative and applies it directly to the state to advance the equation

Gravity in simulation applies a mass-ignorant force.

I tried to keep this as general and uninhibitive as possible.

This is given as a simple example of how to create a slightly more complex force generator.

Games often need to get the current state of various keys in order to respond to user input.

This should typically be accessed through the more user friendly interface

The simulation takes the form:

  1.

This type is intimately tied to SAT collision detection.

Rigid bodies have some definable qualities worth mentioning.

This is a meticulous and accurate IODESolver.

This is the simplest force generator scenario- a vector given at instantiation is applied to any element that calls generate.

SimpleParticle could be used to simulate particle movement- though no collision system is currently in place for such elements.

Due to the need for spring forces to update within an ISimulatable's integration, there is 1 Spring element per force generation.