Hi all, visualization_common 1.1.0 and visualization 1.1.0 have been released. This is an **unstable** development release to try out features considered for inclusion in their 1.2 versions. visualization 1.0 will work with visualization_common 1.1, but visualization 1.1 requires visualization_common 1.1. The largest changes in these releases involve additions to the visualization_msgs/Marker API, see below for details. visualization_common 1.1 changelist: - visualization_msgs - Marker - Added support for meshes -- MESH_RESOURCE type and mesh_resourcemember. This allows you to specify a mesh resource by URI (e.g. package://pkg/file) - Added TEXT_VIEW_FACING type and text member - Added frame_locked member that specifies the marker should be continually re-transformed into its frame - Added colors member for per-point/line color - ogre_tools - PointCloud: Added outlines on billboards and boxes visualization 1.1 changelist: - rviz - Added dialog which is shown when it cannot contact the master. No longer fully initializes and then closes immediately (r28449) - TF Display: added "Frame Timeout" option, which will fade out frames when we haven't received data about them in a certain amount of time. Defaults to 15 seconds. (#3825, r28455) - Ogre.log file is now suppressed by default, with a command line option (-l) to turn it on (r28432) - Fixed relative paths passed to -d command-line options (r28429) - Marker Display - New MESH_RESOURCE marker type that can load meshes from disk/web - New TEXT_VIEW_FACING marker type for displaying text - New frame locked option for markers, which automatically retransforms them into a frame every update cycle - Support for per-point color for POINT, CUBE_LIST, LINE_LIST and LINE_STRIP markers. Does not yet support per-point alpha though the capability exists in the message. - POINT, CUBE_LIST, LINE_LIST and LINE_STRIP markers no longer throw away messages with empty points members (#3839, r28128) - Camera Display now uses image_transport, with a dropdown to choose from the available transport types. It does not yet have any way of knowing which transport plugins are loaded however ( #3974 ) - Moved rendering into an idle callback, which should be a better way of keeping the UI responsive Josh