Adverti horiz upsell

mr_motionTrail 1.3.0 for Maya (maya script)

A tool for managing motion trails and arc tracking.

License
Button download
1,662 Downloads

Compatibility

  • 2013, 2012

Operating Systems

  • Windows

History

Created:07/01/2012
Last Modified:07/12/2012
File Size: 29.8 KB

Bugs

Does not work entirely...

Statusclosed
Prioritymedium
Date07/09/2012
Submitted bygeoff3d geoff3d

So this is the error I get:

The "Current Trails" box doesn't get updated (is still empty) and obviously thickness and spacing markers etc are not updated.

// Error: line 1: setAttr: No object matches name: mr_motionTrail_pCube1_trailHandleShape.trailThickness //

# Error: CallbackError: file C:\Program Files\Autodesk\Maya2011\Python\lib\site-packages\pymel\internal\factories.py line 568: Error executing callback <function <lambda> at 0x00000000471817B8> - <lambda> - module mr_motionTrail - C:/Users/Geoff/Documents/maya/2011-x64/scripts\mr_motionTrail.py, line 136 - original message:

Traceback (most recent call last):

File "C:\Program Files\Autodesk\Maya2011\Python\lib\site-packages\pymel\internal\factories.py", line 566, in callback

res = origCallback( *newargs )

File "C:/Users/Geoff/Documents/maya/2011-x64/scripts\mr_motionTrail.py", line 138, in <lambda>

increment_field.getValue(), thickness_field.getValue(), xray_check.getValue(), spacing_check.getValue()))

File "C:/Users/Geoff/Documents/maya/2011-x64/scripts\mr_motionTrail.py", line 186, in prep_motion_trail

self.create_motion_trail(self.create_locator(ctrl), time_range[0], time_range[1], increment, thickness, xray, spacing)

File "C:/Users/Geoff/Documents/maya/2011-x64/scripts\mr_motionTrail.py", line 275, in create_motion_trail

mel.eval(cmd)

RuntimeError: Error occurred during execution of MEL script

line 1: setAttr: No object matches name: mr_motionTrail_pCube1_trailHandleShape.trailThickness # 

Comments on this bug:

  • kyleMR

    kyleMR said over 12 years ago:

    The current version of the script may not be compatible with the version of pyMel released with Maya 2011. The next update of the script should fix this problem.

Post a comment: