FixtureDef filter.groupIndex bug about libgdx HOT 5 CLOSED

From badlogicgames on June 29, 2010 08:40:56

Hm, i'll be looking into it tomorrow.

Status: Accepted
Owner: badlogicgames

from libgdx.

From [email protected] on June 29, 2010 09:28:09

I did look again at it, and i was sucessfully able to use it. There is a difference tought with stock box2d/jbox2d (it seems). I had to set my ground fixture def and collide bodys groupeIndex to 1 then it work, while with jbox2d/box2d the ground groupeIndex is not set and other collide body are set to -1.
Hope it help.

from libgdx.

From [email protected] on June 29, 2010 10:45:05

Sorry for the spam ... would it be possible to get a mail address ? I'd like to send you a code i wrote. It don't react the same way on the computer and on the phone. I'v wrote a motorcycle code, it run very well on the computer side, but it does react strange on the phone. The wheel (RevoluteJoint) is not solid to the chassis. Can't explain very well :)

from libgdx.

From [email protected] on June 29, 2010 13:52:04

My last problem seems to be related to a fixture "restitution" parameter bug on the android side. A low value will cause the body to bug when it is in contact with an oriented shape while a high value will of course make it too "elastic".

from libgdx.

From badlogicgames on July 15, 2010 03:26:54

I modified the Box2DTest like this: ground fixture has groupIndex 0, all boxes have group index set to -1. Boxes don't collide with each other but only with the ground. I guess without a sample i can't reproduce your problem. I set this to WontFix in the meantime, if you happen to be able to provide me with a test case i'll reopen it.

Concerning your "restitution" problem i again would need a sample. As we discussed seperately it is connected to you not using a fixed time step, which i could reproduce with a slow software OpenGL renderer on my desktop.

Status: WontFix

from libgdx.