Skip to content

mayaMatchMoveSolver-v0.3.14
Compare
Choose a tag to compare
@david-cattermole david-cattermole released this 01 Aug 16:54
· 1979 commits to master since this release
v0.3.14
5208852

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.

Bug fixes

  • (#221) Fix "Remove Controller" tool when the controller is parented under other nodes, also supports baking/removing multiple controllers at once.
  • (#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.
Assets 14