Slider
Linear travel along local −Z. Travel is the total positive stroke.
JoltPhysics Asset Editor 0.31.1 · verified against project sources on 27 September 2026.
Blender setup#
Available since addon 0.18.0; supported by 0.31.1. Add this type under Physical Controls, assign its Key and keep scale 1.
| Field / operation | Meaning and validation |
|---|---|
| Geometry and pivot | Full Handle Size XYZ; mounting point is the handle centre at value 0. |
| Motion | Linear travel along local −Z. Travel is the total positive stroke. |
| Initial state and reading | Initial Value is the actual starting position in 0..1. get_value() reads normalized travel. |
| Limits and capabilities | No press thresholds or is_pressed(). Use a scalar return target and detents in 0..1. Drive and resistance use N. |
| JSON v3 | size:[x,y,z], travel, initial_value |
Create from the asset#
The following example assumes loaded asset data, a live machine_body and an authored slider named control_main. Geometry overrides are optional; omit settings to use Blender defaults.
var settings = jolt_asset_control_settings();
settings.set_size(0.20, 0.20, 0.10);
settings.set_travel(0.50);
settings.set_initial_value(0.30);
settings.set_max_force(15);
control = jolt_asset_create_control(asset, "control_main", machine_body, settings);
if (is_undefined(control)) show_debug_message(jolt_get_error_message());
// Step, after the physics update:
if (!is_undefined(control) && control.is_valid()) {
var value = control.get_value();
}Live behavior#
Live set_auto_return, set_target, set_resistance, set_detents and set_locked adjust supported behavior. Auto Return takes priority over detents. Output mapping and inversion are runtime choices. These operations do not rebuild geometry or replace the original construction pose.
Simulation, rendering and lifetime#
Use the existing jolt_update() loop, then read the control's physical state. Drive your visual model with control.get_transform() or the existing control rendering API. The asset helper creates the same JoltControl bodies and constraints as the direct factory; it does not render your model or assign gameplay actions. Each creation is independent.
control.destroy() removes the mechanism and preserves its parent. Parent destruction and jolt_stop() clean up attached controls. Use managed lifecycle calls. No additional native bridge change is required by the Blender controls integration; use the matching current GML loader and jolt_asset_controls scripts.