Gazebo 8 support #536
Comments
|
Thanks for the report Ben. Could you please try to run the standalone gazebo to see if it runs? If gazebo runs, could you run with |
|
Hi Jose, Thanks for the quick reply.
|
Thanks for the quick test. Another question: is the standalone gazebo (no ROS) able to load the worlds? |
|
Yeah: |
|
Thanks. Looks like we will need to debug what's going on with the parameter passing mechanism. I need to find some time for this. |
|
Hey Jose -- do you debug in a Docker environment? If so, here's the docker file to run Ubuntu 16.04/ROS Kinetic/Gazebo 8: https://github.com/BenBlumer/gazebo8_with_ros_docker |
|
I know you guys have changed the support cycle of Gazebo + Kinetic: out of curiosity, how many version of Gazebo will the |
From experience, being an LTS, it is hard to say but we have been supporting in Indigo every single Gazebo version out there. |
|
I tested the current kinetic-devel branch together with gazebo8 and they seems to work pretty well on my system. I've created the binary packages: https://discourse.ros.org/t/gazebo8-ros-kinetic-wrappers-available/1585 @BenBlumer could you confirm that they work for you? |
|
Please reopen if the problem persists |
|
Hi Jose, I've tested a few install options in Docker and:
I'll try a couple more approaches and update. |
|
Basically, from an install of ros-kinetic-desktop-full (Using OSRFs dockerfile), followed by the instructions:
I get a series of errors which seem to boil down to a conflict between ros-kinetic-gazebo8-msgs and ros-kinetic-desktop-full: |
|
OK, so you can get it to install by installing gazebo8-msgs first. Sample Dockerfile attached. But unfortunately, |
Hello Ben. The problem seems related to a conflict between the Solutions could be:
They are working on my Xenial system (no docker, just plain system). You could be facing a problem related to docker interaction with the X system. I highly recommend to check out the ROS page related to this topic |
|
Hi Jose, I don't believe it's related to the X system because my system works fine with Gazebo 7 in docker both as Gazebo stand alone as well as using roslaunch (see attached) thanks to the methods posted on the page you linked to. To solve the conflicts, I've tried starting from kinetic-ros-base and installing Gazebo 8 from the OSRF repo. Indeed, there are no conflicting packages anymore, but Gazebo crashes when, and only when, I roslaunch it; it runs fine as a stand alone. I've attached the message from the crash. Does this mean anything to you? |
|
Anddddd ... To make things more interesting: If one first launches gzclient you still get the same crash log (big stack trace followed by I figure this has to be something about the way that ros_gazebo is interacting with ros or gazebo (otherwise standalone Gazebo wouldn't work and gazebo_ros wouldn't work even with a workaround). Perhaps something related to this . Thoughts? |
|
@j-rivero Did this issue have been resolved? And could we use |
|
hhhm I'm getting error trying to run gazebo 8 with ROS of the sort: Anyone else? Edit: Looks like the same error as @BenBlumer |
The issue is resolved in the sense that we have now kinetic packages supporting
This has nothing to do with the original goal of the issue and the problem was introduced in |
I've installed Gazebo 8 with ROS Kinetic on Ubuntu 16.04 in a Docker container.
apt-get install -y libignition-math3Then pulled the gazebo_ros package into a catkin_workspace and built.
Any roslaunch of the gazebo_ros package will open Gazebo, and seemingly start up ROS packages, but it won't actually launch the world file. To replicate, install Gazebo as described above and
roslaunch gazebo_ros mud_world.launch. You'll see nothing is actually in place.The text was updated successfully, but these errors were encountered: