It’s point4, not sure where you got frgba…

In that case you most probably don’t want user properties but a different mechanism altogether

SetUserProp works on scene nodes, not on plugin instances. You can get the dependent node(s) with refs.dependentNodes

Just an observation, in 2019.1 it doesn’t seem there’s a significant difference between the two: Get values 0.015 sec Set zeroes 0.0 sec …

Hmmm, I only tested in 2019 but subobject level definitely doesn’t change here (modifier selection does, if some other modifiers are selected other th…

So the problem with the .NET solution is that it’s only available in newer versions of max? And the main problem of get+setCurrentObject pair is the f…

This migh be better: $.modifiers[1].enabled = not $.modifiers[1].enabled $.modifiers[1].name = random 1231 68465465 as string notifyNumSubObjs = ( …

I really don’t see anything better than just modPanel.setCurrentObject(modPanel.getCurrentObject())

It also adds the first modifier to current modifier selection and scrolls to that first modifier – btw. if shortened to sending only the two events, i…

Any reason not to do it this way? global Temp ( struct NestedStructDef ( owner, fn TestValue = print owner.MainStructValue …

Serejah: Should it work or this error is expected? Might be that older max versions need to have the lHit, lDir, wHit, wDir, str, rad assigned to…

And of course, the Painter Interface doesn’t do that: global startPos, prevEvent, currObj global lHit, lDir, wHit, wDir, str, rad manipulateMode = on…

Okay, so after digging through the SDK, I now know why the same mouseTool run separately vs during object creation behaves differently, there’s an add…

It’s a requirement.

Right, the first gif shows what happens when the action is initiated from the create panel. The idea with fake plugin sounds great but it seems the pl…