Welcome to MotionBuilder 2026.1!

You can access this release from your Autodesk Account.

This release introduces new icons along with other general workflow improvements.

Enhanced icons and scaling support

MotionBuilder 2026.1 introduces new, high-resolution icons to enhance the user experience and support better scaling on high-DPI displays. This update ensures that icons are crisp, clear, and easy to recognize regardless of your screen resolution or size.

Configurable default scene frame rate

The default scene frame rate to use when starting MotionBuilder, or when creating a new scene, is now configurable in Preferences under the new Transport Controls section, streamlining your workflow and improving precision in animations.

New connection styles and grid snapping for Relations constraints

Connection styles

We added four new connection styles to the Relations constraints' graph interface. These connection styles are: Bezier, Straight, Corner, S-Shape, and contribute to a more efficient, flexible, and user-friendly experience when working with the Relations constraints' graph in MotionBuilder.

Grid snapping

You can now activate grid snapping in a Relations constraint. Grid snapping ensures accurate alignment of boxes, which is useful when organizing complex scenes. This feature is inactive by default, but you can activate it through the contextual menu within the Relations constraint. Additionally, you can change the value of this new property when creating a new Relations constraint using the new config:

Application.txt
[Display]
RelationConstraintGridSnapping = No;
Snap relation constraint boxes to grid when dragging (Default: No) (Yes/No).

New search bar in the Property View

MotionBuilder 2026.1 introduces a new search bar feature within the Property View. This enhancement lets you filter the displayed properties quickly and efficiently. The search bar supports regular expressions, making it easy to locate specific properties.

New Auto-Save Unsaved Unnamed Scripts functionality in the Python Editor

A new preference named Auto-Save Unnamed Scripts on Exit is now available in the Python Editor of MotionBuilder. Active by default, this new preference keeps unnamed scripts in the Python Editor without having to either save or discard them when quitting the software.

An unnamed script is surrounded by the "<>" characters, like the generic "" tab, and has never been saved to disk.

This new preference is applicable when the Reload Last Scripts on Startup preference is active.

For edited scripts (scripts already saved to disk but with changes unsaved), MotionBuilder will still ask you to save or discard the changes on exit, regardless of the new preference value.

If MotionBuilder crashes, it will now try to automatically auto-save all unnamed scripts, regardless of the preference value. For edited scripts, it asks you to save, discard, or preserve both copies of the script. The Python Editor will display the edited version the next time you relaunch MotionBuilder.

We've introduced a new config related to this new feature:

Application.txt
[Python]
AutoSaveUnnamedScripts = Yes;
Auto-save unnamed scripts (never saved to disk) on exit (Default: Yes) (Yes/No).

Added functionality to set new environment variables using License.env

We've added the MOBU_LOCATION environment variable (similar to MAYA_LOCATION), allowing you to set up required paths (like xml, pit) relative to the install without hardcoding them. Additionally, you can now set the environment variables AUTODESK_ADLM_THINCLIENT_ENV, MOBU_LEGACY_THINCLIENT, and ADSKFLEX_LICENSE_FILE in the bin\License.env file.

Updates to the MotionBuilder SDK

We implemented a new addition to the FBUndoManager class: the TransactionAddObjectCreate SDK method. This new method enhances your workflow by adding object creation to the Undo stack. With TransactionAddObjectCreate, you can now easily undo and redo object creation actions, providing better control over your project.

We also introduced a new FBVector4MatrixMult SDK helper function. Unlike the previous FBVectorMatrixMult function, which didn't compute a real 4x1 vector by a 4x4 matrix (as it always considered the value of 1 for the 4th component of the vector), the new FBVector4MatrixMult function now provides a true mathematical implementation, improving the precision and reliability of your scenes.