Skip to content

mayaMatchMoveSolver-v0.3.11
Compare
Choose a tag to compare
@david-cattermole david-cattermole released this 15 Dec 01:00
· 2629 commits to master since this release
v0.3.11
61ef910

Release v0.3.11 adds a few useful tools, and fixes some bugs.

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

New Features

  • Project Markers on Mesh UI
    • (#177) Projection on a frame range (animated, multiple frames)
    • (#179) Display Layers are checked for visibility on meshes.
    • (#178) Uses smooth-preview mesh, if enabled on a mesh to be projected on.
  • (#128) Add support for rolling shutter correction with Marker (2D Tracks) export from 3DEqualizer. documentation
    • Download the scripts on 3DEqualizer ScriptDB here and here
  • (#180) - Add a "Special Thanks" credits to the About window, and documentation.

Changes

  • An option box has been added for the Smooth Keyframes UI - documentation

Bug Fixes

  • (#165) Attribute nodes with identical Maya UUIDs are now correctly added into the Solver UI.
  • (#182) Bug fix for Paste Camera (in 3DEqualizer)

For Developers

  • (#165) mmSolver.api.Attribute.get_node() was fixed to return the correct node name when there are duplicate UUIDs in a Maya scene.
  • Added Option Box configuration options for the (dynamic) shelf and menu creation.

Known Issues

  • 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
    • 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.
Assets 12
Loading