Skip to main content
Realsee
Dashboard
Sign out
Documentation
Docs
/
Dnalogel

Dnalogel

Five SDK plugin collection for spatial UI layers, floorplans, labels, rulers, camera motion, and custom interaction.

@realsee/dnalogel@3.81.0 is the Realsee Five SDK plugin collection. It packages common VR space interaction capabilities as Five SDK plugins: floorplan overlays, model labels, panorama rulers, camera motion, CSS3D rendering, cruise paths, item labels, video layers, and other spatial UI primitives.

Register a concrete exported plugin class when creating the Five SDK instance:

import { Five } from '@realsee/five'
import { PanoRulerPlugin } from '@realsee/dnalogel'

const five = new Five({
  plugins: [[PanoRulerPlugin, 'PanoRulerPlugin', {}]],
})

After this registration, the plugin instance is exposed as five.plugins.PanoRulerPlugin. Individual plugin methods vary, but common plugin lifecycles include loading data, enabling, disabling, and disposal.

Version note

This page is adapted for the overseas package metadata available from npm:

PackageVerified versionSource
@realsee/dnalogel3.81.0npm package metadata and libs/index.d.ts
@realsee/five used by the package build6.6.18package devDependencies
Portal Five SDK version@realsee/five@6.8.9local portal dependency

Because the Dnalogel package build is verified against @realsee/five@6.6.18 while this portal uses @realsee/five@6.8.9, validate each plugin in your target scene before shipping. The public exports are available, but plugin behavior can depend on Five SDK renderer internals.

When to use Dnalogel

  • Add spatial UI layers to a Five SDK scene without building every object from scratch.
  • Show floorplan radar, model room labels, or panorama measurement helpers.
  • Drive camera movement, cruise paths, or guided interaction flows.
  • Render CSS3D or video content inside a spatial scene.

Data dependency

Many plugins depend on scene-specific data from Realsee OpenAPI or from your own backend. Use the OpenAPI overview to plan server-side data access and Team and App Management to request the Developer app credentials required for production calls.

Next steps