I ran into a very similar problem with MFnMesh:: getPointAtUV a few months ago.
The solution in my case was to use the MDagPath constructor instead of the MObject one for your MFn* class. Apparently, functions that require a dag path won't actually return an error if you used the other constructor to build your MFn* object. They just fail silently. I logged a bug for the getPointAtUV issue. If this turns out to be a similar thing, I think you should log it. Autodesk needs to know how painful this is for customers. Maya's API should either return an error, or use the first path to an object under the covers. In fact, pretty much anything other than failing silently would have been nice. Sivanny -- 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/d0a81d6f-3266-4885-9e62-f2c15e74076b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
