Skip to content

mayaMatchMoveSolver-v0.3.13

Compare
Choose a tag to compare
@david-cattermole david-cattermole released this 29 Mar 01:08
· 2031 commits to master since this release

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

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.