Skip to content

mayaMatchMoveSolver-v0.3.5

Compare
Choose a tag to compare
@david-cattermole david-cattermole released this 13 Jun 17:37
· 3010 commits to master since this release

Release v0.3.5 contains a bug fix, and some new features.

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

New Features

Changes

  • Various Documentation improvements have been made.
  • Added a documentation page to help users download the latest version.

Bug Fixes

  • Fixed annoying selection callback bug - Parenting using the native Maya "p" hotkey failed to re-parent a transform node (fixed in commit c87bfd6).
  • Query the SolverWindow class instance failed when the class was valid; now fixed.
  • Sphinx Auto-Doc Mocking has been improved so that UIs now have documentation.

Known Issues

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