-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mesh fails to load when filename attribute doesn't start with package:// #1741
Comments
I think relative paths are not supported by the convention. At first glance, we should be able to robustify to also handle relative path wrt the current file. @fabinsch Could you handle this issue? |
Hi @stephane-caron, I agree with @jcarpent : it is written in the ROS urdf specs that the However, I added the ability in Pinocchio to handle this kind of relative path in #1742. |
Thanks for checking 🙂 Unfortunately there are several URDFs out there that use relative paths, I just took that one as an example. From the sentence you quote, what the spec says is: "if you want to make the path relative to a package, then use
Looks perfect 👍 |
Solved by #1742. |
The description
cf2p.urdf
for the Crazyflie 2.0 drone does not load properly with pinocchio 2.6.3:I believe I have configured the mesh path properly. Here is why:
<mesh filename="./cf2.dae" scale=" 1 1 1"/>
package://
prefix:<mesh filename="package://./cf2.dae" scale=" 1 1 1"/>
, then the mesh loads properly and can e.g. be visualized in MeshCat:Is there indeed an inconsistency in the way pinocchio treats the optional
package://
prefix?(Relevant part of the URDF spec.)
The text was updated successfully, but these errors were encountered: