Computed signals: combine inputs before mapping

简体中文 | English

Use a computed signal to turn several readings into one reusable result. Select the inputs, choose an operation and tune its response; then give the result a name and select it in any output binding. This reference starts with everyday combinations and continues into spatial and temporal operations.

Workbench operation · Sources and outputs

From inputs to motion

OSC/tracking, manual, script, feedback, replay or constants
                         ↓
                  Named calculation
                         ↓
    Each output's range, curve and target → one or more outputs

Choose Tracking measurement (SensaPoint), then the object and metric. SPS four-anchor tracking provides solved positions, Contact provides position/velocity and Shader adds axes/scale. Calculations retain the measurements' validity checks. Metric meanings

Each computed signal has a stable identifier and a readable name. Other computations, axis mappings and output bindings refer to its identifier, allowing several destinations to reuse the result. Computation retains the raw numeric result; each mapping then converts it to its own motion range.

Create a computation in the workbench

1. Open Flow and choose Add computed signal in the Computed signals area. OSC → Mappings also provides an editor for the same calculations.
2. Enter a recognizable name, choose an operation and add the inputs.
3. Choose an OSC parameter, tracking measurement, pose metric, manual, script, device feedback, recording replay, another calculation or a constant. Parameters need their actual path; tracking selects both object path and metric.
4. Select Computed signal as an axis mapping or output binding source, choose the new computation, then configure its destination and input/output ranges.
5. Save calculations and mappings. Live previews use the saved setup. Check readings and ranges before enabling current input.

Saving configuration disables input. Computations containing tracking metrics retain experimental spatial-input permission and the selected route's validity conditions. A constant-only computation needs a consuming mapping or binding and enabled input before it can drive an output.

Weighted average: choose each input's influence

For inputs A=0.2 and B=0.8, with weights 1 and 3:

result = (0.2 × 1 + 0.8 × 3) ÷ (1 + 3) = 0.65

B has 75% of the influence and A has 25%. Weights may be any finite nonnegative numbers with a positive total. Multiplying every weight by the same number preserves the result. A zero-weight input does not participate and needs no sample.

When both inputs express the same kind of intensity from 0 to 1, the result can keep a 0–1 input range. Use constants and operations to bring different ranges into a comparable meaning before combining them. A mapping's range applies to the final computed result.

Narrow layout

Supported operations

Numeric combinations accept 1–16 inputs; Difference and Ratio require exactly two. Temporal and threshold operations use one input, while Sine accepts zero or one. Only Weighted average uses weights. Computations run in dependency order and each result is evaluated once per evaluation. A configuration holds at most 64 computations with at most 16 reference levels. Saving checks duplicate identifiers, missing references and cycles. Update dependent computations and mappings before deleting a referenced definition.

Process time, thresholds and events

timeMs accepts 0–60000 ms. Hysteresis release must be at or below its active threshold. Sine frequency accepts 0–100 Hz; amplitude, offset and thresholds must be finite. A device or binding’s sending rate separately determines how frequently the result is delivered.

For example, set hysteresis to turn on at 0.7 and off at 0.5 to stabilize a touch switch. Use Duration to require 500 ms of continuous contact. Use Pulse when an event should remain high for a defined time. Edge and cooldown results are single-evaluation events that can feed a positive-trigger output; the backend delivers events in order while observing that binding's send rate.

Invalid input, source changes, backward time, reconfiguration or input stopping clears the relevant temporal history. Edge operations first establish a baseline, then react to subsequent crossings. Delay retains the historical sample time, so additional age limits should accommodate its intended delay. The delay buffer is bounded to 4096 samples.

Use Shader axes and scale

Choose Tracking measurement (SensaPoint), use a root pattern such as Sensa/Shader/42/** and select RightX/Y/Z, ForwardX/Y/Z or AvatarScale. The two axes retain direction and length; scale expresses world metres per root-local unit. This source checks all twelve fields, spatial-input activation, validity and frame freshness. Freezing also invalidates dependent calculations.

To convert local X displacement to metres, use Product with X and AvatarScale from the same source. The result uses AvatarRootMeters. For the reverse conversion, use Ratio with metre displacement divided by AvatarScale, yielding AvatarRootLocal. Axis components of the same kind can also form magnitudes or dot products. Position, axes and scale retain separate quantities.

Combine root coordinates

In Flow → Computed signals, expand Spatial calculation presets, choose an operation and select Add spatial calculation. XYZ components are grouped together: enter fixed values, choose a tracked position, or select a Shader Forward/Right direction. Expand individual components to use OSC parameters or other computed signals.

A normal points perpendicular to a plane. The default (0,0,1) describes the XY plane with +Z as positive depth. The normal is normalized, so (0,0,1) and (0,0,2) produce the same result. Two axes establish the plane's orientation: default U=(1,0,0) and V=(0,1,0) produce a +Z normal. Swapping U and V reverses signed depth while preserving lateral distance.

For example, choose origin O=(0,0,0), measured position P=(0.03,0.04,0.12) and a +Z normal:

If positions use metres, these results also use metres. The existing single-point Distance metric measures from the point's coordinate origin. Distance between points lets you choose another measured position as the reference.

These captures show the running Measured position and Plane normal input groups: P=(0.3,0.4,0.2) and N=(0,3,4). Fixed coordinates let you try a calculation; select a tracking object under XYZ source to use live measurements.

Narrow position controls

Narrow direction controls

Follow an Avatar's movement with a plane

Tracking Frame and Shader templates measure relative movement between a target and reference on your own Avatar. For interaction between Avatars, use paired three-marker pose in the receiving Socket’s local frame, selecting its SensaPose depth fraction, opening offsets and angles directly.

Add a Unity Tracking Frame, choose the bone, SPS root or marker it follows, then adjust its centre and orientation. It publishes positions for <name>_Origin, <name>_Forward and <name>_Right. Forward−Origin gives the current depth direction, which changes with measured bone rotation.

In the workbench, expand Spatial calculation presets → Follow a moving plane and select Tracking Frame · Origin / Forward. Enter the Tracking object path and Plane reference object path, such as Sensa/Contact/Target/** and Sensa/Contact/Frame_Origin/**, then choose Add following-plane drafts. The template reads the matching _Forward and creates three direction differences, depth and offset: 5 calculations in total. Select Also create point distance to add one more. Review the instances, save calculations and mappings, then connect the results to outputs. One target can then control both depth and off-centre feedback. Unity setup and coordinates

Alternatively, choose Shader · Position and Forward. The selected Shader position supplies the plane origin and Forward supplies its normal, creating depth and offset directly as two drafts.

Shader already provides Forward/Right directions for a normal or a plane defined by two axes. Using Forward as the normal makes the depth direction follow measured Forward: +Z in the default orientation, changing as it rotates. With Right as U and Forward as V, the default orientation produces a −Y normal; reverse their order for +Y.

Keep motion within the entrance area

For Contact positions in metres, first compute plane depth D and lateral offset R. To drive a traditional axis only after the target enters the plane near its centre, combine these calculations:

Map Allow motion to Gate (closed stops output) (GateEnable) with Input range set to 0–1 and the full Remap range of 0–999, keeping the direction forward. Map D separately to Stroke (L0) (Depth), choosing a range for the intended movement. Optionally add Sustained condition (Duration) after Allow motion, with threshold 0.5 and time 100 ms, then map that result to the gate to require a stable entry before opening. These distances are examples; adjust them to your measurement units and entrance size.

GateEnable stops and resumes traditional axis mappings. Independent output bindings follow their own sources and validity conditions. Multiplying depth by zero produces a valid zero target; use the gate when the axis should stop. For interaction between Avatars, paired three-point pose tracking directly evaluates Valid and Engaged against the receiving Socket's entrance and orientation.

Coordinates, units and valid inputs

Positions in a calculation share one OSC source, reference, axis directions and units. SPS four-anchor tracking and Shader use AvatarRootLocal, expressed in authored Avatar-root units; Contact direct tracking uses AvatarRootMeters. The system checks coordinate metadata carried by tracking sources. Independent Point/Handle/Pose have a separate ReferenceLocal frame for each instance. Select matching frames before combining positions, using AvatarScale from the same source for unit conversion when needed.

Shader axes describe direction without position units. Known AvatarRootLocal axes can provide directions for AvatarRootMeters positions because both use the Avatar root's axes. You assign meaning to raw OSC parameters and constants; configure them with consistent references and units. Length results retain position units, while angles use degrees.

The system also checks the physical meaning of known inputs: position groups use position coordinates, while direction groups can use axes or velocity vectors. Derived acceleration, angular velocity and other rates retain their quantity identifiers for subsequent calculations with those physical quantities.

A zero coordinate is a valid position. Normals and direction vectors need nonzero length, and two plane axes need a clear angle between them: their normalized cross-product length must exceed 0.0001. Invalid inputs, an undefined direction or a nonfinite result invalidate the calculation, retaining the source's sample-age checks.

Three-point pose angles participate as their reported numeric values; Roll, for example, uses the raw −180° to 180° angle. Crossing the ±180° boundary causes a numeric jump, so choose a mapping range within a continuous interval. Average uses the ordinary arithmetic mean.

Validity and sample age

Every required input must uniquely match one parameter or tracking object. Use source fixes the OSC source to read. When several parameters or sources match, the UI reports the waiting or invalidity reason. Complete the path and source selection, then check again.

A computation retains the oldest contributing sample time, including through references to other computations. Input validity (ms) defaults to 0, following OSC receiver settings without an additional computation-specific age limit. Ordinary OSC receive timeout defaults off, allowing parameters that publish only when their value changes to remain useful while stationary.

To require periodic updates from every input, set computation validity to 100–60000 ms. At 1000, any contributing sample older than one second invalidates the result; another input's updates do not renew it. Constant-only results remain valid at the current evaluation. Tracking inputs always retain their own Sample/Frame, geometry and age checks.

Missing or expired inputs, invalid tracking, division by zero and nonfinite results invalidate the computation and its dependents. Invalidity propagates to dependent output bindings; existing axis mappings retain their motion-runtime stop rules. Input remains enabled. New valid samples can automatically resume linkage. Disable input or use emergency stop to keep motion stopped; explicitly enable input again after saving configuration or clearing emergency stop.

When several mappings target the same role, existing fusion selects by normalized priority. For a proportional blend, first create a weighted average and map its result to that role. Features · Parameter dictionary

Ordinary SensaPoint/SensaPose mappings have priority on their destination axes; other direct mappings, computed mappings and DepthOverride retain that priority relationship. To combine or weight tracking results first, map the computed signal to the axis and replace its original single-point/pose mapping.

Manual inputs use an axis such as L0; script inputs select L0, Progress (0–1) or Time (seconds). Device feedback uses identifiers provided by its output. For recording replay, funscript uses recording-output-id/value for 0–1 positions, while JSON Lines/CSV use recording-output-id/signal-id for raw readings. Combined mode lets these sources participate together. OSC inputs still share one selected OSC source, and spatial inputs retain compatible coordinate-frame checks. Source and destination setup

Configuration example

The workbench handles ordinary setup. For manual editing, replace TouchA and TouchB with actual parameter names and retain other settings. Names allow up to 80 characters. Identifiers start with an English letter and may contain letters, digits, underscores and hyphens, up to 48 characters; the workbench generates these automatically.

{
  "computedSignals": [
    {
      "id": "touch_mix",
      "name": "Two-zone touch",
      "operation": "WeightedAverage",
      "maxAgeMs": 0,
      "inputs": [
        { "sourceMode": "Direct", "oscPath": "TouchA", "weight": 1 },
        { "sourceMode": "Direct", "oscPath": "TouchB", "weight": 3 }
      ]
    }
  ],
  "signals": [
    {
      "sourceMode": "Computed",
      "oscPath": "touch_mix",
      "role": "V0",
      "vrchatMin": 0,
      "vrchatMax": 1,
      "curve": "Linear"
    }
  ]
}

Computed signals live in Sensa's configuration while the Avatar continues publishing its existing OSC parameters. Their identifiers are internal Sensa references. Custom presets store OSC parameter and tracking mappings. Flow exports axis mappings, axis profiles, computations and outputs as a complete plan, with review before importing. Presets · Complete plans