Announcement

Collapse
No announcement yet.

VrayObjectProperties doesn't work with identical named objects

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

  • VrayObjectProperties doesn't work with identical named objects

    I have a scene where I wanted to switch one Object invisible while the other is still rendering but it kept showing up no matter what I tried.

    After breaking down the problem I figured out that the Object Properties don't work if the objects have identical names and shaders.

    This is my test Scene:





    The right plane has the Object Properties assigned and shouldn't be visible.

    If I assign the Object Properties to the left Plane (Inside the Group) they will both disappear.

    Is this just a limitation of Vray/Maya or can this be fixed in future updates?

    You can download my Scene here:

    https://www.dropbox.com/s/xvd6as3g10...003_eg.mb?dl=1

    Vray 3.30.01
    Maya 2016 Ext 1 SP 5
    Windows 7

  • #2
    Figured it out - both objects also have some render stats tweaked. If you re-enable cast shadows in the renderstats on both objects' shape nodes it will work, along with the other option to rename the objects, of course.
    Nevertheless, seams like something our developers should look into, but hopefully you can use the above as a workaround until we find out how to improve this.
    Last edited by yolov; 20-05-2016, 09:18 AM.
    Alex Yolov
    Product Manager
    V-Ray for Maya, Chaos Player
    www.chaos.com

    Comment


    • #3
      Thanks for the answer. I tried re-enabling the cast shadows and it solves the problem.
      I already renamed my objects to solve that but still wanted to inform you about it.

      This isn't a big problem but still something that can be very annoying if you don't know about that.

      Comment


      • #4
        Yes, I've already logged it to our system so our devs can have a look.
        Alex Yolov
        Product Manager
        V-Ray for Maya, Chaos Player
        www.chaos.com

        Comment


        • #5
          This is now fixed for the nightly builds.
          Alex Yolov
          Product Manager
          V-Ray for Maya, Chaos Player
          www.chaos.com

          Comment


          • #6
            I've literally spent 2 days running scripts and various thing to fix this issue on a large scene, so I second this. I was trying cycling through objects and assigning maxSubdivs etc using a script which should have been like 1 for loop. But I ended up having to rename almost all the shape and group nodes in the scene.
            It would be great if that wasn't the case. I can see why it makes sense to have unique shape names for a renderer but for a user where you have multiple reference to the same object to speed the process of modelling up, having to rename everything in a final layout scene is a pain. There are a few scripts online which you can cannibalise if you can work in MEL or Python. jh_findDuplicateNames.mel seems to work and if you want to do it more manually theres comentRename() but that does some weird naming to the shape nodes if you select the overall object and not the shape node itself.

            It would be good if maya or vray would use the whole node path or something in the shape node rather than just the last part, or if it told you when shape objects in multiple groups have the same name. It does it with top level objects, just not things in groups.
            Anyway I guess I've learned a lot about planning a scene which I didn't envisage being a problem at the start as a result (student) so I guess that is good.
            Maybe being a student I approached this is the wrong way either way, I thought I'd comment here anyway.

            Comment


            • #7
              Originally posted by yolov View Post
              This is now fixed for the nightly builds.
              Emm_Rouse, I guess you've missed the comment, just before yours.
              Unfortunately the fix is not in 3.40.02, but I'm sure it will land the next release from the 3.40 branch.
              V-Ray developer

              Comment


              • #8
                Hi yes sorry, it was more of an observation. My university hasnt updated Vray from the initial install and I figured other people might be in a similar situation so I posted some solutions.
                Hope thats alright.

                Comment


                • #9
                  This issue will be fixed for the next release. In fact, it's already fixed in the nightly stable builds.
                  V-Ray for Maya dev team lead

                  Comment

                  Working...
                  X