Closed dyspr0sium closed 4 years ago
I can't tell much without checking out the mesh files.
Sure, here are the meshes. The original files from SolidWorks are STL but I converted them to OBJ because there was an error importing the original STL meshes into raisim.
I should add that the URDF, regardless of STL or OBJ meshes, was checked to work correctly in PyBullet.
well, apparently I was wrong about the obj convention. You obj file has a line like
v -0.00381818 0.000196837 -0.00616337
There are two spaces after the "v". same for "f". My obj reader can only read if there is only one space...
I fixed this is in V1.0 but you can't get this version yet. I suggest just replace all double spaces with a single space. Thank you for reporting this bug
and your meshes seem very fine. This creates so much burden on collision detection. You will lose the benefits of the super-fast dynamics solver of RaiSim with this model...
Perfect, thank you very much. The issue is resolved after replacing all double spaces with single spaces in the OBJ files.
I will consider replacing the collision boxes with simple shapes if the performance too slow due to the fine meshes.
I am writing a Gym environment for a robot in Python using raisimpy, following the ANYmal example environment from raisimpy's examples. The ANYmal URDF loads in fine but using a URDF exported from SolidWorks, I cannot see the robot on the floor. With the floor not loaded visually in raisimOgre, I can see the robot falling down to infinity. I suspect there is a problem with the collision properties in the URDF, which are linked to OBJ files exported from SolidWorks rather than simple shapes defined directly in the URDF. The URDF is as follows:
I can provide the collision OBJs if necessary. Appreciate any help.