mayaMatchMoveSolver-v0.3.2

Release v0.3.2 is a bug fix release, with some new features focused on improving loading 2D data into mmSolver.

The Marker loading workflow has been improved, this release includes the ability to use non-uniform overscan (both width and height values), as well as a new feature to avoid the need to manually enter overscan values on a Marker Group node at all. To get the latest features for the Load Marker tool, be sure to upgrade your 3DEqualizer export scripts.

This release also improves the documentation page with updated screen shots and documentation for more tools.

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

---

Below is a list of some of the new features, changes and bugs that are fixed in v0.3.2.

New features

• #133 - Added a new tool to visualise the screen-space position of any Maya transform node, across time.
• #131 - The Load Markers tool can now automatically compensate for any overscan values used in the Maya camera. The new feature requires the 3DEqualizer project used for 2D tracking to be set to the correct field of view, otherwise it is advised to turn "Use Embedded Overscan" off.
• #127 - If your workflow requires non-uniform overscan values (for both width and height), you can now set these on the Marker Group node. Note: you do not need to set overscan values if using the "Use Embedded Overscan" feature.

Changes

• Moved the Copy Camera to Clipboard tool into it's own sub-menu group in the mmSolver shelf/menu.

Bug Fixes

• #125 - Fixes the Create/Remove Controller, and Re-Parent tools; the tools did not behave as expected in previous versions.
• #129 - Fixed the 3DEqualizer Paste Camera tool, when re-opening the UI a second time in 3DE.
• #130 - Fixed the use of hidden meshes for Ray-Casting, when the parent transform of a mesh node is hidden.
• #132 - Converting a Maya transform node into a Marker is now faster, and does not error when multiple transform nodes are selected.
• #104 - Minor scripting incompatibilities with v0.2.x have been improved (however there are still changes between v0.2.x and v0.3.x which are not fixed, and may not be fixed).

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