When starting gazebo there's no indication of which physics engine is being used in the console output. This would be handy to have in cases where lots of arguments are passed and one wants to see what physics engine is being used in the current run
$ gazebo --verbose -e bullet
Gazebo multi-robot simulator, version 9.4.1
Copyright (C) 2012 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org
[Msg] Waiting for master.
Gazebo multi-robot simulator, version 9.4.1
Copyright (C) 2012 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://127.0.0.1:11345
[Msg] Publicized address: 172.17.0.4
[Msg] Connected to gazebo master @ http://127.0.0.1:11345
[Msg] Publicized address: 172.17.0.4
[Wrn] [Publisher.cc:141] Queue limit reached for topic /gazebo/default/physics/contacts, deleting message. This warning is printed only once.
osrf-migration
commented
6 years ago
Original report (archived issue) by Shane Loretz (Bitbucket: Shane Loretz, GitHub: sloretz).
When starting gazebo there's no indication of which physics engine is being used in the console output. This would be handy to have in cases where lots of arguments are passed and one wants to see what physics engine is being used in the current run