-
Notifications
You must be signed in to change notification settings - Fork 44
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
[BUG]SAPIEN 2.2.2 cannot drive the dexterous hand properly. #196
Comments
My guess is that the issue is caused by cylinder collisions, which are not supported in SAPIEN 2 (which converts cylinders to capsules) but supported in SAPIEN 3 (by converting cylinders to meshes with a similar shape). You can verify this by removing all the cylinder collisions and try SAPIEN 2 and 3 again. |
I have already removed all collisions in the URDF, but the issue has not been resolved. |
The other thing to try is to increase the mass and inertia of all links, and make sure the mass and diagonal of the inertia are at least 1e-6. PhysX is known to skip solving links with small mass properties. SAPIEN 3 does this kind of checking for you but SAPIEN 2 does not. |
Thanks! It makes sense when I increase the mass of the dexterous hands links. |
System:
Describe the bug
When importing a humanoid robot URDF with dexterous hands, the intermediate_joint for both the left and right hands fails to correctly drive or display in SAPIEN 2.2.2. However, the same URDF works as expected in SAPIEN 3.0.0b1. Since SAPIEN 2.2.2 is required for ManiSkill2 compatibility, it is crucial to resolve this issue in the older version for me.
To Reproduce
Steps to reproduce the behavior (use pastebin for code):
Expected behavior
The intermediate_joint for both hands should be correctly driven and displayed, as observed in SAPIEN 3.0.0b1.
Screenshots
If applicable, add screenshots to help explain your problem.
SAPIEN2.2.2:
https://github.com/user-attachments/assets/c8c4e2c7-e305-4374-bc09-c4eaad7bcf9e
SAPIEN3.0.0:
https://github.com/user-attachments/assets/b245b704-9b21-4b33-83c5-d66b7b54da7f
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: