Projects and Web Configurations

Last validated: 2026-05-05

Oden has two related configuration layers.

Oden project files

.vproj files loaded by Oden Streamer, OdenVR, or Oden Dome Player. They contain scenes, entities, camera inputs, stream settings, network links, plugins, and display behavior.

Web configurations

Portal-backed or customer-hosted web projects that drive operator UI, vehicle selection, video layout, widgets, and control panels through Oden’s webview integration.

Preferred self-serve model

For new self-serve users, the portal should own the project-level setup:

  • Which vehicles belong to the account.

  • Which operator can access which vehicle.

  • Which Streamer package and license context belongs on the vehicle.

  • Which operator controls and widgets are shown.

  • Which web-based layout or project should open for the operator.

This lets the first useful setup happen without manually editing .vproj files.

When .vproj projects still matter

.vproj files remain the low-level Oden project format. Use them when you need direct control over:

  • Camera inputs and Streamer output.

  • Entity placement and native Player layout.

  • Stitched video, dome projection, VR, or multi-monitor display.

  • Project plugin paths and plugin entities.

  • Service startup projects such as /opt/oden-streamer/oden-vehicle-config.vproj.

For the detailed project model, see Projects and Scenes.

Web-based operator layouts

Web-based operator layouts use the Oden WebView plugin and JavaScript SDK. The web page creates DOM regions for video, widgets, gauges, maps, or controls. Oden draws the actual video surfaces in those regions.

For details, see:

Gated enterprise features

Non-web-login usage, custom web-page hosting, and customer-specific authentication flows are enterprise features. They are powerful, but they also affect who can operate a vehicle and what project is loaded for that operator. Voysys should be involved when you need those flows.