Announcement

Collapse
No announcement yet.

Vray literally not paying attention to enum/visibility

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Vray literally not paying attention to enum/visibility

    I've had numerous problems over the years with Vray simply ignoring things like animated visibility on objects, but this is a new one. I have two custom enum attributes driven with simple condition nodes to control and animate which flavor of an asset is visible, simply by returning a 0 or a 1 on a group node's visibility. This is animated in a couple of places in my scene.

    It works fine in the viewport, and works fine when playblasted. Vray is completely ignoring this when rendering, even when rendering to a single frame. If I scrub to a certain frame I can see Maya correctly switching the visibility in the viewport. When I render, it's as if the switch isn't happening.

    In other words, Vray simply isn't even rendering what's in my viewport. WTAF?

  • #2
    Originally posted by SonyBoy View Post
    I've had numerous problems over the years with Vray simply ignoring things like animated visibility on objects, but this is a new one. I have two custom enum attributes driven with simple condition nodes to control and animate which flavor of an asset is visible, simply by returning a 0 or a 1 on a group node's visibility. This is animated in a couple of places in my scene.
    I'm not sure if I did the setup correctly, so please confirm: Empty Group with Enum attribute (Box, Sphere, Cone) -> plugged into three Condition nodes (First Term; Second term adjusted based on Enum Attribute ID) -> plugged into the Visibility slot of each Shape. This way I don't see any issues while rendering, but have a feeling you are doing it in another way. Mind if you share a simple scene?

    Aleksandar Hadzhiev | chaos.com
    Chaos Support Representative | contact us

    Comment


    • #3
      Ive been finding more and more attributes that Vray wont render when animated. I made a new post about more I found today also. Im going to have to stop working this way and only use render layers for version / options for renders...(often the retoucher will want two or three versions of a render, or a car part, and its easier (sometimes) to just setup keyframes and animate the objects refraction for example and render three variations...now Im thinking it isnt a reliable workflow.
      Website
      https://mangobeard.com/
      Behance
      https://www.behance.net/seandunderdale

      Comment


      • #4
        Originally posted by hermit.crab View Post

        I'm not sure if I did the setup correctly, so please confirm: Empty Group with Enum attribute (Box, Sphere, Cone) -> plugged into three Condition nodes (First Term; Second term adjusted based on Enum Attribute ID) -> plugged into the Visibility slot of each Shape. This way I don't see any issues while rendering, but have a feeling you are doing it in another way. Mind if you share a simple scene?
        That is essentially how I had it set up, although Enum ID is connected to each condition node's First Term (Second Term is set to the Enum ID I want that condition to match to), and with the operation set to Equal and Color If True on red/X set to 1 and Color If False to 0, output is just the red/X value of the condition plugged into visibility of a group node or transform (not a shape node). I'm not able to reproduce at this point, but for some reason toggling the depth of field and motion blur back ON on the Vray camera I was using resolved the problem.
        Last edited by SonyBoy; 18-12-2024, 12:11 PM.

        Comment

        Working...
        X