PhysX-3.4 icon indicating copy to clipboard operation
PhysX-3.4 copied to clipboard

Published 20 hours ago • verified publisher icon NVIDIAGameWorks

Negatively scaled PxTriangleMesh collisions have penetration problems

Open sunwtGitHub opened this issue 3 years ago • 3 comments

I now have a step-shaped PxTriangleMesh and set its MeshScale value to PxVec3(-1, 1, 1). This results in a TriangleMesh that is a mirror image of the X-axis. Then roll a small ball down the top of the step. Each time the ball passes the edge of the step, it falls into the TriangleMesh and then pops out of the TriangleMesh. It looks like the edge of the steps didn't collide.

sunwtGitHub avatar Dec 23 '21 05:12 sunwtGitHub

Yes this bug has been fixed in PhysX 5. I am not sure how easy it would be to back-port to 4 or if there are plans to do so. Will ask around.

PierreTerdiman avatar Jan 03 '22 17:01 PierreTerdiman

Hmmm but you're using PhysX 3.4 anyway right? There's certainly no plan to port that fix back to PhysX3 unfortunately.

PierreTerdiman avatar Jan 03 '22 17:01 PierreTerdiman

Thanks for getting back to me. I did the same test with UE4 version 2.7 engine, but there was no similar BUG in UE4. The version of Physx3.4 engine they used seems to be released in 2017, while the version I used was released in 2018. By the way, when will we be able to use PhysX 5 in our own engines?

sunwtGitHub avatar Jan 11 '22 09:01 sunwtGitHub