You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, maybe I am wrong but it seems that it is not possible to automatically use collision mesh of the custom end-effector. In the RVIZ I wanted to have both models: precise = visual and simplified = collision. In the xarm_description/meshes I created a custom_directory with visual and collision folders and proper stl files with the same names. I adjusted the demo.launch. As an argument I set add_other_geometry as true and geometry_type as mesh. I recommend to add an information in manual or change the code in file other_geometry.urdf.xacro as follows:
Thanks for your suggestion, we will consider this modification in later commits. In the mean time, you may fork and modify the code to suit your needs.
Hi, maybe I am wrong but it seems that it is not possible to automatically use collision mesh of the custom end-effector. In the RVIZ I wanted to have both models:
precise = visual
andsimplified = collision
. In thexarm_description/meshes
I created acustom_directory
with visual and collision folders and properstl
files with the same names. I adjusted the demo.launch. As an argument I setadd_other_geometry
astrue
andgeometry_type
asmesh
. I recommend to add an information in manual or change the code in fileother_geometry.urdf.xacro
as follows:and
The text was updated successfully, but these errors were encountered: