Skip to content

mayaMatchMoveSolver-v0.3.1

Compare
Choose a tag to compare
@david-cattermole david-cattermole released this 27 Oct 11:16
· 3176 commits to master since this release

Release v0.3.1 is a bug fix release, with a few new features aimed at improving Marker copy/pasting from 3DEqualizer and copying Maya camera data into 3DEqualizer.

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

New features

  • #38 - Added ability to load distorted and undistorted 2D Data with UV Track format (v3).

  • #37 - Updated copy/export Tracks 3DEqualizer tool with compatibility for #38.

  • #15 - Added a default Hotkey Set for Maya 2016+, and added a Hotkey Set Switcher to the shelf. The module (.mod) file now contains a new environment variable MMSOLVER_CREATE_HOTKEY_SET, to control the auto-creation of this hotkey-set. Hotkeys:

    • a key = Hold down and left-mouse-click to activate the mmSolver Marking Menu.
    • c key = Center 2D on Selected
    • z key = Zoom / Pan tool (the same one with Maya)
    • m key = Swap Marker / Bundle Selection
    • n key = Select both Markers and Bundles
  • #105 - Added "Load Mode" to Load Markers tool, allowing to create new markers, or replace selected Markers with 2D data from 3DEqualizer.

  • #126 - Added Copy Camera tool, in Maya, and a Paste tool in 3DEqualizer.

  • #125 - Adjusted the transform utility module for better transform value decomposing and querying, for control over rotation order.

  • Added 'Marker/Bundle rename with metadata', to auto-rename nodes using custom attributes stored on the nodes.

Minor Changes

  • Added utility function to get image planes.
  • Changed Solver UI to show Frame Deviation by default.

Bug Fixes

  • Changed Smooth Keyframes tool to undo all keyframes in a single CTRL+Z.
  • Get image size from coverage attr of image plane, not camera.
  • Add missing BUILD_* flags to cmake, to allow fast copying of Python files during development.
  • Make usage of Qt.py to be compatible with v1.1.0.b7, for Solver UI.
  • mmSolver.utils.camera.get_camera incorrectly considered a default primitive sphere to be camera.

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