Major Improvements
Impact Trigger (recommended, enabled by default)
- Added an impact-based trigger system that gates forward response by actual physical contact
- Receiver movement is now driven by collision events, not estimated timing
- Produces a causal response chain:
contact → impulse → inertia → settle
- Impact Trigger is enabled by default and is the recommended mode of operation
Legacy velocity-based response remains available
- The original velocity-driven system is still included
- Can be disabled or re-enabled via toggle for compatibility or alternative workflows
Cleanup / Simplification
The following
legacy timing and rate parameters were removed, as they interfered with both response modes and caused conflicting dynamics:
- Forward Delay
- Backfall Delay
- Engage Delay
- Thrust Build Rate
- Back Build Rate
- Return Rate
These parameters introduced:
- phase lag
- double smoothing
- jitter and snap artifacts
Their removal allows the remaining physics systems to operate
without internal conflict, resulting in smoother behavior even with default settings.
Core Physics (unchanged)
The core physical response pipeline remains intact:
- Velocity-based response system (legacy mode)
- PD controller (Position Gain / Damping Gain)
- Axis filtering and smoothing
- Speed and direction gates
- Acceleration clamping
- Max Forward / Back Offset
- Resting Offset
With redundant timing layers removed, these systems now produce
more stable and predictable results.
Preset System Improvements
Impact Trigger state and geometry are now stored in Custom Presets
- Custom presets now save and restore:
- Use Impact Trigger (on/off)
- Trigger Offset Y
- Trigger Offset Z
- Trigger Radius
- Trigger Height
This makes presets
fully reproducible, restoring both:
- the interaction model (impact vs velocity)
- and the exact trigger placement
Built-in presets remain neutral
- Built-in presets (Soft / Medium / Strong) do not store impact-trigger state or geometry
- Custom presets are intended for pose- or scene-specific tuning
Design Notes
- TRD now supports two response modes:
- Impact-triggered response (default, recommended)
- Velocity-based response (legacy, optional)
- Both modes share the same physical response pipeline (PD + damping + clamping)