Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pybullet.getClosestPoints gives wrong distance with obj-models #4596

Open
hubernikus opened this issue Apr 11, 2024 · 0 comments
Open

pybullet.getClosestPoints gives wrong distance with obj-models #4596

hubernikus opened this issue Apr 11, 2024 · 0 comments

Comments

@hubernikus
Copy link

hubernikus commented Apr 11, 2024

I have decomposes a complex gripper of a robot into multiple convex parts in order to have a more precise distance measurement in real-time. The decomposition was performed manually with blender (but should be the same as is obtained using pybullet.vhacd).

In order to look at the behavior, I simplified the problem into an urdf containing a single link, with an *.obj file of two cubes (2x2x2). I create two instance of this urdf file, which are 10 meters apart from each other.

When computing the distance measurement between these to instance using pybullet.getClosestPoints, the shortest distance is ~18 (=17.998), even though the closest cubes have a distance of 2. This indicates, that pybullet.getClosestPoints does not consider all the convex objects in the file, but only parts of it.

The visualization of the *obj files works without issues.

Files to replicate the issue two_cubes.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant