Plugin Distribution

Last validated: 2026-05-05

Plugins are dynamic libraries loaded by Oden. They normally end in .dll on Windows and .so on Linux.

Project plugins

Use project plugins when the plugin belongs to one .vproj.

  1. Put the plugin and runtime dependencies in a folder beside the project, for example bin.

  2. Set the project plugin path.

  3. Save and reopen the project.

  4. Add the plugin entity or configure the plugin-provided settings.

Relative plugin paths are useful when the project and plugin folder move together.

Global plugins

Use global plugins when the plugin should run without being added to the scene graph. Global plugins must be installed where the Player or Streamer scans application-level plugins.

Restart Oden after changing global plugin paths or replacing global plugin binaries.

Deployment checks

Before shipping a plugin deployment:

  • Match operating system, CPU architecture, and Oden build.

  • Include all runtime dependencies.

  • Check Windows dependencies with Dependencies GUI.

  • Check Linux dependencies with ldd -r -d ./plugin.so.

  • Keep plugin versions aligned with the Oden version deployed to the vehicle and operator.

  • Disable hot reload in production.

See Plugins for detailed loading and troubleshooting.