Actually what drives the visibility is a Custom Attribute. Here we used an EmptyModifier to hold it as the OP used it too, but you can attach it to an…

The callback needs to validate objects. fn visibilityFilter node = (not node.visibility) registerDisplayFilterCallback visibilityFilter “Visibility” …

Well, if you code a paradox you end up with an infinite loop. Your example is one case, but there are others. For instance, simply go to the display…

I think it is “safer” too, somehow. And you can code it with to work with a modifier, if preferred.

The Rendering radio buttons simply unhide all the objects when se to “Enable in Renderer”, so when you render an animation they will be all unhidden b…

I don’t get any error from Max 2014 to 2021, however hiding/unhiding the nodes this way may lead to instability. I tried animating 1500 objects in vi…

Here is another approach using .isHidden and node visibility, which should allow you to do hide/unhide objects y viewports and when rendering. You ne…

Yes, it has all the disadvantages of a geometry modifier.

Of course it won’t be faster than hiding the object, in best case it will perform the same, but the difference is that it works. While this topic has…

In Max 2016+ you could do something like this. Not perfect but seems to work and since it is not a “hack” I see no drawbacks using it. plugin SimpleM…

“Made proudly by Shakuro”

If the pivot points will be as in these images and not as in the image of the first post, then the solution may be far easier. ( delete objects …

This takes just 188ms for 500K items in an unsorted array, which in my opinion is pretty fast. ( fn FindStringInArray arr str = ( str += “*” co…

In order to use bsearch() you first need to sort the array, and that will be a killer, moreover if you use qsort(). I don’t think this is a good case…

This may also work. If so, it should be easier to work with and you also would get access to events. ( NotifyIcon = dotnetobject “System.Windows.F…