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+.

mayaMatchMoveSolver-v0.3.8

Release v0.3.8 is the same as v0.3.7 but with a small bug fix.

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

---

Below is a list of the bug fixes in v0.3.8.

Bug Fixes

• (#163) Ensure the Solver UI root frames "Set Auto" button sets at least 2 root frames.

Known Issues

• 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+.

mayaMatchMoveSolver-v0.3.7

Release v0.3.7 with new features to improve performance and stability, and with many bug fixes.

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

---

Below is a list of the new features, changes and bug fixes in v0.3.7.

New Features

• (#18) Improved performance of Solver UI update and refreshing (~300% faster).
• (#160) Add "Set Auto" button to Solver UI Rootframe widget, calculating the root frames based on the currently added Markers.
• (#138) Automatically add newly created Markers to active Collection.
• (#77) Print pop-up warning and error messages to the viewport.
• Add Marker and Attribute "status" column displaying if an object is used by the solver or not.
• Add "Attribute Tools > Open Graph Editor" shelf menu, to open the Maya Graph Editor.
• Add "Rename Markers/Bundles" right-click menu option to Object tab in the Solver UI.
• (#123) Allow custom plug-in transform nodes to be used for cameras.
• Add -withCameraDirectionRatio flag to maya.cmds.mmReprojection() command.
• Add output attribute outCameraDirectionRatio to the mmReprojection node.
• Add documentation to explain how to override the shelf and menus for an individual user, see this page.
• Add missing documentation for "Sort Outliner Nodes" tool, see this page.
• (#146) Beta support for Maya 2018 and 2019 on MacOS.

Changes

• Changed default attributes add to the Solver UI when no attributes are selected in the channel box.
  • Scale X, Y and Z attributes added by default.
• (#159) Add restrictions on what type of locator is considered a Bundle (all non-translates must be locked and non-keyable).
• (#153) Changed to short node names in the Solver UI Output Attributes widget.

Bug Fixes

• Fixed incorrect "Attribute Tools" shelf right-click menu, for the "minimal" shelf type.
• Fixed bug stopping Duplicate Markers tool from working correctly.
• Fixed bug in Convert to Screen-Space Transform and Convert to Marker tools, causing small screen-space Y translate offset.
• Fixed bug in deviation calculation that could cause the plug-in to crash Maya.
• (#162) Fixed forward slashes in the GUI for 3DEqualizer "Paste Camera" tool.
• (#161) Fixed incorrect forward slashes in file paths for Maya "Copy Camera" tool.
• (#153) Fixed incorrect node name queries in mmSolver.api.Attribute.

Changes for Developers

• Change build directory names, so each OS and Maya version produces a unique build directory name (multiple Maya version builds can happen at once).
• Added functions to API:
  • mmSolver.api.get_root_frames_from_markers()
  • mmSolver.api.action_func_is_mmSolverAffects()
  • mmSolver.api.SolverAffects()
  • mmSolver.api.Collection.get_attribute_used_hint()
  • mmSolver.api.Collection.get_attribute_used_hint()
  • mmSolver.api.Marker.get_used_hint()
  • mmSolver.api.Marker.set_used_hint()
• Add mmSolver.utils.event module, used for triggering events that happen in the mmSolver API.
• Added triggers when events happen in the API; mmSolver.tools.registerevents:
  • EVENT_NAME_MARKER_CREATED
  • EVENT_NAME_BUNDLE_CREATED
  • EVENT_NAME_COLLECTION_CREATED
  • EVENT_NAME_COLLECTION_MARKERS_CHANGED
  • EVENT_NAME_COLLECTION_ATTRS_CHANGED
  • EVENT_NAME_ATTRIBUTE_STATE_CHANGED
  • EVENT_NAME_ATTRIBUTE_CONNECTION_CHANGED
  • EVENT_NAME_NODE_NAME_CHANGED
  • EVENT_NAME_NODE_DELETED
  • EVENT_NAME_MEMBERSHIP_CHANGED
• Added command maya.cmds.mmSolverAffects to calculate "node affects relationships".
• Fixed SolverStandard class when calculating root-frames in a non-global way.
• Added new root frame solving strategy named ROOT_FRAME_STRATEGY_FWD_INCREMENT_VALUE.
  • The solver strategy will solve 3 frames at a time, moving forward in the list.
  • [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] to [[1, 2, 3], [1, 2, 3, 4, 5, 6], [1, 2, 3, 4, 5, 6, 7, 8, 9], [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]]
• Fixed mmSolver.api.SolverTriangulate() and now no longer breaks.
• Added one-liners for building and packaging from scratch.
• By default, the build scripts also create a (.zip or .tar.gz) package ready for release.
• (Windows MSVC) Stop logger macros from producing MSVC warning C4127.
• Add UNUSED macro to tell the compiler the variable is not used.
• (#152) Reduce the amount of C++ compiler warnings.

Known Issues

• 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+.

mayaMatchMoveSolver-v0.3.7-beta.1

This is a pre-release with experimental support for Maya 2019 on MacOS.
This version is functionally equal to v0.3.6, there are no extra features.

This is for testing only with issue #146.

To install, extract the .tar.gz archive and move the folder and .mod file into your home Maya version preferences "modules" folder:

/Users/<user name>/Library/Preferences/Autodesk/maya/2019/modules

You will need to create the "modules" folder if it does not exist.

Note: The MacOS Finder hides the "Library" folder. To open the Maya preferences folder, open Finder, and use the Go > Go to Folder... menu, then enter ~/Library/Preferences/Autodesk/maya and press "Go".

If there are issues, please comment on the issue #146.

mayaMatchMoveSolver-v0.3.6

Release v0.3.6 fixes bugs, improves UI performance and workflow.

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

---

Below is a list of the new features, changes and bug fixes in v0.3.6.

New Features

• Sort Selected Nodes In Outliner tool for organizing nodes.
• Average Deviation and Maximum Deviation attributes are now added to the Marker nodes (visible in channel box)
• Solver UI
  • 'Input Objects' and 'Output Attributes' panes can now be resized (using bar in the middle of panes).
  • #55 When opening the Solver UI, create a new collection if no Collection already exists in the scene.
  • Asks the user for confirmation before deleting a Collection node.
  • Markers show as dark-gray when they are disabled (depending on current frame).

Changes

• Improved performance of the Solver UI
  • Opening the UI
  • "Validate" and "Solve" buttons
  • Input objects scroll bar
• Improved performance of solver validation.
• mmSolver build scripts are now Python 3.x compatible.
• Reduced Solver UI empty space.
• Removed the 'Camera deviation' shown in the "Input Objects" pane - it was causing performance slow-downs.
• Removed unneeded profiling debug logging (for plug-in debugging) - off by default.
• Updates to the display of overscan values in the Load Marker UI.

Bug Fixes

• Fixed the Loader Marker UI when the 'User Embedded Overscan' checkbox is unchecked.
• Re-Fixed annoying selection callback bug - Parenting using the native Maya "p" hotkey failed to re-parent a transform node (fixed in commit 920f0b4).
  • This was originally fixed on some Maya versions in v0.3.5, but this failed on Maya 2017 Linux.
• Solver UI 'Edit' menu includes new checkboxes for smoothness/stiffness, and fixes for other checkboxes.
• Fixed the Average Deviation statistic - Deviation of markers when below -1.0 were counted toward average deviation.
• Fixed solver output for Maya 2018 (and above).
• Fixed 'Solve Current Frame' shelf button - it now solves the current frame rather than all frames.

Known Issues

• 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+.