Take the 2-minute tour ×
Game Development Stack Exchange is a question and answer site for professional and independent game developers. It's 100% free, no registration required.

Previously, I struggle with the sequential impulse-based method I developed. Thanks to jedediah referring me to this paper, I managed to rebuild the codes and implement the simultaneous impulse based method with Projected-Gauss-Seidel (PGS) iterative solver as described by Erin Catto (mentioned in the reference of the paper as [Catt05]).

So here's how it currently is:

  1. The simulation handles 2-dimensional rotating convex polygons.

  2. Detection is using separating-axis test, with a SKIN, meaning closest points between two polygons is detected and determined if their distance is less than SKIN.

  3. To resolve collision, simultaneous impulse-based method is used. It is solved using iterative solver (PGS-solver) as in Erin Catto's paper. Error-correction is implemented using Baumgarte's stabilization (you can refer to either paper for this) using J V = beta/dt*overlap, J is the Jacobian for the constraints, V the matrix containing the velocities of the bodies, beta an error-correction parameter that is better be < 1, dt the time-step taken by the engine, and overlap, the overlap between the bodies (true overlap, so SKIN is ignored).

However, it is still less stable than I expected :s I tried to stack hexagons (or squares, doesn't really matter), and even with only 4 to 5 of them, they would swing! Also note that I am not looking for a sleeping scheme. But I would settle if you have any explicit scheme to handle resting contacts.

That said, I would be more than happy if you have a way of treating it generally (as continuous collision, instead of explicitly as a special state).

Ideas I have tried: Using simultaneous position based error correction as described in the paper in section 5.3.2, turned out to be worse than the current scheme.

If you want to know the parameters I used:

  • Hexagons, side 50 (pixels)

  • gravity 2400 (pixels/sec^2)

  • time-step 1/60 (sec)

  • beta 0.1

  • restitution 0 to 0.2

  • coeff. of friction 0.2

  • PGS iteration 10

  • initial separation 10 (pixels)

  • mass 1 (unit is irrelevant for now, i modified velocity directly<-impulse method)

  • inertia 1/1000

Thanks in advance! I really appreciate any help from you guys!! :)

EDIT

In response to Cholesky's comment about warm starting the solver and Baumgarte: I forgot to mention! I do save the contact history and the impulse determined in this time step to be used as initial guess in the next time step.

As for the Baumgarte, here's what actually happens in the code. Collision is detected when the bodies' closest distance is less than SKIN, meaning they are actually still separated. If at this moment, I used the PGS solver without Baumgarte, restitution of 0 alone would be able to stop the bodies, separated by a distance of ~SKIN, in mid-air! So this isn't right, I want to have the bodies touching each other. So I turn on the Baumgarte, where its role is actually to pull the bodies together! Weird I know, a scheme intended to push the body apart becomes useful for the reverse.

Also, I found that if I increase the number of iteration to 100, stacks become much more stable, though the program becomes so slow.

UPDATE

Since the stack swings left and right, could it be something is wrong with my friction model?

Current friction constraint: relative_tangential_velocity = 0

share|improve this question
    
That's interesting... I'm surprised this doesn't make everything feel sticky. Have you tried not applying this adhesion stabilization and just letting numerical drift allow them to touch? –  Cholesky Nov 22 '12 at 13:34
    
Yeah. If I turned the adhesion stabilization off, objects will stabilize at a separation larger than 0 at arbitrary orientation (so e.g., a box falling onto the ground will stop before it even touches the ground). Also, this doesn't give rise to stickiness because the impulse (of the stabilization plus the normal force) can only push objects apart, but not pull together. The adhesion stabilization works because if it is on, then objects will be pushed apart less compared to when it is off. –  Register Sole Nov 23 '12 at 9:25

1 Answer 1

Are you maintaining contact history from frame to frame so you can warm start the solver? I wouldn't expect to be able to support stacking of more than a few bodies without temporal coherence.

It's also worth making sure you have a threshold that allows for a tiny bit of overlap before apply baumbarte stabilization so things aren't too "bouncy."

ie. if(penetration > someEpsilon) stabilization = stabilizationFactor * (penetration - someEpsilon)

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.