Skip to content

Adding logging to previously silent mesh finding failure.#188

Open
ethanfowler wants to merge 1 commit intoosrf:gzweb_1.4.0from
shadow-robot:F_#SRC-4999_mesh_path_logging
Open

Adding logging to previously silent mesh finding failure.#188
ethanfowler wants to merge 1 commit intoosrf:gzweb_1.4.0from
shadow-robot:F_#SRC-4999_mesh_path_logging

Conversation

@ethanfowler
Copy link

This silent failure to resolve meshes frustrated me for a while, thought I'd save someone else the trouble. Not sure which other branches/tags might want this merging?

'". Mesh URIs using an absolute path syntax should use ' +
'the ROS-standard directory structure of ' +
'"<package_path>/meshes/<mesh_path>", e.g. ' +
'"/home/user/workspace/src/ur_description/meshes/base.dae".');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GzWeb is not ROS-specific, do you mind rephrasing the warning so it doesn't mention ROS? I know that the comment above mentions gazebo_ros_pkgs as an example of how a user may end up here, but there are other ways in which absolute paths could be passed to Gazebo too.

How about something like:

"Mesh URIs using an absolute path syntax should be located inside a meshes directory, e.g. /home/user/workspace/src/ur_description/meshes/base.dae"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants