PxMeshQuery::findOverlapTriangleMesh different results between standalone PhysX app vs Omniverse C++ extension

Omniverse Developer Tools & Resources Developer Tools
1

I am using PxMeshQuery::findOverlapTriangleMesh to query Intersecting faces and using the below callback to get faces indices

The issue:
Using PhysX api in omniverse c++ extension, When a triangle face is completely enclosed by a the opposing triangle mesh it does not get reported in PxMeshQuery::findOverlapTriangleMesh callback object…also note the face in question from mesh1 is coplanar (and opposing) to the supposed face from mesh2.

The same problem is not present when using the same api in an standalone PhysX app.

I apologize for the vague description of the problem, but I want to get insights on what to look for, what kind of flags or mesh properties might cause this?

2

Ok let me run this by the physics team.

3

Thanks Richard,

Actually the discrepancy between the 2 cases was caused by a bug in my own implementation. the API reports the same pairs in both cases.

but It seems that faces which are completely enclosed by the opposing mesh do not get reported in callback.
Is there way to get those triangles as well through PhysX?

4

This is expected behavior because meshes are treated as a surface and not as a volume. If you want a volume you need to go with a convex mesh approximation or an SDF.