mayaMatchMoveSolver-v0.3.16

Release v0.3.16 provides support for Maya 2022 (Python 3 - #217), support for importing PFTrack .txt/.2dt files with the Load Markers tool (#239), as well as bug fixes and minor changes.

For installation with Maya 2022, please see the special section in the INSTALL.md file.

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

---

New Features

• (#217) Maya 2022 (Python 3) support is now provided
  • Make sure to load the mmSolver plug-in manually in Maya 2022, because startup scripts no-longer work.
  • See INSTALL.md file. for more details.
• (#239) Loading 2D Trackers exported from PFTrack with the native .txt/.2dt files is now supported.
  • Note: the PFTrack .txt/.2dt files are resolution dependent and do not support much of the advanced features of the Load Markers tool.

Bug fixes

• (ab1c61d) Fix "node affects relationships" when calculating how Markers and Bundles affect each other.
• (621f8a5) Fix possible minor Solver UI marker bug.

Changes

• (#237) Change default marker group depth from 10 to 2 units from camera.
• (7f4aea6) Darken image plane file for Camera Calibration.
  • This is to allow the user to see the lines/locators on top of the image.

Developer Notes

• As a result of the Maya 2022 security preferences, a new Python module mmSolver.startup has been created which contains most of the functions in the userSetup.py file responsible for loading mmSolver components in previous releases. This new module should be called to load mmSolver components. For versions of Maya before Maya 2022 the userSetup.py is maintained for backwards compatibility, however the functions are deprecated.

Known Issues

• Documentation is not included in the Linux build of mmSolver for v0.3.16. The online documentation is available instead.
• As of v0.3.15 mmSolver is no longer supported on MacOS, and per-compiled versions are not provided.
• 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.