Mouse interaction with controls

Operate all nine physical control types without changing their limits, springs, resistance, detents or motors. Forces/torques run before fixed physics steps; dynamic mounts receive reaction.

Example#

interaction = jolt_control_interaction();
interaction.set_camera(o_control_bbmod_camera);
interaction.set_carry(carry);
interaction.set_distance(3);
interaction.set_sensitivity(0.35);
interaction.set_max_force(200);
interaction.set_max_torque(20);
// End Step:
if (!interaction.update_controls()) carry.update_controls();

Usage and limits#

Camera Step must test interaction.controls_use_mouse(id) before consuming mouse-look. Carry has priority when holding an item. Initial ray hit acquires capture; moving the ray away does not release. Mouse-up, focus loss, distance, lock, destruction or stale input releases; acquiring again requires a new click.

Button defaults to press/hold; set_button_mode("drag") uses its projected axis. Lever, Pedal, Slider and Pull Handle use visible movement direction. Knob and Hand Wheel retain their initial turning direction; Crank follows the changing handle tangent and needs circular movement. Joystick projects two axes within its physical cone. Approach sliders/handles obliquely if looking along their stroke.

For custom input use jolt_control_interaction_frame(origin,forward,up), begin_from_hit(hit,frame), then update_drag(frame,dx,dy,held,dt_seconds) with a fresh complete raycast result. Own the filtering and do not also run the automatic adapter. Destroy interaction in Clean Up.

API reference#

Public function and method signatures. Call methods on the returned instance; parameters with defaults are optional.

Related guides#

• Migrating existing code›
• Carry: moving objects›
• Carrying Soft Bodies›

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.