Kickflipkid687: Glad u got it sorted. Actually the first issue is not sorted out yet.

What I want to in the mzp.run is always execute a ms file which contains an installer struct. I will then have a run and drop command that will start …

Ok I found the solution to the second issue. It’s a matter of supplying exactly the right format it seems: run directory/file.ms –does not do anythi…

Yes. Although in the other methods the number of materials is implicit. The loop “for m in meditmaterials” operates on all materials in that collectio…

Oh that’s some interesting results! I had not thought the getnodebyname function would even be close to that fast. Also nice to know that setting prop…

lo: Nifty benchmarker you got there Hehe, nice isn’t it I use it quite a lot and I find it very useful. So nice work on that!

I was curious about the performance of these 3 alternatives, so I did a quick benchmark: Output for 1000 iterations: Method A: Time: 18.611 Seconds, …

How about this for a start? ( for o in objects do ( for m in meditmaterials do if m.name == o.name do o.material = m ) ) or an alternative a…

lo: define you action as a macroscript and find away to automatically assign it to a hotkey For the latter part, have a look at either: for a m…

Thanks for the heads up. That is an annoying little problem indeed… I have often wondered whether it would be fair to blame the Autodesk people for is…

Thanks for reminding me about the NodeEventCallback! The reason I am using the general event is to be able to support max2008, and partially for ‘hist…

Ah yeah if max uses single precision floats then definitely use a float array. Use the minimal size data type possible without losing precision.

Nice. Another thing that might improve performance is replacing the Point3D by a float or double array. Then if you really need the Point3D class in y…