Myogestic.Remote.SetPresentationRequest
VHI_godot¶
Myogestic.Remote¶
SetPresentationRequest Class¶
How the target blends between the values it is given.
This is the third and last of three distinct layers, and confusing them is the mistake it exists to prevent:
1. Continuous smoothing, on the MyoGestic side, inside ControlBus and before any target sees a frame. Authoritative: it decides what value is *commanded*. 2. Discrete debounce and hysteresis, also MyoGestic-side, declared on the DOF. A classifier's state must be gated for stability before it becomes a transition. A discrete control is never numerically low-pass filtered as though it were an axis — that would interpolate through states nobody selected. 3. This: purely visual interpolation in the target, so the rig does not snap jarringly between poses.
Layer 3 must never be relied on as protection against classifier chatter. It changes only how a commanded value *looks* on its way to being reached; it does not change the value, and it cannot make an unstable prediction stable. A build with blending on and no debounce still jumps between states — it just does so smoothly.
public sealed class SetPresentationRequest : Google.Protobuf.IMessage<Myogestic.Remote.SetPresentationRequest>, Google.Protobuf.IMessage, System.IEquatable<Myogestic.Remote.SetPresentationRequest>, Google.Protobuf.IDeepCloneable<Myogestic.Remote.SetPresentationRequest>, Google.Protobuf.IBufferMessage
Inheritance System.Object → SetPresentationRequest
Implements Google.Protobuf.IMessage<SetPresentationRequest>, Google.Protobuf.IMessage, System.IEquatable<SetPresentationRequest>, Google.Protobuf.IDeepCloneable<SetPresentationRequest>, Google.Protobuf.IBufferMessage
Properties¶
SetPresentationRequest.Blend Property¶
Interpolate toward each newly commanded pose instead of snapping to it.
Property Value¶
SetPresentationRequest.BlendSpeed Property¶
Interpolation speed when blend is true; higher is snappier. Non-positive leaves the target's current speed alone.