Hi guys , normally by design the closest point value returned by the intersector is in object space http://help.autodesk.com/view/MAYAUL/2017/ENU/?guid=__cpp_ref_closest_point_cmd_2closest_point_cmd_8cpp_example_html
in the function closestPointCmd::createDisplay( MPointOnMesh <http://help.autodesk.com/cloudhelp/2017/ENU/Maya-SDK/cpp_ref/class_m_point_on_mesh.html>& info, MMatrix <http://help.autodesk.com/cloudhelp/2017/ENU/Maya-SDK/cpp_ref/class_m_matrix.html>& matrix ) we go from local to worldspace by applying the mesh parent transform ( and its what is used as well for the matrix initialization.) is quite horrible that they labelled a local point as world point though.. i would as well stay as far as possible from the OpenMaya 2 layer if i can as you will soon see some hidden bugs and only 30 percent of the function are exposed ( dont concern yourself with pythonic argument as you will need to convert your code to c++ if your are serious about your work) Le jeudi 2 août 2018 15:34:56 UTC-4, Luiz Amaral a écrit : > > OK I’m out of ideas now :/ -- 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 python_inside_maya+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/7aed4d19-7f93-415d-8f83-50a98dad7f4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
