mayaMatchMoveSolver-v0.4.0.alpha3

DO NOT USE THIS IN PRODUCTION!!!
This version of mmSolver is for testing only!

This is a feature incomplete and buggy release of the upcoming v0.4.0 release of mmSolver.

This release contains fixes for Maya 2022 / Python 3, a new (2D) "Line" object type and an accurate "live" image plane to preview 3DEqualizer lens distortion.

The 2D Line is intended to be used to align to straight edges in a plate and then be used to solve lens distortion without any 3D (Bundle) information.
The lens solving part is not yet implemented, however the 2D Line can be used to visualise the line while you manually adjust the lens attributes.
This new 2D Line object is also integrated into the Camera Calibration set up (first introduced in v0.3.15).

The "live" image plane has been improved with a traditional "baked" (non-editable) image plane option and can be toggled with an attribute on the transform node (see the "Extra Attributes" roll out).
The lens distortion effects on the live image plane are accurate to the 3DE "classic" lens distortion model, so values from mmSolver can be (manually) typed into 3DEqualizer, Nuke or Natron and produce the same lens distortion effects.

---

Load mmSolver in Maya 2022

To load mmSolver on Maya 2022 you must run the following MEL command:

mmsolver_load

This will load the mmSolver plug-in, and allow you to automatically load the mmSolver plug-in and will ensure it is loaded each time Maya is started.

If you wish to unload mmSolver so it will not be loaded at Maya start-up run the following MEL command:

mmsolver_unload

These new commands were added to work-around the new Maya 2022+ Security preferences and ensure mmSolver will be loaded when it's needed.

Additionally the Python module mmSolver.startup was added, and allows pipelines to manually load mmSolver with the Python commands:

import mmSolver.startup
mmSolver.startup.mmsolver_startup()

---

Features / Changes

The main changes in this release:

• Improves support for Maya 2022 / Python 3, especially for these tools:
  • Smooth Keyframes tool.
  • Change Rotation Order (Morgan Loomis - ML Tools)
  • User Preferences save correctly.
• Introduces the Line shape node, mmSolver.api.Line() API object and related tools
• The "live" image plane distortion plane accurately matches 3DEqualizer lens distortion.
• The image plane loads a default image when created.
• Improved visual display of Camera Calibration setup (with new Line nodes).
• Added horizon line and axis dome presets for mmSkyDome shape node.

Developer (low-level) changes:

• Marker are now assumed to always be under a camera with the translate X/Y values representing the position on the image plane in the range -0.5 to +0.5.
• Parity between MM Scene Graph and Maya DAG 3D transform reprojection methods.
• Internal tests have been upgraded - most tests have been improved and tested.
• Changed structure of C++ code.
• Build system improvements to allow multiple Maya versions and platforms to build from the same project directory.
  • .ui to .py file generation is still generated in the source tree which creates issues.

---

Known Problems

• Compatibility with Maya scenes with mmSolver v0.3.x nodes may not work as expected - please report issues.
• Solving with the new "Scene Graph" option in the Solver UI will cause a crash if solving with the "Standard" tab.
• Marker nodes may not update position in the Viewport when moving the camera - this is a Maya playback cache/viewport update bug.
• The Viewport 2 "MM Renderer" has aliasing problems and does not allow changing the "mode" of the viewport.
• Marker shape nodes change size when the marker depth or camera focal length is adjusted.

---

Please report any bugs or suggestions you find in this release here and clearly state the version of mmSolver you are testing.

mayaMatchMoveSolver-v0.4.0.alpha2

DO NOT USE THIS IN PRODUCTION!!!
This version of mmSolver is for testing only!

This is a feature incomplete and buggy release of the upcoming v0.4.0 release of mmSolver.

This release version now supports Linux and Windows, and (mostly automatic) start-up on Maya 2022.

---

Load mmSolver in Maya 2022

To load mmSolver on Maya 2022 you must run the following MEL command:

mmsolver_load

This will load the mmSolver plug-in, and allow you to automatically load the mmSolver plug-in and will ensure it is loaded each time Maya is started.

If you wish to unload mmSolver so it will not be loaded at Maya start-up run the following MEL command:

mmsolver_unload

These new commands were added to work-around the new Maya 2022+ Security preferences and ensure mmSolver will be loaded when it's needed.

Additionally the Python module mmSolver.startup was added, and allows pipelines to manually load mmSolver with the Python commands:

import mmSolver.startup
mmSolver.startup.mmsolver_startup()

---

Features

The following features are included in various levels of completion...

Compatibility:

• #217 - Python 2.7 and 3.x and Maya 2022+ Support

Solver Features and Performance:

• #106 - Solve Lens Distortion
• #114 - Core Solver - Use In-Memory Representations of Bundles and Cameras
• #144 - Core Solver - Add libmv solver
• #174 - Core Solver - Add Ceres Solver
• #175 - Custom Marker and Bundle Transform Nodes

Build System:

• #149 - Remove Qt from Build Dependency
• #150 - Refactor CMake Build System
• #167 - Update to C++11 Standard
• #172 - Add Lens Distortion Plug-in Kit (LDPK) to Build System

User Interface and Viewport:

• #21 - Maya Plugin - Create a Shape Node for Markers
• #67 - Maya Plugin - Create a Shape Node for Bundles
• #120 - Maya Tool - Add Marker Line
• #216 - Maya Plugin - Create Sky Dome Viewport Visualiser Node
• #231 - Viewport Renderer for MatchMove

---

Known Problems

• Compatibility with Maya scenes with mmSolver v0.3.x nodes may not work as expected - please report issues.
• Solving with the new "Scene Graph" option in the Solver UI will cause a crash if solving with the "Standard" tab.
• Marker nodes may not update position in the Viewport when moving the camera - this is a Maya playback cache/viewport update bug.
• The created Image Plane polygon does not contain an image or shader at all - this will be added in a future release.
• The Viewport 2 "MM Renderer" has aliasing problems and does not allow changing the "mode" of the viewport.
• Marker shape nodes change size when the camera focal length is adjusted.

---

Please report any bugs or suggestions you find in this release here and clearly state the version of mmSolver you are testing.

mayaMatchMoveSolver-v0.4.0-alpha.1

DO NOT USE THIS IN PRODUCTION!!!
This version of mmSolver is for testing only!

This is a feature incomplete and buggy release of the upcoming v0.4.0 release of mmSolver.

---

The following features are included in various levels of completion...

Compatibility:

• #217 - Python 2.7 and 3.x and Maya 2022+ Support

Solver Features and Performance:

• #106 - Solve Lens Distortion
• #114 - Core Solver - Use In-Memory Representations of Bundles and Cameras
• #144 - Core Solver - Add libmv solver
• #174 - Core Solver - Add Ceres Solver
• #175 - Custom Marker and Bundle Transform Nodes

Build System:

• #149 - Remove Qt from Build Dependency
• #150 - Refactor CMake Build System
• #167 - Update to C++11 Standard
• #172 - Add Lens Distortion Plug-in Kit (LDPK) to Build System

User Interface and Viewport:

• #21 - Maya Plugin - Create a Shape Node for Markers
• #67 - Maya Plugin - Create a Shape Node for Bundles
• #120 - Maya Tool - Add Marker Line
• #216 - Maya Plugin - Create Sky Dome Viewport Visualiser Node
• #231 - Viewport Renderer for MatchMove

---

Known Problems:

• Microsoft Windows is currently the only supported operating system - Linux (CentOS 7) support will be added in a newer version.
• Compatibility with Maya scenes with mmSolver v0.3.x nodes may not work as expected - please report issues.
• Solving with the new "Scene Graph" option in the Solver UI will cause a crash if solving with the "Standard" tab.
• Marker nodes may not update position in the Viewport when moving the camera - this is a viewport update bug.
• The created Image Plane polygon does not contain an image or shader at all - this will be added for final release.
• The Viewport 2 "MM Renderer" has aliasing problems and does not allow changing the "mode" of the viewport.
• Marker shape nodes change size when the camera focal length is adjusted.

MAYA 2022 NOTE: This has successfully been opened and loaded in Maya 2022 with (the default) Python 3 mode enabled, however mmSolver shelves and menus will not be created by default (it's a known bug #217). To load the mmSolver shelves and menus each time Maya opens, you must manually open and run the contents of mayaMatchMoveSolver-0.4.0-maya2022-linux/scripts/userSetup.py in the Maya Script Editor. This should generate the shelves and menus the same as previous versions of Maya.

---

Please report any bugs or suggestions you find in this release here and clearly state the version of mmSolver you are testing.

mayaMatchMoveSolver-v0.3.15

Release v0.3.15 provides a new Camera Calibration tool (currently beta), Convert Rotation Order tool (from Morgan Loomis - ML Tools) tool, a Blender add-on to Copy/Export 2D Markers, support for 3DEqualizer4 Release 7 (#225), as well as bug fixes and minor features.

Download the archive file for your operating system and Maya version, and follow the INSTALL.md instructions.

---

New Features

• (#225) Support for 3DEqualizer4 Release 7 (Python 3), while keeping the backwards compatibility.
  • Also available on 3DEqualizer ScriptDB.
• (#201 #233) Integrated Change Rotation Order tool from the fantastic Morgan Loomis - ML Tools).
  • Thanks to @ktonegawa!
• (#62) Blender Add-On to Copy and Export 2D Marker data from Blender to Maya.
  • See the blender Add-on installation documentation for more details (including the limitations).
• (#227) The Convert to Marker tool allows Bundle positions take on the 3D location of the input transform when Converting a 3D transform to a Marker.
  • Available on the shelf/menu mmSolver > General Tools > Convert Rotation Order....
• (#121) Camera Calibration tool to calculate camera line ups (translate, rotation and focal length) from parallel 2D lines.
  • Inspired by fSpy and the fSpy project.
  • This tool is currently Beta because it lacks displaying 2D lines and a user-interface for the user, however the tool is functional.
• (#230) Project Marker on Mesh (Ray-Cast) now has the ability to rotate the bundle in various ways.

Bug fixes

• (#236) When Cameras are pasted into 3DEqualizer the playback frame range is reset to the full frame range.
• (#232) Fixed solving single frames of static attributes.
  • Thanks to @ktonegawa!
• (#229) Fixed the Legacy solver tab (although it is deprecated and will be removed in future versions - it is recommended to use the Basic or Standard tabs).
• (#228) Fixed errors when trying to re-parent nodes with locked transform attributes.

Changes

• Bundles now display Rotate, Scale b and Translate attributes in the channel box.
  • This change was made for #230.

Developer Notes

• Now requires CMake 3.15+ to build, for support of packing the Blender Add-On .zip file via CMake.

Known Issues

• Evaluation
  • Solver engine can become slow with many attributes.
  • The Maya viewport is refreshed during solving to force Maya to evaluate all nodes in the solve. This causes slower performance (e.g. 6 seconds verses 30 seconds), but ensures accurate solver results. Users may wish to turn this feature off in the Solver UI > Edit > Refresh Viewport check box.
• Maya 2016
  • Maya 2016 is unsupported by the mmSolver project, we are not able to provide testing for Maya 2016.
  • On Linux has problems with the new user preferences UI - the release for Maya 2016 is available for download, with this limitation.
  • the Solver UI disables selection of the Attributes - the cause is unknown.
  • The mmSolverType command raises an error with certain flags on Maya 2016 for an unknown reason. This problem is specific to Maya 2016, the same command works on Maya 2017+.
• Compatibility
  • New v0.3.0 default values will not be used until a new Collection is created. Delete your previous Collection and create a new Collection using the Solver UI > File > New Collection menu item.
• Development/Building:
  • The test suite fails on 3 different solver tests, due to a deviation that is too high, this is intentional and will be fixed in a future version.

mayaMatchMoveSolver-v0.3.14

Release v0.3.14 integrates the Qt.py into mmSolver directly. There is no longer any need to install it manually. Additionally some bugs have been fixed, the Remove Controllers, Reparent Under Node and Unparent to World tools have been improved.

Download the archive file for your operating system and Maya version, and follow the INSTALL.md instructions.

---

New Features

• (#200) Updated "Reparent" window with added features.
  • See Reparent UI documentation.

Bug fixes

• (#221) Fix "Remove Controller" tool when the controller is parented under other nodes, also supports baking/removing multiple controllers at once.
  • Thanks to Patcha Saheb Binginapalli.
  • See Remove Controller documentation.
• (#222) Fix "Object Relationships" checkbox in Solver UI from being always enabled after being enabled once.
• (#223) Fix crash when opening/creating new scene files.
• (#224) Fix problems with Marker deviation curves after solving.

Changes

• mmSolver Marking Menu (A + left-click) has updated tools for Create/Remove Controller and Re-parenting tools.
• (#156) Qt.py has been integrated into the mmSolver.ui.Qt sub-package and no longer needs to be installed separately.

Known Issues

• Evaluation
  • Solver engine can become slow with many attributes.
  • The Maya viewport is refreshed during solving to force Maya to evaluate all nodes in the solve. This causes slower performance (e.g. 6 seconds verses 30 seconds), but ensures accurate solver results. Users may wish to turn this feature off in the Solver UI > Edit > Refresh Viewport check box.
• Maya 2016
  • Maya 2016 is unsupported by the mmSolver project, we are not able to provide testing for Maya 2016.
  • On Linux has problems with the new user preferences UI - the release for Maya 2016 is available for download, with this limitation.
  • the Solver UI disables selection of the Attributes - the cause is unknown.
  • The mmSolverType command raises an error with certain flags on Maya 2016 for an unknown reason. This problem is specific to Maya 2016, the same command works on Maya 2017+.
• Compatibility
  • New v0.3.0 default values will not be used until a new Collection is created. Delete your previous Collection and create a new Collection using the Solver UI > File > New Collection menu item.
• Development/Building:
  • The test suite fails on 3 different solver tests, due to a deviation that is too high, this is intentional and will be fixed in a future version.

mayaMatchMoveSolver-v0.3.13

Release v0.3.13 adds support for Maya 2020 on Windows and Linux, and adds some very helpful and long-overdue new tools; the Center 2D offsets, Create/Remove Controllers v2, Screen-Space Rig Bake, and Bake Attributes tools.

Unfortunately, this release also removes support for Maya 2016. The plug-in is untested on Maya 2016.

Download the archive file for your operating system and Maya version, and follow the INSTALL.md instructions.

---

New Features

• (#135 #209) Center 2D with offsets (thanks to Kazuma Tonegawa).
  • See Center 2D documentation.
• (#184) Bake Attributes UI (thanks to Patcha Saheb Binginapalli).
  • See Bake Attributes documentation.
• (#193 #192) Create / Remove Controller tool (version 2) (thanks to Patcha Saheb Binginapalli).
  • See Add / Remove Controller documentation.
• Screen-Space Rig Bake (thanks to Patcha Saheb Binginapalli).

Changes

• (#151) Added support for Maya 2020 (Windows and Linux).
• (#206) Each UI now contains an "Edit" and "Help" menu, and the "Reset" button has been removed from most UIs.
• Maya 2016 is unsupported by the mmSolver project, we are not able to provide testing for Maya 2016.

Known Issues

• Evaluation
  • Solver engine can become slow with many attributes.
  • The Maya viewport is refreshed during solving to force Maya to evaluate all nodes in the solve. This causes slower performance (e.g. 6 seconds verses 30 seconds), but ensures accurate solver results. Users may wish to turn this feature off in the Solver UI > Edit > Refresh Viewport check box.
• Maya 2016
  • Maya 2016 is unsupported by the mmSolver project, we are not able to provide testing for Maya 2016.
  • On Linux has problems with the new user preferences UI - the release for Maya 2016 is available for download, with this limitation.
  • the Solver UI disables selection of the Attributes - the cause is unknown.
  • The mmSolverType command raises an error with certain flags on Maya 2016 for an unknown reason. This problem is specific to Maya 2016, the same command works on Maya 2017+.
• Compatibility
  • New v0.3.0 default values will not be used until a new Collection is created. Delete your previous Collection and create a new Collection using the Solver UI > File > New Collection menu item.
• Development/Building:
  • The test suite fails on 3 different solver tests, due to a deviation that is too high, this is intentional and will be fixed in a future version.

mayaMatchMoveSolver-v0.3.12

Release v0.3.12 fixes solver evaluation issues, improves UI features, and adds Remove Solver Nodes tool.

Download the archive file for your operating system and Maya version, and follow the INSTALL.md instructions.

---

New Features

• (#76 and #181) Remove All Solver Nodes (thanks to Kazuma Tonegawa!)
  • Delete mmSolver nodes from the Maya scene - for scene clean up.
  • See Remove Solver Nodes documentation.
• (#187) Add "Evaluate Object Relationships" check-box - disabled by default.
  • Reduces solve time for simple solves and Maya scenes with character rigs.
  • See Solver Option documentation.
• (#195) Only show the Solver UI progress bar and solve information while solving.
  • See User Preferences documentation to enable/disable the feature.
• (#208) Add default hotkey for Project Markers on Meshes (as "ALT + p").
  • See default hotkeys documentation.

Changes

• (#185) Change the Solver UI button text while solving.
  • The button text explains what will be done when clicking the button.
• Added names to the "Special Thanks" section.
• Added documentation page for User Preferences window.
• Added the current mmSolver version in the Solver UI window title.

Bug Fixes

• (#183 and #207) Fixed evaluation of rigs with nodes using multi-compound attributes (thanks to Kazuma Tonegawa!)
• (#194) Do not disable the viewport when projecting markers on to meshes for only one frame.

For Developers

• Fixed CMake warnings about "BOOLEAN" variables.

Known Issues

• Evaluation
  • Solver engine can become slow with many attributes.
  • The Maya viewport is refreshed during solving to force Maya to evaluate all nodes in the solve. This causes slower performance (e.g. 6 seconds verses 30 seconds), but ensures accurate solver results. Users may wish to turn this feature off in the Solver UI > Edit > Refresh Viewport check box.
• Maya 2016
  • On Linux has problems with the new user preferences UI - the release for Maya 2016 is available for download, with this limitation.
  • the Solver UI disables selection of the Attributes - the cause is unknown.
  • The mmSolverType command raises an error with certain flags on Maya 2016 for an unknown reason. This problem is specific to Maya 2016, the same command works on Maya 2017+.
• Compatibility
  • New v0.3.0 default values will not be used until a new Collection is created. Delete your previous Collection and create a new Collection using the Solver UI > File > New Collection menu item.
• Development/Building:
  • The test suite fails on 3 different solver tests, due to a deviation that is too high, this is intentional and will be fixed in a future version.

mayaMatchMoveSolver-v0.3.11

Release v0.3.11 adds a few useful tools, and fixes some bugs.

Download the archive file for your operating system and Maya version, and follow the INSTALL.md instructions.

---

New Features

• Project Markers on Mesh UI
  • (#177) Projection on a frame range (animated, multiple frames)
  • (#179) Display Layers are checked for visibility on meshes.
  • (#178) Uses smooth-preview mesh, if enabled on a mesh to be projected on.
• (#128) Add support for rolling shutter correction with Marker (2D Tracks) export from 3DEqualizer. documentation
  • Download the scripts on 3DEqualizer ScriptDB here and here
• (#180) - Add a "Special Thanks" credits to the About window, and documentation.

Changes

• An option box has been added for the Smooth Keyframes UI - documentation

Bug Fixes

• (#165) Attribute nodes with identical Maya UUIDs are now correctly added into the Solver UI.
• (#182) Bug fix for Paste Camera (in 3DEqualizer)
  • documentation
  • Download on 3DEqualizer ScriptDB here

For Developers

• (#165) mmSolver.api.Attribute.get_node() was fixed to return the correct node name when there are duplicate UUIDs in a Maya scene.
• Added Option Box configuration options for the (dynamic) shelf and menu creation.

Known Issues

• Evaluation
  • Solver engine can become slow with many attributes.
  • The Maya viewport is refreshed during solving to force Maya to evaluate all nodes in the solve. This causes slower performance (e.g. 6 seconds verses 30 seconds), but ensures accurate solver results. Users may wish to turn this feature off in the Solver UI > Edit > Refresh Viewport check box.
• Maya 2016
  • On Linux has problems with the new user preferences UI - the release for Maya 2016 is available for download, with this limitation.
  • the Solver UI disables selection of the Attributes - the cause is unknown.
  • The mmSolverType command raises an error with certain flags on Maya 2016 for an unknown reason. This problem is specific to Maya 2016, the same command works on Maya 2017+.
• Compatibility
  • New v0.3.0 default values will not be used until a new Collection is created. Delete your previous Collection and create a new Collection using the Solver UI > File > New Collection menu item.
• Development/Building:
  • The test suite fails on 3 different solver tests, due to a deviation that is too high, this is intentional and will be fixed in a future version.

mayaMatchMoveSolver-v0.3.10

Release v0.3.10 fixes a node evaluation problem when using complex rigs, and deforming geometry with rivets.

Download the archive file for your operating system and Maya version, and follow the INSTALL.md instructions.

---

New Features

• (#176) The "Evaluate Complex Node Graphs" check box was added to the Solver UI Standard and Basic tabs.
  • The new check box, when enabled, will change the internal evaluation method to help solve "complex" node networks (such as Mesh Rivets which have cyclical node connection networks).

Performance numbers for a test scene:

Maya 2018 v0.3.10 - avg deviation 2.27px | time 334.400sec - Eval Complex Graphs=OFF
Maya 2019 v0.3.10 - avg deviation 2.27px | time 304.046sec - Eval Complex Graphs=OFF
Maya 2018 v0.3.10 - avg deviation 2.27px | time 870.519sec - Eval Complex Graphs=ON
Maya 2019 v0.3.10 - avg deviation 2.28px | time 903.377sec - Eval Complex Graphs=ON
Maya 2018 v0.3.9 - avg deviation 2.28px | time 369.991sec
Maya 2019 v0.3.9 - avg deviation 2.27px | time 282.662sec

Changes

• The Solver UI Validate button and text is now grouped and hidden or shown together using the User Preferences "Show Validate Button" option.
• Turn off Maya's "Auto Keyframe" feature while performing a solve.
• Turn off Maya's "Cycle Check" feature while performing a solve.

Bug Fixes

• (#176) rivets and complex rig or large node networks will not be removed from the solver.
• Solving per-frame animated attributes failed on Maya 2016, 2017 and 2019 (but strangely not Maya 2018). This is now fixed.
• Constrained plugs that were added into a Collection for solving would incorrectly be listed as "static" attributes. These plugs are now considered "locked".

For Developers

• Added mmSolver.api.TIME_EVAL_MODE_DG_CONTEXT, mmSolver.api.TIME_EVAL_MODE_SET_TIME and mmSolver.api.TIME_EVAL_MODE_LIST
• Added timeEvalMode flag to the maya.cmds.mmSolver() command to force different time evaluation modes (helps to fix #176).
• mmSolver.utils.nodeaffects.find_plugs_affecting_transform() and mmSolver.api.find_marker_attr_mapping() now considers the connected DG network, rather than just the DAG network (helps to fix #176).
• Added mmSolver.api.SolverStep.get/set_time_eval_mode()
• Added mmSolver.api.SolverBasic.get/set_eval_complex_graphs().
• Added mmSolver.api.SolverStandard.get/set_eval_complex_graphs().

Known Issues

• Maya 2016 on Linux has problems with the new user preferences UI - the release for Maya 2016 is available for download, with this limitation.
• In Maya 2016, the Solver UI disables selection of the Attributes - the cause is unknown.
• Solver engine can become slow with many attributes.
• New v0.3.0 default values will not be used until a new Collection is created. Delete your previous Collection and create a new Collection using the Solver UI > File > New Collection menu item.
• The Maya viewport is refreshed during solving to force Maya to evaluate all nodes in the solve. This causes slower performance (e.g. 6 seconds verses 30 seconds), but ensures accurate solver results. Users may wish to turn this feature off in the Solver UI > Edit > Refresh Viewport check box.
• The test suite fails on 3 different solver tests, due to a deviation that is too high, this is intentional and will be fixed in a future version.
• The test suite fails to run on Maya 2018 with mayapy, the cause is unknown.
• The mmSolverType command raises an error with certain flags on Maya 2016 for an unknown reason. This problem is specific to Maya 2016, the same command works on Maya 2017+.

mayaMatchMoveSolver-v0.3.9

Release v0.3.9 provides a user preferences window to control the "Add New Markers to Collection" feature (#164), and changes the solver validation system.

Download the archive file for your operating system and Maya version, and follow the INSTALL.md instructions.

---

New Features

• (#164) Users can turn on/off the "Add New Markers to" feature in the User Preferences window (mmSolver > General Tools > User Preferences... menu)
• (#166) Skip invalid frames from solving, rather than not allowing to solve at all.

Changes

• Validate button in the Solver UI has been hidden by default.
  • Turn on the old behaviour on in the "User Preferences" window, with the "Solver UI Preferences > Show Validate Button" option.
  • The text showing the deviation, parameters and frames now reads "INFORMATION" unless the preference is changed.
• When opening the Solver UI, no solver validation will occur.
  • Turn on the old behaviour on in the "User Preferences" window, with the "Solver UI Preferences > Validate on open" option.
• Adding a Camera transform will not add the scale attribute to the Solver UI by default.

Bug Fixes

• Rotation Euler filter will now filter all animated rotation attributes.
• (#165) Attempt to fix incorrect being added to solver UI - if this still happens, please comment on the issue.

For Developers

• mmSolver.api.createExecuteOptions() is deprecated and will be removed in v0.4.0, please use mmSolver.api.create_execute_options().
• mmSolver.api.validate() now has a as_state keyword to allow returning a list of ActionState. (this defaults to False currently but in v0.4.0 it will be removed and defaulted to True)
• Add mmSolver.api.ActionState object type.
  • This new ActionState is returned from mmSolver.api.validate(as_state=True).

Known Issues

• Maya 2016 on Linux has problems with the new user preferences UI - the release for Maya 2016 is available for download, with this limitation.
• In Maya 2016, the Solver UI disables selection of the Attributes - the cause is unknown.
• Solving per-frame animated attributes fails on Maya 2017 - it is recommended to use Maya 2018+
• Solver engine can become slow with many attributes.
• New v0.3.0 default values will not be used until a new Collection is created. Delete your previous Collection and create a new Collection using the Solver UI > File > New Collection menu item.
• The Maya viewport is refreshed during solving to force Maya to evaluate all nodes in the solve. This causes slower performance (e.g. 6 seconds verses 30 seconds), but ensures accurate solver results. Users may wish to turn this feature off in the Solver UI > Edit > Refresh Viewport check box.
• The test suite fails on 3 different solver tests, due to a deviation that is too high, this is intentional and will be fixed in a future version.
• The test suite fails to run on Maya 2018 with mayapy, the cause is unknown.
• The mmSolverType command raises an error with certain flags on Maya 2016 for an unknown reason. This problem is specific to Maya 2016, the same command works on Maya 2017+.