PhysX related error

Okay, so I’ve just upgraded our huge project to Unity 5.0.0.b12 to see how many problems that would give etc. And as soon as I click on one the objects in the world during runtime I get the following error:

m_Actor->getNbShapes() == 0

Just that, without a stacktrace or anything to help me debug it. As far as I can tell from google it’s a PhysX related issue. I’ve tried to trace it so I could create a smaller sample project to reproduce this error and file a bug report, but I can’t figure out what’s causing it. We have a lot of logic surrounding the selection of an object and the closest I’ve been able to get is that it’s something that happens after the MouseUp logic’s done.

Has anybody else run into this or a similar error or does anyone have any idea where to start looking for the cause?

EDIT: So I checked with colleagues and apparently we destroy the rigid collider after we finish dragging an object. Gonna search further.

Search before posting, we have thread dedicated to new physx, no need to have more.

Yes I know this thread exists, but I read it and I didn’t think that was the best place to post my problem as it’s a more of a features rather than issues thread imho. If any of the moderators disagree with me please close this thread.

This sounds like a bug, please send a bug report with a repro case.

@jonas-echterhoff_1 I’ll try to create a repro project and send it with a bug report today.

Found the source of the bug, if you destroy a Rigidbody with the Is Kinematic flag set you get this error. Create a repro project and submitted a bug report. Just adding this to the thread in case others run into the same error.

Thanks, we found the bug and fixed it - expect the fix in a future 5.0 build.

1 Like

Nice. I’ll look forward to the fix. ^^