Skip to content

mayaMatchMoveSolver-v0.2.1
Compare
Choose a tag to compare
@david-cattermole david-cattermole released this 13 Apr 13:25
· 3745 commits to master since this release
v0.2.1
de6d31e

This is a bug fix release addressing a number of issues in v0.2.0. A small number of minor features were also added. See the below list.

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

Note: (Changed in v0.2.1 compared to v0.2.0) The per-compiled archives include Qt.py 1.1.0. If you already have Qt.py installed, remove the previous version.

New

  • Added SynthEyes exporter script (see INSTALL.md for installation details); #46.
  • Added Toggle Marker Lock State tool.
  • Right-click menu for Solver UI shelf icon, allowing to run the solver without opening the Solver UI.

Changes

  • Opening a UI that is already open will bring focus to the window.

Bug fixes and Improvements

  • Fixed #78; Display of Solver Error value; The displayed solver error value was rounded to the nearest integer.
  • Fixed #49; Solver UI opening multiple windows. Only one Solver UI window will be created.
  • Fixed #60; Debug Logs being written into the home directory.
  • Fixed #84; Maya selection being changed when the Solver UI receives focus.
  • Fixed #90; Smooth Keyframes tool was incorrectly smoothing negative numbers.
  • Fixed #85; Clashing node names created by Marker/Bundle Rename tool.
  • Fixed #81; The weight and enable Marker attribute keyframes were not shown in the Timeline.
  • Fixed #89; Marker Bundle node selection toggling is now more consistent when other objects are also selected.
  • Fixed #82; Ray-Cast Markers tool, it would raycast behind the camera.
  • Fixed a small problem reading malformed 3DEqualizer track .txt files.
  • Improved #88; Better Qt integration for PyQt and PySide.
  • Repeatedly clicking "Center 2D" tool will not try to reload mmSolver (performance bug).
  • Lock Bundle transform "Shear" attributes to avoid strange values being added.

Known issues

  • New v0.2.x 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.
  • 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. The root cause is being investigated.
  • The Solver does not find the absolute minimum and sometimes requires pressing "solve" multiple times to get a minimum error.

For Developers

  • Updated to Qt.py v1.1.0; for Qt.QtCompat.warpInstance usage; #88.
  • Preferred Qt binding changed to PySide/PySide2 over PyQt.
  • Started adding support for nicer printing of API classes (Marker and Bundle are currently added); #19.
  • Changed an occurrence of "nullptr" to "NULL" for c++0x compatibility (for gcc 4.4.7 / CentOS 6.x).
  • Progress made on #60; turn on debug mode with "MMSOLVER_DEBUG = 1" for solver testing.
  • Configuration environment variable MMSOLVER_CONFIG_DIR added, but not currently used (added prematurely for #17).
Assets 10
Loading