Changelog: v2.16
v2.16.0 (2026-11-15)
RaiSim
- Runtime joints.
World::addRuntimeJoint()connects two rigid objects or articulated links, also of different robots, with aFixed,Ball,HingeorSliderjoint between simulation steps, andWorld::removeRuntimeJoint()removes it again. The joints keep the objects separate; their impulses are solved together with contacts, tendons and joint limits. The world XML (<runtime_joint>) saves them with their enabled and broken state, and checkpoints keep the state of the joints that exist; adding or removing a joint makes earlier checkpoints unrestorable. See Runtime joints. The newruntime_joint_benchmarktimes them. World::discardPendingStep()cancels a step prepared byintegrate1()orintegrateNoContactDetection()without solving, integrating or advancing the world time. It clears the prepared contacts and constraint rows and allows adding and removing objects, tendons and wires again; preparation already done (waking objects, advancing projectiles) is not rolled back.- Articulated systems use less memory and reuse their dynamics scratch storage between steps.
MatDyncopies no longer allocate for empty matrices. - Windows: the native FEM mesher build compiles in RaiSim's message logger, and its external projects use explicit build directories.
- The FEM mesher reads and tessellates more STEP files; six complex parts (a DC motor, a hollow section, a pneumatic cylinder, a servo horn, a socket screw and a sprocket) are checked against independent Open CASCADE measurements, and a knee mount is a browser regression case.
- The
raisim_engine2world editor (theraisim_engine2/tree and theRAISIM_ENGINE2CMake option) was removed from this repository.
raisimPy
raisimpy.RuntimeJointandWorld.addRuntimeJoint(),getRuntimeJoint(),getRuntimeJoints()andremoveRuntimeJoint(); theruntimeJoints.pyexample.World.discardPendingStep().
Examples and documentation
- The C++
runtime_jointsexample. - The examples build with MSVC's
/bigobj. - The Newton benchmark pages compare ten-step control intervals and random actuation, and normalize performance by hardware price.