Skip to content
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

ign-gazebo defaults to ogre2 rendering engine, that is not available #27

Closed
traversaro opened this issue Oct 12, 2021 · 8 comments
Closed

Comments

@traversaro
Copy link
Contributor

Launching ign gazebo on a platform where this is supported (as 6.0.0_h18f0bbf_1 only Linux) results in:

[GUI] [Err] [RenderEngineManager.cc:461] Failed to load plugin [ogre2] : couldn't find shared library.
[GUI] [Err] [MinimalScene.cc:514] Engine [ogre2] is not supported
[GUI] [Err] [MinimalScene.cc:653] Unable to initialize renderer
[GUI] [Err] [RenderEngineManager.cc:461] Failed to load plugin [ogre2] : couldn't find shared library.
[GUI] [Err] [MinimalScene.cc:514] Engine [ogre2] is not supported
[GUI] [Err] [MinimalScene.cc:653] Unable to initialize renderer

This is because ign gazebo defaults to ogre2, that is not packaged at the moment in conda-forge . To launch it, it is necessary to explicitly launch it with render engine ogre, via the --render-engine ogre option:

ign gazebo --render-engine ogre

It would be great to either package ogre2, or to patch ignition gazebo to use ogre as default render engine if ogre2 is not available.

@diegoferigo
Copy link

Another option, especially for those that are not using the command line to start Ignition Gazebo, is editing ~/.ignition/gazebo/6/gui.config and change //plugin[@filename=MinimalScene]/engine from ogre2 to ogre. Probably finding and patching this file could fix at least the new installations, since this file is copied into the user's home the first time Gazebo is launched.

@traversaro
Copy link
Contributor Author

Even with #28, ign gazebo shapes.sdf fails because ogre2 is not found. Probably we would need to change ogre2 to ogre in all the examples sdf files.

@diegoferigo
Copy link

Even with #28, ign gazebo shapes.sdf fails because ogre2 is not found. Probably we would need to change ogre2 to ogre in all the examples sdf files.

I fear this could not be a permanent workaround, since after gazebosim/gz-sim#278, most of the world files do not hardcode ogre2 but read the configuration file stored in the user's home. Something else worth noting is that in fortress, the configuration directory has changed gazebosim/gz-sim#1050.

@traversaro
Copy link
Contributor Author

traversaro commented Oct 27, 2021

Even with #28, ign gazebo shapes.sdf fails because ogre2 is not found. Probably we would need to change ogre2 to ogre in all the examples sdf files.

I fear this could not be a permanent workaround, since after ignitionrobotics/ign-gazebo#278, most of the world files do not hardcode ogre2 but read the configuration file stored in the user's home. Something else worth noting is that in fortress, the configuration directory has changed ignitionrobotics/ign-gazebo#1050.

I think that is problematic on many levels, so I opened a separate issue for that: #31 .

@traversaro
Copy link
Contributor Author

As it is clear from RoboStack/ros-galactic#104, it is not possible to install ogre 1.10 with ROS2, while we have problems with ogre 1.12 tracked in #6 . At this point, I think the only proper solution is to package ogre-next (what used to be called ogre2 and is still called ogre2 in Gazebo [that used to be called Ignition]). I was kind of waiting for OGRECave/ogre-next#259 to be fixed before so that we could install in the same environment ogre and ogre-next (otherwise we can't have Ignition Gazebo and RViz), but I guess there is no expected release date for that. Probably we could just package the latest ogre-next with a custom patch to fix OGRECave/ogre-next#259, that in the end is what OSRF is doing in their deb packages.

@traversaro
Copy link
Contributor Author

I tried to package ogre-next, but I got stuck as described in conda-forge/staged-recipes#19384 (comment) .

@traversaro
Copy link
Contributor Author

I tried to package ogre-next, but I got stuck as described in conda-forge/staged-recipes#19384 (comment) .

I then got unstack as described in later comments.

@traversaro
Copy link
Contributor Author

After:

This problem is solved, at least for Ignition Gazebo 6 on Linux :

rosignhumble

On WSLg this does not work, but for reason indipendent from the conda packaging that also affect apt packages (llvmpipe has a antialiasing problem, see gazebosim/gz-sim#1116, while d3d12 does not support the required GL_ARB_copy_image opengl extension).

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

No branches or pull requests

2 participants