Hi Offer,

Sorry for neglecting your post, somehow I missed it. The way to call a .NET function from MaxScript is outlined here:

http://www.ephere.com/autodesk/max/docs/987.html

I would pass a node using its handle (in MXS: MyFunction( myNode.Handle ) ). The .NET function would take an int and then I'd use IGlobal.COREInterface.GetINodeByHandle( handle ) to get the node. Getting other objects (i.e. a controller) could be a bit trickier, I would do it using an anim. handle but I'm not sure if you can get a node's anim handle from MaxScript.

Returning a value back to MaxScript should be trivial by specifying the .NET function's return value.

Marsel Khadiyev (Software Developer, EPHERE Inc.)

Right, unfortunately workarounds is probably the best approach. I've been dealing with MaxScript exposure in C++ a lot previously and it is just as involved/painful and also seems to be on its way out. I am considering of excluding MXS namespace/classes from Max.NET in near future as they take up (largely unused) space.

Return values would need to be handled same as parameters. I just opened MXS reference and I see that there actuall is a way to get objects by anim handle, which makes everything much easier:

In .NET: UIntPtr myHandle = global.Animatable.GetHandleByAnim( myMaterial or anything else );
In MXS: myMaterial = GetAnimByHandle myHandle

Haven't actually tried it, but should work theoretically.

Marsel Khadiyev (Software Developer, EPHERE Inc.)