Supported Components

Overview

realvirtual WEB reconstructs a running digital twin in the browser from a single GLB file. All component configuration is embedded in the GLB using the rv_extras (REALVIRTUAL) extension during Unity export, and the browser viewer reads this metadata to recreate the simulation, the 3D-HMI and the digital-twin links — no separate configuration files.

This page lists the Unity C# components that are exported and supported in realvirtual WEB, grouped by area. Component names in the browser match their Unity counterparts, so a scene authored in Unity behaves the same way in the browser.

Note

Support is defined by the rv-ODT v1 interchange schema. Everything below is read from the GLB and reconstructed automatically. Components not listed here are either Unity-only or belong to a runtime layer outside the interchange format (for example the in-browser DES engine and library behaviors).

Motion & Drives

The Drive component and its drive behaviors are fully supported, including position, speed and acceleration control with limits.

Component	What runs in realvirtual WEB
Drive	Linear (X/Y/Z) and rotational motion, limits, acceleration, current position
Drive_Simple	Jog forward/backward with speed and position feedback
Drive_Speed	Speed-controlled motion from a PLC target-speed signal
Drive_DestinationMotor	Point-to-point positioning (start → destination) with feedback
Drive_FollowPosition	Drive directly follows a PLC position signal (scale + offset)
Drive_Cylinder	Two-position pneumatic cylinder with end-position feedback
Drive_Gear	Slave a drive to a master drive with gear ratio and offset
Drive_PositionSwitch	Bool output while the drive is inside configured position areas
Drive_ErraticPosition	Random / alternating motion between min and max
DrivesRecorder / ReplayRecording	Record and replay drive motion sequences, signal-triggered

Caution

Drive_CAM (cam-disc coupling) is reserved in the schema and is not simulated in realvirtual WEB yet.

Kinematics & Robotics

Component	What runs in realvirtual WEB
Kinematic	Kinematic hierarchy re-parenting (integrate group / kinematic parenting, hierarchy simplification) applied on load
RobotIK	Inverse-kinematics solver configuration on the robot root (spherical / non-spherical wrist)
IKPath	Ordered list of IK targets forming a robot path, with start/end signals and looping
IKTarget	Target pose, interpolation and blending, pick/place configuration

Transport & Material Flow

Component	What runs in realvirtual WEB
TransportSurface	Conveyor surface moving MUs along a direction at the referenced drive’s speed; accumulation and radial turntables
Source	Spawns MUs by interval or distance and places them on the transport system
Sink	Destroys MUs that reach it
MU	Movable-Unit template that the Source clones
Grip	Pick-and-place gripper (1-bit or pick/place signals, auto / static / physics place modes)
GripTarget	Snap / align marker for precise MU placement
Path	Arc-length path for path-based movement (AGV / overhead conveyors); line and arc segments with graph chaining

Sensors

Component	What runs in realvirtual WEB
Sensor	Presence sensor (AABB overlap or raycast); occupied / not-occupied PLC signals

Signals & Logic

Component	What runs in realvirtual WEB
PLC Signals	PLCInputBool/Float/Int and PLCOutputBool/Float/Int are registered in the browser SignalStore and drive all components
ConnectSignal	One-way signal bridge that copies a source signal onto its own signal
LogicStep	Sequencing steps: serial / parallel containers, delay, set/wait signal (bool & float), wait for sensor, drive-to / start-drive / set-drive-speed, wait for drives at target, enable, grip pick / place, IK path, jump on signal

Note

Live signals arrive over WebSocket, MQTT or REST and always override local behavior immediately. Signal direction follows the PLC convention — PLC Outputs are read by the viewer, PLC Inputs are written by the viewer.

3D-HMI

Marker components authored in Unity that build the browser-based 3D-HMI. For field-level details and authoring workflow see Building a 3D-HMI.

Component	What runs in realvirtual WEB
WebSensor	Signal-bound status indicator with Low / High / Warning / Error states (ISA-101 colors, blink) and optional label
WebError	Bool-signal error state: 3D badge + entry in the message panel; configurable highlight
WebVisibility	Show / hide parts from a bool signal, plus an optional error state
WebSafetyDoor	Safety-door overlay with hazard-zone halo and label
CustomRuntimeInstruction	Signal-activated operator instruction: multi-step, per-step 3D highlight / isolate, optional document link
RuntimeMetadata	Tooltip / annotation content (article numbers, descriptions) shown on hover and used for document linking
WebDiagnostics (preview)	Couples a PLC error signal to AI error diagnosis — currently a realvirtual WEB feature; the Unity authoring component is planned

Message panels, KPI dashboards and drive / sensor tooltips are provided by realvirtual WEB itself and are driven by the components above and by live signals.

Digital Twin Integration

Component	What runs in realvirtual WEB
AASLink	Links a part to an Asset Administration Shell (AASX from a local folder or a server URL); shows Nameplate and Technical Data as a tooltip
CADLink	CAD-import provenance metadata and in-browser re-import

Scene & Structure

Component / feature	What runs in realvirtual WEB
Group	Named group membership drives visibility groups
WebPivot	Explicit pivot point for a library object (used at import / placement time)
Connections	Self-describing typed connections (for example sensor → station stop-on-exit)
Camera presets, Measurement	Provided by the viewer at runtime (camera views, distance measurement)

Extensibility

Feature	What runs in realvirtual WEB
WebComponent (GLB-embedded JS)	Sandboxed setup(self) behavior scripts embedded in the GLB, executed in a secure in-browser sandbox (opt-in)

See Also

• realvirtual WEB — export and publish workflow
• Building a 3D-HMI — authoring the Web* 3D-HMI components in Unity