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