1. Home
  2. Docs
  3. renderStacks
  4. Pass Modifier | Pmodifier
  5. [Vi] Visibility

[Vi] Visibility

[Vi] Visibility – 1 per pass

Visibility pmodifier hide/unhide objects per pass. This is the pmodifier that you need to use to define what to render!

Check the Object Selection section for details of how to use this UI.

When you use LayerSet, Nested LayerSet, Layer, Nested Layer for Visibility pmodifier. renderStacks turn on/off the selected layers not individual objects. This certainly make hide/unhide faster and reliable.

When renderStacks hide layer, it will just hide the layer. When layer is set to hidden, all object in that layer will be hide in anyway. There is no reason to worry if each object is set to hidden or not.

But, when renderStacks unhide objects by one of layer methods, it will make sure to unhide all the object in that layers. Again, if you use layer set to unhide objects, all objects in the layers will be automatically unbidden.

Using Layer Set or Nested Layer Set is the recommended workflow for renderStacks. If you use Layer Sets, you don’t have to manage each individual objects, you just need to make sure to put object in the correct layers. This is easiest, fastest and most reliable way to hide/unhide objects.

renderStacks also take care all nested hierarchy behavior for you. For example, When you have a nested layer and a higher level of layer is turned off, all descendant layers of that layer will be turned off. Therefore, you are suppose to make sure to include all ancestor layers for a layer set hen you make a layer set for Visibility pmodifier. But, that’s kinda annoying and would still cause problem when you change the hierarchy of layers. So, I decided to take care those ancestor layers automatically. You just need to choose the exact layers you want to show. renderStacks will take cares everything else!