Construction settings

Override Blender defaults before construction, then use live JoltControl setters.

JoltPhysics Asset Editor 0.31.1 · verified against project sources on 27 September 2026.

Syntax#

jolt_asset_control_settings();

Returns JoltAssetControlSettings, a construction builder with no physics allocation. Valid setters return the builder; invalid input returns false and preserves the previous setting. Inspect jolt_get_error(). Some cross-field and type checks are deferred to jolt_asset_create_control; a successful setter does not guarantee that the complete combination is valid.

All construction setters#

Override precedence#

Blender defaults → construction overrides → live runtime setters. Overrides never mutate the loaded asset. Plain options use position:[x,y,z] and rotation:[x,y,z,w], unlike body creation's position struct. Identity, Key, UUID and type cannot be overridden. Unknown or wrong-type fields fail before successful construction.

Partial drive, circular size and crank arm_size merge only supplied fields. Other fields replace their original value. Detent shorthand is expanded by the existing runtime validators. Geometry and initial pose apply at creation; changing a builder later does not rebuild an existing control.

Example#

var settings = jolt_asset_control_settings();
settings.set_size(0.10, 0.10, 0.60);
settings.set_min_angle(-30);
settings.set_max_angle(45);
settings.set_initial_angle(15);
settings.set_max_torque(12);
var lever = jolt_asset_create_control(asset, "lift_lever", machine_body, settings);
if (is_undefined(lever)) show_debug_message(jolt_get_error_message());
else lever.set_resistance(0.2);

A plain struct is equivalent for selected overrides; it can change a return motor without repeating the rest of the exported configuration.

var lever = jolt_asset_create_control(asset, "lift_lever", machine_body, {
    initial_angle:15, auto_return:true, drive:{max_torque:12}
});

• Control asset API and JSON v3›
• Physical Controls from Blender›

Verified operation contracts#

These contracts distinguish units, return values, errors and lifetime according to the current implementation. Check results: false, 0 and undefined can mean different things for different methods.