maybe im understanding this wrong, but translateBy seems to need a vector based on local space not world (which i think is what the example code is doing?) so i tried with settranslate: http://pastebin.com/JWyJ9Cfb
@10000 time for xform, poly: 0:00:00.444000 time for xform, surface: 0:00:00.429000 time for setAttr, poly: 0:00:00.263000 time for setAttr, surface: 0:00:00.260000 time for API, poly: 0:00:00.133000 time for API, surface: 0:00:00.122000 @100000 time for xform, poly: 0:00:04.557000 time for xform, surface: 0:00:04.509000 time for setAttr, poly: 0:00:04.207000 time for setAttr, surface: 0:00:04.175000 time for API, poly: 0:00:01.221000 time for API, surface: 0:00:01.238000 Thanks manuel and vux! looks like surface is a tiny bit faster, but with the api it seems negligable On Thu, Apr 11, 2013 at 2:41 PM, vux <[email protected]> wrote: > The fasted way in scripting is api2 MFnTRansform.translateBy > > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
