Skip to content

MuJoCo Release Notes

DeepMind Technologies Limited · A physics engine for fast, accurate simulation and model-based optimization of contact-rich systems.

CaskEngineering and CAD 18.3K
Install command
brew install --cask mujoco
30-day installs
51
#1245 in App
1-year installs
330
Last 365 days
Latest version
4.0.1
Download size
58MB
dmg
Release cadence
Every 2 weeks
3 releases in 30 days
  1. 4.0.1

    LatestPatch

    OpenNavo editorial Added to Homebrew

    MuJoCo 4.0.1 fixes a wrong sparse solver result from 4.0.0 and skips a plugin library that fails to load.

    MuJoCo 4.0.1, released on 2026-11-11, is a physics engine for people simulating robots and mechanisms. This build fixes a wrong sparse solver result from 4.0.0 and stops one bad plugin library from aborting startup. Official notes: https://github.com/google-deepmind/mujoco/releases/tag/4.0.1

    • Adds a function to read one entry of a string vector by index.
    • Ships the Studio web viewer so it can run on Windows.
    • Fixes the sparse Cholesky factorization from 4.0.0, which could give the Newton solver a wrong factor and make it diverge (issue 3767).
    • Skips a plugin library that fails to load instead of aborting simulate at startup.
    • Fixes single-shot multicontact for cylinder edge collisions (issues 3748 and 3752).
  2. 4.0.0

    OpenNavo editorial Added to Homebrew

    Adds speculative contacts, elasto-plasticity, and splits the Python packages.

    MuJoCo 4.0.0 was released on 2026-11-06. This update adds speculative contacts, elasto-plasticity, and splits the Python packages.

    • The speculative flag adds speculative contacts so fast-moving convex geoms do not tunnel through thin obstacles in one timestep.
    • Joint and tendon springs can use ideal elasto-plasticity. Plastic deformation is stored in mjData.plastic (mjSTATE_PLASTIC), with springyield on joints and on spatial and fixed tendons.
    • 2D and 3D flexes can use continuum elasto-plasticity. 2D shells have separate stretching and bending yield strains, with volumetric-deviatoric (von Mises J2) stretching and 2D shell bending return mapping.
    • The Python distribution splits into mujoco-core (bindings and the C library, depending only on numpy), mujoco-studio (Studio and Filament renderer bindings), and mujoco (installs both).
    • Upgrading a pre-split mujoco install with pip needs an uninstall first, or pip install --force-reinstall --no-deps mujoco mujoco-core mujoco-studio, so pip does not remove files moved into mujoco-core.
  3. 3.17.0

    OpenNavo editorial Added to Homebrew

    Adds threaded batch simulation, 1D flex bending and referenced textures; includes breaking API/ABI and model-behavior changes.

    Adds the C batch API and Python mujoco.batch for many simulations of one model on a dedicated thread pool. Results match a plain loop bit for bit at any thread count; memory scales with worker threads. Adds referenced textures loaded on demand, asset deduplication, and fixes in flex elasticity, Filament, named access and error cleanup. Python Bazel builds initially cover core bindings, not rendering or the viewer.

    1D flexes with positive young now bend, using a straight reference rod and the discrete integrator. Existing models that set young can change behavior; degenerate sections, zero-length edges or non-straight reference rods fail compilation. Interpolated flexes gain self-collision; reduced default flex arena memory can trigger Newton-to-CG fallback with a warning.

    Migration: mj_setConst no longer resolves dampratio damping, automatic tendon spring lengths or model statistics; edit compiled fields directly. Solver termination scaling changes; meaninertia is deprecated. mjNEQDATA grows from 11 to 12, breaking ABI. For body welds without authored relpose, zero eq_data[11] before mj_setConst to set their relative pose directly. mjs_fuseStatic/mjs_discardVisual now return counts or -1: test errors with <0, not !=0. Replace mjs_addTexture(spec) with mjs_addTexture(spec, NULL).

    Selected release summary; see the official notes for the full API and asset-path migration details.

    https://github.com/google-deepmind/mujoco/releases/tag/3.17.0

  4. 3.16.0

    Expand

    OpenNavo editorial Added to Homebrew

    Compile-time scaling, model-saving improvements and API migrations.

    MuJoCo 3.16.0 — Release notes

    Highlights: frames gain compile-time scale, scaling and massscale; default similar preserves dynamics under proportionally scaled gravity, while geometry scales spatial dimensions and inertia only. savecompiled and savecanonical default to true and can be disabled to preserve authoring. Adds Bazel builds, contact relative velocities, procedural meshes, mesh assets for flexcomp and Python struct assignment.

    Migration: decoder callbacks gain char* error, int error_sz; resource-provider functions are renamed. mj_copyBack and mj_saveLastXML reject inexpressible changes, and structurally edited specs must be recompiled before saving compiled values. API-added assets need explicit names. Write replicate keyframes for the complete model. Discarding massive visual geoms with inertiafromgeom="true" errors: use auto or zero mass. Actuator gains belong in defaults of the same shortcut or general. settotalmass is deprecated: scale masses/densities or use mj_setTotalmass followed by mj_setConst.

    Filament renames mjrf functions, types and flags; enum flags now take strings instead of integers. VSM soft-shadow parameters are removed: use filament.shadows.type=pcss. filament.msaa.enabled is removed: use offsamples or mjrf_setSceneMsaa. The public debugging-editor API is removed.

    Fixes flex stiffness, cloth contacts, capsule collisions, tendon wrapping and many model saving/editing issues. Stiffness corrections can change existing flex-model behavior. This categorized summary is not the full changelog; consult the official release for complete rename tables and migration details.

    Official sources

  5. 3.15.0

    Expand

    OpenNavo editorial Added to Homebrew

    Revises actuator damping calculations, adds engine capabilities, and updates `.mjz` archives and model serialization. Includes a breaking API change and constraints on experimental elasticity.

    Engine
    Breaking change to the reflected-inertia calculation for dampratioExperimental elasticity for non-interpolated 3D flexesFlex forces now account for articulated vertex attachmentsAdds capsule multicontact and an insidesite sensor attributeRemoves a deprecated flex collision option and related structuresFlex bending factors retain cross-coordinate couplings
    General
    Windows-written .mjz archives now use forward slashesAssets resolve in rewritten archives and absolute, .., or URI pathsModel serialization supports buffers larger than 2 GiB

    MuJoCo 3.15.0 changes how dampratio calculates reflected inertia at mjModel.qpos0: it now uses operational-space inertia, averaged across force outputs for multi-output actuators. Damping may be lower for actuators on multi-link kinematic chains; actuators driving tendons or sites spanning multiple joints are damped more accurately. This is a breaking API change. The deprecated internal flex collision option and associated evpair structures were removed.

    Experimental simplified Stable Neo-Hookean elasticity is available for non-interpolated 3D flexes through mjsFlex.elastic3d = 1. It requires the discrete integrator and is not available in MJCF; the default remains StVK. Flex bending and stretching now account for articulated vertex attachments. The discrete integrator supports these attachments with the CG solver; elastic flexes attached to mocap bodies produce a compiler error. Other engine changes include capsule multicontact and the enclosed attribute for insidesite sensors, which reports signed clearance or protrusion. Flex bending factors also retain cross-coordinate couplings.

    Windows-written .mjz archives now use forward slashes. Assets resolve correctly in rewritten archives and when directory paths are absolute, contain .., or use a URI scheme. mj_saveModel and mj_loadModelBuffer now accept mjtSize for buffer_sz, supporting models larger than 2 GiB.

    Source: https://github.com/google-deepmind/mujoco/releases/tag/3.15.0

  6. 3.14.0

    Expand

    OpenNavo editorial Added to Homebrew

    Adds experimental penetration-free flex contact and archive resource providers, preserves MJCF frames, changes control-reading and spec-signature APIs, and fixes several engine and parsing issues.

    General
    Adds experimental IPC contact for supported dim-2 flexes.Adds archive resource providers for containers such as .mjz and .zip.Saving MJCF now preserves frame transforms and relative contents.
    Engine
    mj_readCtrl now supports multi-input actuators; this changes its API.Edited, uncompiled mjsSpec signatures are now 0.Inertia warnings now cover additional integrator factorizations.
    Fixes
    Procedural spec editing is incremental; 8,000 geoms build roughly 10x faster.Fixes weld and tendon forces reported by force and torque sensors.Fixes memory leakage, GMSH header reads, and sparse Newton pivot handling.

    MuJoCo 3.14.0 adds experimental IPC contact for dim-2 flexes. It uses frictionless contact, and its retained contact multipliers are not captured by mj_getState/mj_setState, so exact replay is unsupported. Archive resource providers can mount containers such as .mjz and .zip without a pre-allocated VFS. Saving MJCF now retains frame transforms and frame-relative contents; changing a frame's pos or quat in an mjSpec also takes effect on recompilation.

    Breaking API changes: mj_readCtrl now follows mj_readSensor semantics and returns either a pointer or NULL while supporting multi-input actuators; control history sizing changes accordingly. After structural edits, mjsElement.signature is 0 until a successful mj_compile. Code relying on another uncompiled signature must compile first. Duplicate-name failures in mjs_setName now preserve the prior name.

    Other changes include broader mjWARN_INERTIA reporting, safer sparse Newton pivot handling, incremental procedural editing, corrected weld and spatial-tendon force reporting, and fixes for actuator force-limit defaults, finite-difference calls with sleeping enabled, a deletion memory leak, and truncated GMSH headers.

    Source: https://github.com/google-deepmind/mujoco/releases/tag/3.14.0

  7. 3.13.0

    Expand

    OpenNavo editorial Added to Homebrew

    Adds a discrete integrator, site-mesh support, and Python 3.15 support. Includes a flex integration migration requirement and changes the PBR metallic fallback color.

    Engine
    Adds a discrete integrator for implicit stiffness and damping.Adds cylinder multicontact and restores inertia-pivot clamping.Changes Newton cone refactorization for some sliding-contact scenes.
    General
    Site geoms can use meshes; adds the mj_insideSite function.Adds Python 3.15 support, including GIL and free-threading.
    Other
    Flex models using the former implicit/CG behavior must migrate.PBR metallic fallback without a texture changes from black to white.

    MuJoCo 3.13.0 adds a discrete integrator that combines constraint solving with the implicit velocity update. It incorporates joint, tendon, and actuator stiffness and damping into the solver metric, and evaluates constraint spring-dampers at the end of the step. The release notes describe its semantics and current limitations.

    The flex effective-metric special case previously available with implicit or implicitfast and the CG solver has been removed. Models relying on it must use integrator="discrete" with a primal solver, CG or Newton. Flex elasticity or passive flex contact with the former settings now raises a runtime error with a migration note. Other engine changes include single-shot multicontact for cylinder geoms, restored clamping of non-positive pivots in sparse inertia factorization with the associated mjWARN_INERTIA warning, and a Newton elliptic-cone refactorization approach that can speed scenes with many sliding contacts. The Plane-Mesh collider was rewritten to fix bugs and improve performance.

    Site geometries can now reference meshes, supporting visualization, the insidesite sensor, and mj_insideSite. The release also adds Python 3.15 support, CDATA input for MJCF custom text, a cutoff attribute for tactile sensors, a headless render.cc sample, and house-of-cards and arch models. The root file in .mjz archives is now named model.xml. For PBR materials without a metallic texture, the metallic fallback is now white rather than black.

    Source: MuJoCo 3.13.0 release

  8. 3.12.0

    Expand

    GitHub Release Added to Homebrew

    Version 3.12.0 (August 20, 2026)

    General

    1. 3f8db4c1 The MJCF grammar is now defined in a single source of truth schema file, src/xml/mjcf.schema. The parser's grammar table, presence constraints, keyword maps, typed attribute bindings and save policies are generated from it and gated by tests, as are the schema's enum keywords and declared defaults against the C headers and default-constructors.

    [!WARNING] Breaking API changes 2. 6fe04aa8 Removed the custom binary texture format (image/vnd.mujoco.texture) and the automatic fallback to custom textures when loading files with unrecognized extensions. Textures can now only be loaded from PNG (image/png) and KTX (image/ktx) files.

    Actuation

    1. 279df98c Added the pid actuator: a PID controller with real position and velocity setpoint inputs, optional integral action (ki, integrating the position error with imax anti-windup), setpoint rate limiting (slewmax), and an optional feedforward input. This subsumes the functionality of the mujoco.pid plugin with proper activation state: correct under all integrators and visible to keyframes and sensors. With a zero velocity setpoint it is identical to position. The input signature is any subset of [pos, vel, ff], selected by input; absent setpoint inputs are fixed at zero, so the control vector contains no inert entries.
    2. 2f1843f4 The dcmotor on-board controller is redesigned: the input attribute selects any subset of [pos, vel, ff, voltage], where pos and vel are setpoints for the controller, ff is a torque feedforward, and voltage is the raw terminal voltage (the default, a plain voltage-commanded motor). Controller gains are in torque space, as for pid, and the drive voltage compensates back-EMF as in a current-controlled driver: commanded torque is delivered exactly until a limit is reached. The keyword input="none" selects the empty signature: the actuator has no control inputs and is purely passive, so friction, cogging and back-EMF braking can be used as passive joint forces.

    [!WARNING] Breaking API changes 5. 2f1843f4 The mode-flag semantics of dcmotor/input ("voltage", "position", "velocity", selecting the interpretation of a single control) are replaced by input signatures, and the controller gains changed from voltage space to torque space. The old velocity mode's integral term (integrated-velocity tracking) is retired without replacement; the integrator always accumulates position error.

    Migration: Voltage-commanded motors (the default) are unchanged. Replace input="position" with input="pos" and input="velocity" with input="vel", and multiply the controller gains by $K/R$ (torque per volt). The motor's back-EMF damping, previously felt in addition to the controller's damping, is now compensated: to preserve behavior when the velocity setpoint is zero, add $K^2/R$ to the converted kd.

    Engine

    1. 83e621d7 Optimized large-mesh convex collision detection with up to 2x speedup in certain cases.
    2. 55d13aec Replaced the per-step sparse Cholesky factorization of the flex block of the implicit effective metric M + K with its prefactored per-vertex 3x3 diagonal blocks. The blocks precondition the CG constraint solver and drive an iterative solve for qacc_smooth, which now converges on tolerance rather than a fixed threshold. Flexes with elastic2d stretch stiffness step roughly twice as fast; bending-only flexes keep the exact constant factor and are unchanged.
    3. 86e98601 Rewrote cleaner box-box SAT collider.

    [!WARNING] Breaking API changes 9. 2a3554c8 Contacts of a flex with passive collisions are now integrated implicitly: their stiffness is carried by the effective metric rather than applied as an explicit spring, and can be far stiffer than the timestep would otherwise permit. Models using passive collisions should be re-checked: the feature now requires implicit or implicitfast with the CG solver, pyramidal cones and sleep disabled; passive handling covers flex-flex, self-, and static-geometry contact, while contact with a moving body stays on the constraint solver; and the stiffness is now a mass-scaled natural frequency rather than a fixed 1e4. 10. 55d13aec Removed mjData.efm_L_rownnz, mjData.efm_L_rowadr and mjData.efm_L_colind. They described the sparsity of the effective-metric Cholesky factor, which no longer exists; mjData.efm_L now holds dense 3x3 blocks, 9 numbers per covered vertex. mjData.efm_active no longer takes the value 2: nothing selects a solve path on preconditioner exactness, so it is now a plain 0/1 flag. 11. 1362a8bd Changed the default value of bvactive from "true" to "false". This avoids unnecessarily clearing bounding volume hierarchy visualization flags at every simulation step, which can be a bottleneck for models with large meshes. 12. ed13bf56 Mocap bodies and their dof-less descendants are now the root of their own weld group: mjModel.body_weldid of a mocap body equals its own id rather than 0. Consequences: dragging a mocap body into sleeping objects now wakes them; children of mocap bodies receive standard parent-child collision filtering; mocap bodies no longer count as static geometry for ray casting, and contact-matching sensors aggregate their contacts under the mocap body rather than the world; and geom pairs where neither body can move no longer generate contacts.

    Models

    1. 2a3554c8 Added drape example model: three cloths draped over a sphere, demonstrating passive collisions. It replaces the sphere_passive model, which has been removed.
    2. 55d13aec Added bag example model: a cloth bag, held open by pinning the ring of vertices around its mouth, catching the standard humanoid dropped in from above. Unlike the poncho models, which are bending-only, this model exercises the 2D stretch elasticity of a flex.

    Rendering

    [!WARNING] Breaking API changes

    1. cc7fb98c Added explicit texture coordinates to built-in geometries (Plane, Box, Sphere, Ellipsoid, Capsule, Cylinder) in both the Classic renderer and Filament. 2D textures applied to primitive shapes will look different as textures are mapped using canonical UV parameterizations rather than projecting onto the $x,y$ plane.

      For finite planes, textures are now anchored to the bottom-left corner instead of the center. This will cause the most common visual breakage, as common procedural checker textures will be phase shifted. Infinite planes continue to be anchored at the origin with no visual changes.

    2. f9a00bd5 Added light/softness: edge softness for spotlights under physically-based lighting models, given as the fraction of the cone over which intensity falls to zero. The default of 0.2 is a semi-soft cone which delivers the full intensity everywhere inside it, so that illuminance follows $E = I/d^2$ independent of the cutoff angle. Previously the filament renderer treated the entire cone as penumbra, dimming spotlights well below their rated intensity, increasingly so for narrow cutoffs.

      Migration: Set softness to 1 to reproduce the previous appearance of existing models.

    MJX

    [!WARNING] Breaking API changes 17. 5e3464f4 mjx.render and mjx.render_with_segmentation now return the updated mjx.Data as the last element in their return tuple (i.e. (rgb, depth, d) and (rgb, depth, seg, d)). This ensures JAX/XLA strictly enforces causal scheduling between sequential refit_bvh and render calls.

    **Migration:** Update unpacking calls from `pixels, depth = mjx.render(mx, d, rc)` to `pixels, depth, d = mjx.render(mx, d, rc)`.
    

    Bug fixes

    1. 95539261 Fixed a bug where models with pinned interpolated flex nodes (e.g. a flexcomp with dof "trilinear" and pinned vertices) could not be reloaded after saving: node coordinates within their body frames were not saved, degenerating the interpolation grid. They are now saved in the new flex nodecoord attribute.
    2. 8655446f Fixed a bug in the box-box collider where near-degenerate face clipping could generate contacts with spuriously large penetration depth between nearly touching thin boxes with positive margin, causing resting stacks to explode.
    3. fb07a9ca Fixed a bug in the box-box collider where penetrations deeper than a box's smallest half-size could produce no contacts, letting boxes tunnel through thin boxes. Fixes #1800.
    4. 54979947 Fixed the flex stretch stiffness operator, which was the Gauss-Newton Hessian of the stretch force rather than its Jacobian: the geometric (stress-proportional) term was missing. Only the tensile part of that term is added, since it is positive semi-definite exactly when the edge is in tension, and its consumers require an SPD operator; the stretch force itself is unchanged. This affects the implicit integrators and the implicit effective metric, so flexes using elastic2d="stretch" integrate slightly differently. Bending-only flexes are unaffected.

    OpenUSD

    1. 39e44588 Upgraded Newton USD schemas support to version 0.4.0:
      • NewtonJointAPI (newton:armature, newton:damping, newton:friction) deprecates the MjcJointAPI equivalent mjc:armature, mjc:damping, and mjc:frictionloss attributes.
      • NewtonMassAPI (newton:massModel, newton:inertia) deprecates the MjcCollisionAPI equivalent mjc:shellinertia and MjcMeshCollisionAPI mjc:inertia attributes. This completes the deprecation of all MjcMeshCollisionAPI attributes, slating it for removal in a future release.
      • Added support for NewtonSiteAPI to declare sites, MjcSiteAPI auto applies this schema, but remains as an extension for the mjc:group attribute.
      • Added support for NewtonMaterialAPI (newton:contactAdhesion, newton:torsionalFriction, newton:rollingFriction). This deprecates MjcMaterialAPI which will be removed in a future release.
      • Added support for NewtonMimicAPI (newton:mimicJoint, newton:mimicCoef0, newton:mimicCoef1) as a base for MjcEqualityJointAPI, this deprecates the mjc:coef0 and mjc:coef1 attributes and the mjc:target relationship.
      • Added support for NewtonArticulationRootAPI (newton:jointsAddMobility).

    [!CAUTION] Breaking ABI changes 23. 279df98c mjsActuator gained velrange and ffrange fields, changing its size and layout. The mjtGain and mjtDyn enums gained pid members, shifting the values of mjGAIN_USER and mjDYN_USER. 24. 596b6f43 mjResource gained an args field (changing its size and layout), used to hold optional extra encoding and decoding arguments formatted as URI query parameters (separated by &).

  9. 3.11.0

    Expand

    GitHub Release Added to Homebrew

    Version 3.11.0 (July 27, 2026)

    Engine

    1. 4787c809 Added geom/surfacevel: the velocity of a geom's surface as seen by contacts, given as a velocity field with a constant component and a rotational component about the geom frame origin. This allows conveyor belts, treadmills and turntables to be modeled with static geoms and no degrees of freedom: friction drives touching bodies along the motion of the surface, with the field projected onto each contact's tangent plane. Surface velocities compose correctly with each other and with body motion. Note that the contact rows of mjData.efc_vel, and the constraint-state sensors that read them, report the velocity relative to the moving surface rather than to the geom, since that is the quantity the constraint acts on; for geoms without surfacevel the two are identical. Contact-point visualization draws an arrow along the surface velocity at contacts with moving surfaces.

      [Image: Watch video](https://youtu.be/PdSdrqhSiZA)

    2. a264d0bc Added geom/adhesion and pair/adhesion: an adhesive force associated with a contact, useful for modeling sticky materials. Contacts can pull with up to the given force before breaking, and the friction budget becomes $\mu(f_N + \text{adhesion})$. Combined with gap, adhesive contacts apply "adhesion at a distance", useful for modeling magnets. Resting penetration is unaffected by adhesion. mj_contactForce reports the net interface force, whose normal component can now be negative.

      [Image: Watch video](https://youtu.be/GioWwB36XHI)

    3. f0fa3d82 Replaced midpoint integration of free bodies with gyroscopic derivatives in the implicitfast integrator: the bias-force derivative of every standalone free body is applied via a local unsymmetric solve of its decoupled block, making implicitfast identical to implicit for such bodies. Unlike midpoint integration, which required vacuum and no constraints, this applies in all environments (contacts, fluid, constraints), and is compatible with discrete-time inverse dynamics. Spinning free bodies no longer gain energy, but tumbling motion is now mildly damped; models requiring long-horizon energy conservation of tumbling bodies in vacuum should use RK4. The invdiscrete flag no longer has any effect on forward dynamics.

    4. 5618666a Added body/simple attribute ("false"/"auto") to disable the simple body mass matrix optimization. This is useful for domain randomization, where model parameters may change post-compilation.

    5. 14c0b0c9 mj_setConst now recomputes the mjModel.{body,geom,site}_sameframe flags, to account for changes in body/geom/site frames after compilation.

    6. 2444defc Added support for multiccd with arbitrarily large meshes.

    7. a04b0c5b Added flg_gravcomp and flg_surfacevel boolean flags to mjModel. These flags replace the fast-path checks as originally guarded by ngravcomp. Since the engine uses these integers as flags (zero vs. non-zero), the new flags are honest boolean properties, writeable from the Python bindings at runtime. The field ngravcomp is deprecated and will be removed in a future release.

    8. a1f38c8e Replaced quadratic scratch in DFS flood-fill island discovery with a linear-memory Union-Find (disjoint set). Contribution by @teerthsharma.

    [!WARNING] Breaking API changes

    1. ff629889 Changed the default value of sleep_tolerance from 1e-4 to 1e-3 (1mm/sec in SI units).
    2. 315bcfbf Removed the legacy sparse ancestor-walk inertia matrix mjData.qM. The joint-space inertia matrix is now stored exclusively in the compressed sparse row (CSR) format mjData.M.
    3. 7e9ac58f Switched mjd_inverseFD to use the CSR-format mjData.M representation instead of the legacy mjData.qM for the mass matrix derivative. This changes the shape of the DmDq parameter from (nv x nM) to (nv x nC).
    4. 1ea2d884 mju_round now breaks ties away from zero rather than towards $+\infty$. This only affects negative half-integers, e.g. mju_round(-2.5) now returns -3 rather than -2.
    5. fa36015b Removed unneeded mjvScene argument from mjv_moveCamera.
    6. ba9a6503 Split up mjrfMeshData into mjrfMeshData and mjrfMeshConfig to allow reuploading of mesh data without having to recreate the mesh object. Introduces mjrf_defaultMeshConfig and mjrf_setMeshData functions.
    7. ba9a6503 Removed bytes field from mjrVertexAttribute.

    [!CAUTION] Breaking ABI changes

    1. 072e963f mjModel gained the actuator_ctrlspec field (input signature of each actuator), and mjsActuator gained ctrlspec, changing their size and layout. The mjtGain and mjtBias enums gained so3 members, shifting the values of mjGAIN_USER and mjBIAS_USER.
    2. d43c3ed4 Added texid, texuniform and texrepeat fields to mjvGeom.
    3. a264d0bc The mjContact struct gained an adhesion member, changing its size and layout.

    [!NOTE] Bug fixes

    1. dddb2767 Fixed a bug where body_margin excluded gap, causing the mid-phase collision filter to incorrectly prune in-gap contacts on multi-geom bodies.

    Actuation

    1. d507e921 Refactored actuator infrastructure in preparation for MIMO (multi-input multi-output) actuator support. Each actuator now has ctrlnum (number of controls) and outnum (number of force outputs). The total counts nu = sum(ctrlnum) and nout = sum(outnum) dimension mjData.ctrl and mjData.actuator_force, respectively, nactuator is the number of actuators. For existing actuators ctrnum = outnum = 1, so nactuator == nu == nout and existing code is unaffected.

    2. 56a93979 Setpoints of position and intvelocity servos acting on 3D rotational transmissions (ball joints, or site transmissions with a refsite and purely rotational gear) are now interpreted on the circle: the force uses the setpoint representative nearest the current angle, so targets winding beyond half a turn are tracked continuously instead of slipping by full turns. Behavior is identical whenever the error does not exceed π. Relatedly, intvelocity actuators now expose actlimited, which was previously hardcoded to "true": as for general actuators it defaults to "auto", so activation clamping is enabled by specifying actrange. Unclamped integrated setpoints are well-behaved on rotational transmissions, where they wrap.

    3. 072e963f Added the orientation actuator: a geodesic servo on a new SO(3) transmission (ball joints, or a site with a refsite), acting jointly on the full relative orientation with an exact equilibrium at every commanded orientation. This is the first actuator with multiple force outputs (3), and, with input="quat", the first with different input and output dimensions (4 controls, 3 outputs). The input signature is recorded in the new mjModel.actuator_ctrlspec, exposed as the input attribute.

    [Image: Watch video](https://youtu.be/17XpwnqyCXs)

    1. 072e963f Added mj_actuatorInputName, returning the name of an actuator input (e.g. "qw" for the first control of a quaternion-commanded orientation actuator). The control sliders in simulate and MuJoCo Studio are now generated per control and labeled with the actuator name plus the input name suffix.

    2. 072e963f Viewer control sliders now use a defined ctrlrange even when ctrllimited is "false": the range sets the slider span, while clamping remains controlled by ctrllimited.

    3. 072e963f Added mj_resetCtrl, setting controls to neutral values: zero, except quaternion inputs which reset to the identity quaternion. Called by mj_resetData and the viewers' "Clear All".

    Solvers

    1. ea230a95 Flex elasticity (stretch, bending, interpolation stiffness) is now integrated implicitly inside the CG constraint solver via an effective metric: the mass matrix is augmented with the stiffness Hessian, so contact and elastic forces are solved against one consistent metric. This replaces the previous post-hoc CG correction, which modified qacc after the constraint solve. The gate is solver="CG" with an implicit integrator and flex stiffness present; Newton and PGS are unaffected. Bending-only models pay zero per-step factorization cost (the factor is precomputed in mj_setConst). Inverse dynamics (mj_inverse) is now discrete-consistent with forward dynamics for gated models.

    2. c499f7f2 Added Nesterov momentum extrapolation with adaptive gradient restart (O'Donoghue-Candès) to the PGS solver, significantly improving convergence. Overall PGS now requires ~2x fewer iterations.

    3. 1e66efd1 Added the Newton decrement -- the quadratic model's predicted cost improvement of the next iteration -- as a third early-termination criterion of the Newton solver, alongside cost improvement and gradient norm. This reduces iteration counts at no accuracy cost. Proposed by @adenzler-nvidia in MJWarp pull request 1520.

    4. c69ef030 The CG and Newton solvers now terminate with zero iterations when a duality-gap certificate proves that the warmstarted solution already satisfies the tolerance. The certificate requires only the existing mass-matrix factorization, so quiescent scenes skip Hessian construction, factorization and the line search entirely. Newton zero-iteration exits additionally require the gradient criterion, preserving Newton's characteristic force-level accuracy. See Warmstart in the Computation chapter for details.

    Compiler

    1. 4e1795b9 mj_encode now supports encoding of MJB and TXT files.

    2. c6c3ec31 The attach element now supports self-attachment (attaching elements of the current model to itself) by omitting the model attribute. It also supports attaching a frame via the new frame attribute, which is mutually exclusive with body.

    3. 040872fd Fixed loading of .mjz archives in simulate: the archive was unmounted before model compilation, so assets failed to load. Failures in the mjz decoder now emit a warning with the underlying error instead of the generic "could not decode content" message.

    4. ebd4abae The mjz decoder now searches for model.xml and <stem>/model.xml as a fallback if <stem>.xml and <stem>/<stem>.xml are not found.

    5. dc7581ac Added support for resource writing via mju_writeResource and the write callback in mjpResourceProvider.

    [!WARNING] Breaking API changes

    1. d83ef0b6 The return type of mj_encode and the mjfEncode callback changed from int to mjtSize (64-bit).

    [!NOTE] Bug fixes

    1. f5f9d9ef Fixed a bug in the mesh compiler where normals were scaled as vectors rather than covectors.

    Python bindings

    1. a07ae6f8 The bindings now support free threading (PEP 703) for Python 3.14.

    Documentation

    1. 1f1bfa9e Expanded documentation for spec.encode workflows and added detailed documentation for the MJZ Archive format (.mjz / .zip).