PR2 robot model is not shown in Rvizweb #31
Comments
|
What distro are you in, and if you built any dependencies from source, what are their versions? Also, do you see any error messages on the browser console? I'd expect some network errors failing to fetch mesh files. |
|
my distro is Kinetic. console output is below. |
|
I launch like this |
|
This is happening since we updated Note however that the problem is with PR2's mesh in particular, not all meshes. I've tried other meshes like Turtlebot and UR arms and they worked well (see this comment for reference). @chapulina the meshes of the PR2 are several years old now; perhaps there's some format incompatibility, and the logs show no errors when loading. This doesn't seem to be a general problem with meshes but a particular one with PR2, so unless more cases like this appear I'd say the problem is not critical. I'll take a look anyways and see if there's anything that can be done with the current library. |
Yes, I already tried baxter, UR and turtlebot and it works! |
Oh ok, I didn't realize the PR2 hadn't been fixed after the referenced comment.
We had previously noted that the PR2 textures weren't well supported because they're in the TIFF format: osrf/polymer-ros-rviz#3 , maybe it could be related? I wouldn't expect them to show transparent in this case though... Maybe it's worth trying to convert them to png and see if it works just in case. |
|
I convert all
|
|
RobotWebTools/ros3djs#209 (comment) |
|
Thanks for the pointers and the update @knorth55! @chapulina please let me know if you think we should still look into this (although the solution might be patching the dependencies?), or if adding a notice in the documentation is enough. |
|
We could make a PR to We could also try the suggestion on PR2/pr2_common#226 (comment) and "do the tiff to png conversion on the fly whenever a browser requests a texture", but this feels overkill just to get the PR2 to work. It's worth mentioning that the previous THREE.js version did show the tiff textures, but they weren't lit properly. So there may be something we can improve in the front-end, but again, I think it's not worth it just for the PR2. I'm in favor of updating the README examples not to use the PR2 and close this issue. People having the same problem should hopefully get to this issue for reference and we can always accept pull requests improving tiffs if someone feels strongly about the PR2. |
|
There are two problems.
|
👍
@knorth55 sounds good. Note that in the comment referenced above (PR2/pr2_common#226 (comment)) the first suggestion is adding a buildstep that converts the meshes to png. That could work, and maybe it's more likely to be accepted upstream rather than just replacing the meshes.
Does that happen to you with Turtlebot and Baxter as well? From #31 (comment) I understood those meshes could be loaded without problems. |
how to convert all *.tif to *.png for PR2 meshes? |
|
PR2 robot model is not shown in Rvizweb!!! |
|
@yzczuzu you can use |
ubuntu@ubuntu:~/catkin_ws/src$ convert *.tiff .png It is not working when I am running this command. |
|
ubuntu@ubuntu:~/catkin_ws/src$ convert *.tiff .png |
|
@yzczuzu you need to be in the directory where the |
ubuntu@ubuntu:~/Desktop/pr2_common-melodic-devel/pr2_description$ convert *.tiff .png I did that in the pr2_description. But still not working. Can u tell me how to do that in detail??? |
|
@yzczuzu The error message said that there is no |
I download your branch. Then I launch the simulation by command |
|
@yzczuzu I cannot reproduce your error, so I cannot help you. |
Thanks for helping! |
Some links in PR2 are not shown in Rvizweb.
The issue is reported in #12 (comment), but I could not find out how to fix this problem.
The text was updated successfully, but these errors were encountered: