I'm implementing a collision detection scheme in Maya 2009 with PyMEL 0.9.2 which makes extensive use of getBoundingBox(). I'm running into some weirdness -- occasionally instead of returning a min and a max, getBoundingBox() returns two points which are both the average of the real min and max.
So instead of: [(1, 1, 1), (2, 2, 2)] I'll get: [(1.5, 1.5, 1.5), (1.5, 1.5, 1.5)] Sometimes this will cause getBoundingBox().intersects() to erroneously return False. When this happens and an intersection is missed, if I run a manual check, the bounding box comes back properly. This doesn't happen consistently, only after quite a few iterations, and only on objects I've just created. I'm only working with polyCubes at the moment. Has anyone else ever run into this? I don't see it in the issues list, did I find a bug? - Peter
-- http://groups.google.com/group/python_inside_maya
