Hi all. Nice to see some responses. Late hours, hehe. Late, tsk, it’s only 02 here, that is nothing…(ehm, friday night though) I found one flaw with…

Ok this function is pretty fast if you don’t use it too often: polyOp.getVertsUsingFace $ #{1} So it’s easy to get all the vertices, I think I need …

Hmm, this is way too common in max. They have a great idea, develop it to 50% and then leave it. I have found ok ways to work with visual maxscript. W…

Myself I normally do this Write the rollout text in a ms file then you right click the code and click Edit rollout. The rollout will now open in visu…

remember that you can write classof($.baseObject) or classof$.modifiers[1]) to get the types of different levels. You don’t always want the top type. …

Here are some examples of mini syntax. Normally I think only one line is needed. polyOp.moveVert $ #{1…7} [0,0,1] One thing that often has pretty co…

I think the syntax is pretty good. Perhaps they should add some checking for the type of the variables. I mean, ARRGG, the amounts of bug you can intr…

I have programmed quite a bit in c++. For my PolySpeed plugin I do most of the programming in maxScript. I think maxScript is very nice for quickly wh…

Osamu, I think this example from the help files show pretty clearly why it’s good to know maxScript. $*.material = undefined This _single line of co…

Yes, it’s possible. Check out the dynamicRollouts.ms (i think it’s called that). it’s somewhere in the max folder, in the UI/MacroScripts I think do …

Arg, I lost my length post. Anyway, you are right no problem. Have you experimented with writing multi functions that work for both mesh/polys etc? M…

Yea, the loop mode is cool, it should be possible to use tools like this for alot of things. One thing I really miss in max is that you can’t know if…