m_normalWorldonB

[markhula]

Hi all,

During a collision this doesn't seem to always return the correct collision normal.
With a cube making contact on a flat plane I got:

0.000000 0.557960 0.829868
0.000000 -0.000003 1.000000
0.000000 -0.000003 1.000000
0.000001 0.000000 1.000000
-0.000001 0.000000 1.000000
0.000000 -0.000003 1.000000
0.000000 0.000006 1.000000
0.000003 0.000000 1.000000
0.000000 0.000000 1.000000
0.000000 0.557960 0.829868
0.000000 0.557959 0.829869
0.000000 0.557960 0.829868
0.000000 0.557960 0.829868

Surely the Y component is bouncing around too much?

In my collision callback I simply:

terrain_normal=_btManifoldPoint.m_normalWorldOnB;

Please tell me where I am going wrong or indeed my mis-understanding/mis-use of m_normalWorldOnB.

Thanks in advance

[SteveDeFacto]

Bump. I'm having the same problem and the random variations in the normal are a serious problem for me. Can this be fixed?

[Erwin Coumans]

Is this against a btStaticPlaneShape?

[SteveDeFacto]

Is this against a btStaticPlaneShape?

For me it's a btBvhTriangleMeshShape.

[MaxDZ8]

Is this against a btStaticPlaneShape?

By the way, I have tried BasicDemo with btStaticPlaneShape. Looks like restitution is much stronger than the default btBoxShape. I'd like to have a better understanding of what's happening. It is my current understanding that btStaticPlaneShape will avoid quantum effects completely being effectively an infinitely tick, infinitely wide brick but I wasn't expecting a so different result. Is it intended?