Could you extend the camera object with a custom oldName attribute into which you can put the current name? When the event is called you can then que…

I wonder if it would be quicker to grab the UVs directly from the mesh faces and process that way… Or, given that they’re lod meshes and are likely t…

Have you tried using the on <param> set <arg> do () and on <param> get <arg> do ( <arg> ) handlers within your param blo…

Nice optimisation

A method to do it without array and sorting etc: fn getClosestVertToPoint theNode thePoint selectVert:false = ( if classOf theNode == Editable_Mesh …

You need to convert the mesh vert array first to a bit array, then you can chnage it to an array if you need to: ($‘Your Object Name’.mesh.selectedVe…

You could try using: $‘Your Object Name’.mesh.selectedVerts as bitarray which should return a bit array of the verts selected with the modifier.

Yes, that’s pretty much what I use them for… the new AssertReporter stuff in 2012 is also pretty useful. Much nicer than lot’s of print statements e…

Full Documentation of the assert functions are here: Assert Functions Hope that helps

Have you considered using the assert systems?

This could be caused because your scripted plugin might have a dependency on something in Max and is being run before Max’s own systems have fully loa…

Yes, it sees the same problem that the points aren’t ‘normalized’ along the length of the curve. Really what I’d like to find out is the method for s…

That will only tell you where the Z_Axis of the object is pointing, and due to floating point errors won’t always work. A tiny variance in the vector…

You could probably use the dot product of the two vectors to work it out: dot <Point3> [0,0,1] where <Point3> is the point3 vector of th…