Broadphase and ObjectLayer filters are missing context about joltphysics HOT 4 CLOSED

In general:

• Broadphase layer: each broad phase layer will result in it's own quad tree so you should not have too many of them. A static layer, dynamic layer, query shapes layer, triggers layer is roughly how we have things set up.
• Object layer: An object layer maps to one or more broadphase layers to test against, this allows you to very quickly discard large amounts of bodies.
• Group filter: Most expensive filtering (bounding boxes already overlap), used only during simulation. Allows you fine tune collision e.g. by discarding collisions between bodies connected by a constraint (see GroupFilterTable).
• Body filter: This filter is used instead of the group filter if you do collision queries like CastRay.

And you're right that the ObjectVsBroadPhaseLayerFilter and ObjectLayerPairFilter should have been interfaces. The interfaces in NarrowPhaseQuery used to be function pointers too at some point. I just didn't change these yet. I'll see if I can change this.

from joltphysics.

I guess the GroupFilter is the most flexible, but also the slowest one. Not sure exactly when this is really needed, maybe for very special cases like the player object ?

I found it necessary to provide my own group filter class to disable collisions between jointed objects, as it is not supported out-of-the-box by Jolt.

from joltphysics.

Was this change integrated? It looks like it wasn't, but maybe I wasn't looking in the right spot.

from joltphysics.

No the broadphase and object layer filters still don't have a context, I never got around to implementing it. It should only be a problem though if you have multiple PhysicsSystems in your application that use different layer configurations.

from joltphysics.