You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to use pr2_description for web applications, but some kinds of web browser (ex. google chrome, firefox) cannot load tiff format. So textures cannot be displayed in WebGL screen. (We use ros3djs in RobotWebTools).
Therefore we suggest that png format (which is compatible with web browser) should be used instead.
I wish to get some opinions.
The text was updated successfully, but these errors were encountered:
I'm not sure why tiff is used as the image format for textures. I think it would be good to keep the tiff textures around to maintain compatibility with packages that use them.
I have two suggestions on how you can proceed:
Add a build step to pr2_description the converts the tiff textures to png and install them alongside the existing tiff textures. If you submit this as a pull request, it can benefit the rest of the community as well.
Set up your web server to do the tiff to png conversion on the fly whenever a browser requests a texture.
We want to use pr2_description for web applications, but some kinds of web browser (ex. google chrome, firefox) cannot load tiff format. So textures cannot be displayed in WebGL screen. (We use ros3djs in RobotWebTools).
Therefore we suggest that png format (which is compatible with web browser) should be used instead.
I wish to get some opinions.
The text was updated successfully, but these errors were encountered: