This may end up needing to be a bug report instead of a question but:
I can't figure out how to bring up the atlas drcsim in the latest drcsim-groovy (3.2.0-1~precise)
When attempting:
roslaunch drcsim_gazebo atlas.launch
I get:
setting /run_id to 90cf90b2-d53d-11e3-a4b9-0025648c7b5e
process[rosout-1]: started with pid [30559]
started core service [/rosout]
process[gazebo-2]: started with pid [30573]
process[atlas_robot_state_publisher-3]: started with pid [30578]
process[multisense_sl_robot_state_publisher-4]: started with pid [30598]
[DEBUG] [ros.gazebo_ros.api_plugin]: GazeboRosApiPlugin Deconstructor start
[DEBUG] [ros.gazebo_ros.api_plugin]: After sigint_event unload
[DEBUG] [ros.gazebo_ros.api_plugin]: Deconstructor skipped because never loaded
process[tf2_buffer_server-5]: started with pid [30623]
[gazebo-2] process has finished cleanly
...
and then a bunch of multisense_sl
processes which stay up. The launch itself stays up until I interrupt it, but gazebo never comes up.
I've also tried:
# rosrun drcsim_gazebo run_gazebo atlas.world
Which results in:
[DEBUG] [ros.gazebo_ros.api_plugin]: GazeboRosApiPlugin Deconstructor start
[DEBUG] [ros.gazebo_ros.api_plugin]: After sigint_event unload
[DEBUG] [ros.gazebo_ros.api_plugin]: Deconstructor skipped because never loaded
[ /opt/ros/groovy/share/drcsim_gazebo/launch ]
#
I've checked the logs and see nothing suspicious. Since I can't find any errors or warnings, I'm not sure how to debug this situation.