Skip to content

mayaMatchMoveSolver-v0.3.3

Compare
Choose a tag to compare
@david-cattermole david-cattermole released this 09 Feb 21:40
· 3224 commits to master since this release

Release v0.3.3 is a bug fix release fixing the Convert to Markers tool.

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


Below is a list of the changes and bug fixes in v0.3.3.

Changes

  • Python 2.x is now explicit in the build process for mmSolver, before the build process assumed the user only has Python 2.x installed. Python 2.7.x is recommended.

Bug Fixes

  • #134 - Convert to Markers tool had error (released in v0.3.2) that caused the tool to stop working.
  • Bug fixed in mmSolver/ui/uimodel.py that stopped from setting data with the ItemModel class.
  • Fixed a rare naming bug when a name was converted into a valid Maya name.

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