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

Disable the automatic loading of Gazebo Server plugins #289

Closed
diegoferigo opened this issue Feb 3, 2021 · 2 comments · Fixed by #379
Closed

Disable the automatic loading of Gazebo Server plugins #289

diegoferigo opened this issue Feb 3, 2021 · 2 comments · Fixed by #379

Comments

@diegoferigo
Copy link
Collaborator

After gazebosim/gz-sim#281, if the SDF world file does not specify any plugin (such as physics, scene broadcaster, etc), the server will load a default set of plugins specified in a new server.config file.

This likely will alter the situation we were expecting before. In fact, we offer and use programmatic APIs to load world and model plugins. We don't expect any plugin to be loaded by default.

I still have to update my source installation (the PR was merged into dome with gazebosim/gz-sim#602 just yesterday). I hope that by exporting an empty IGN_GAZEBO_SERVER_CONFIG_PATH as documented here would suffice.

@diegoferigo
Copy link
Collaborator Author

At first look, the server.config file is read when no plugins are specified in the following locations:

  • SDF world file
  • ServerConfig object passed to Server

Waiting to address , we rely on a workaround involving a singleton (-.-) to get the full simulation state, implemented as a plugin loaded through ServerConfig:

https://github.com/robotology/gym-ignition/blob/50caccfa1b5ddb617ec0b1aea98bfec72c8fbadf/cpp/scenario/gazebo/src/GazeboSimulator.cpp#L648-L652

I leave this issue open as reminder. Until we keep this workaround, no action is necessary. Exporting an empty IGN_GAZEBO_SERVER_CONFIG_PATH as documented would not harm, however now is is not yet strictly needed in our current situation.

@diegoferigo
Copy link
Collaborator Author

Closed via #379.

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

Successfully merging a pull request may close this issue.

1 participant