Hi, I don't necessarily agree with the idea that an increase in cpu usage dictates a performance increase in your node. Low cpu usage doesn't mean your node or code is slow. cpu usage is not a very good way to gauge the performance. Even frame rates would be better, but the profiler would be ideal.
are you using parallel evaluation? I would think the hit you're taking is not in retrieving an MMatrix, but rather in the MItGeometry iterator being created for you. You also don't have to use the deform() method, and can do your deformation within the compute. You're also using the inputValue, which could also cause everything upstream to be recomputed. I think it's pretty common to use outputValue from within the deform method. goodluck! -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/322f1b59-7bb6-4e67-b76c-2c4c16f69295%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
