Those are node-specific properties that are only related to how it will be displayed in the viewport, and it’s explained quite well in the docs.

Sure, this was the case in max 2, basically very little changed in this area since max 4.

Because getVertColor is a method that predates meshop methods, back then mapchannels were supposed to do one thing and there were only two mapping ch…

What’s so complicated about (result * 255) as color and (color / 255) as point3?

Sure, just use meshop.get/setMapVert instead.

That’s the complete list. I guess you could crawl the SDK but what use would that be anyway?

There are also scripted controllers, simpleMeshMod and simpleSpline.

See above. In prior versions, you could do something like that by storing custom attributes and using their rollout. Anyway, if you can’t think of a w…

Create a that parameter just like any other and feed it for example (refs.dependsOn (Box()).baseObject)[1]

Think of it as a container of the individual parameters that allows you to easily store and retrieve them, get their types, controllers etc. This is t…

windows.getChildHWND 0 cmdPanelName This is wrong, don’t do this, if there is more than one max instance open, it will always give you the handle to …

Isn’t there also the issue that the floating command panel is identified by its text, which is different in various max localizations?

No idea who’s in charge of MCG (Autodesk is not exactly transparent, who can name the current 3ds max Product manager off the top of their head, for e…

To tell the truth, that sounds extremely complicated and error prone (plus MCG operations are faster on MCG triMesh, you have to create that from max …

Also when deciding, take into account the cost of immutability when operating on any moderately complex type like a mesh – i.e. every MCG node that do…