1. OpenSourceRoboticsFoundation
  2. Simulation
  3. gazebo
  4. Issues
Issue #2072 new

Gazebo cannot handle collada files as collision mesh

Stephan Opfer
created an issue


I created a collada mesh (Floorplan.dae) which drives gazebo crazy. It is loadable and gazebo does not crash, but when I spawn a TurtleBot on it, the TurtleBot gets twisting wheels and is hovering and hopping around.

Here are some more details: http://answers.gazebosim.org/question/14591/why-does-my-custom-collada-mesh-makes-the-turtlebot-wheels-twist/

I am using Gazebo 7.0.0 with ROS Kinetic under Ubuntu 16.04 LTS.

The collada file in question is attached.

Greetings, Stephan

Comments (6)

  1. Steven Peters

    There are often multiple equivalent ways to represent a collision geometry. For example, you have represented that floorpan with a triangle-mesh, but it could also be represented with a collection of boxes. I think gazebo's collision engine would work much better if it was expressed as boxes.

    You may also be interested in the building editor, which is a graphical interface for drawing walls and floorpans, which happens to generate box shapes so that gazebo's collision engine is happier.

  2. Stephan Opfer reporter

    Hi Steven,

    the building editor cannot open a building again, in order to make adjustments in it. So that is no option for me.

    Currently I transformed the collada mesh into stl format and don't get problems anymore. I simply imported the .dae file in meshlab and exported it to .stl.

    If collada makes problems for the collision engine, is there a tutorial/documentation that mentions the option of using .stl files as alternative?

    Greetings, Stephan

  3. Stefan Kohlbrecher

    I also found that .dae files are buggy when used for collision geometry. As mentioned before, converting to .stl fixes the issue, so as a standard procedure I'd recommend never using .dae collision geom, instead always using a mesh converted to .stl (or using primitives instead to be faster).

    /edit: I think I observed issues with .daes that contain different materials/groups internally, so maybe the loader gets confused by those.

  4. Log in to comment