Announcement

Collapse
No announcement yet.

Vray for Rhino - Cannot render to ANY of my slaves in DR -

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

  • Vray for Rhino - Cannot render to ANY of my slaves in DR -

    I've been rendering to 4 machines for a while without problems.
    Today suddenly I get this
    Starting DR 0
    dr host: 192.168.0.16:20211
    dr host: 169.254.62.210:20211
    dr host: 192.168.0.15:20211
    dr host: 192.168.0.10:20211
    dr host: 192.168.0.35:20211
    Host 192.168.0.16:20211 added to waiting list
    Host 169.254.62.210:20211 added to waiting list
    Host 192.168.0.15:20211 added to waiting list
    Host 192.168.0.10:20211 added to waiting list
    Host 192.168.0.35:20211 added to waiting list
    Could not use any of the selected (5) hosts for distributed rendering! <

    I checked the firewall, I re-installed the spawners even I re-installed vray in the server machine. Nothing.
    An also get random crashes .
    I'm running the latest service packs on both Rhino and vray
    I ran out of ideas ...
    Please help

  • #2
    Please, email support@chaosgroup.com
    they will help you.

    Comment


    • #3
      Thank you. I will.

      Comment


      • #4
        I happens often,usually what I do is wait a few minutes,or close the drawing and reopen again,and all is good.

        Comment


        • #5
          Actually it never happened to me before. But I discovered since last night that when Rhino crashes while rendering, the license server process goes somehow to limbo so if I kill it in task manager and start it again, DR works fine again and all the machines are back to rendering. However, a separate issue is that Rhino keeps crashing randomly when using DR. I haven't been able to figure out why.
          If I disable DR I can render fine ...

          Comment


          • #6
            We seems to have exactly the same problem.I did not find a solution.what I do and sometimes it works,is start the rendering,and when the light cache is done,I then start the drit seems to help but not always

            Comment


            • #7
              So far this morning has been fine after wasting a whole day yesterday ... go figure.
              I find VR for Rhino still very buggy even after the latest update. I still have at least 4 or 5 times a day freezes mostly related to the material manager. The whole panel goes gray and I have to restart rhino and check the task manager for Rhino instances that sometimes remain in memory. The freezes seem to happen randomly but mostly when I change a materiel or access the texture dialog but definitely almost always while in the materials manager. The think is that Rhino still works and I'm able to save but the materials manager and often the options panel becomes unresponsive and I cannot close it.

              Comment


              • #8
                Hi
                The material freeze is due the V-Ray GUI license.

                After a certain amount of inactivity with the main editor windows, the V-Ray GUI license experiences a timeout.

                To fix this issue, you'll have to edit the V-Ray for Rhino .ini file located:
                C:\ProgramData\ASGVIS\V-Ray For Rhino.ini

                Please note this is a hidden folder.

                If you open that file in any text editor and scroll to the
                [Licensing]
                gui_timeout_minutes=5

                and change the value to
                [Licensing]
                gui_timeout_minutes=-1

                Save the file then restart Rhino if it is open, and that should resolve the issue.

                Thank you,

                Comment


                • #9
                  Is this a bug and hasn't been fixed yet, or is it by design ?
                  If by design, I find the setting really silly (pardon me), why would you do that? Or at least it should be properly documented or have an option in the interface to change it. This problem has been driving me and many other users absolutely nuts.
                  Thank you anyway, you made my day if this fixes it !

                  Comment


                  • #10
                    Hi Juan
                    That was designed like that. If you lock at your dongle license, you will found two licenses. One is the GUI license (interface) and the other is the render license. The idea is that two users can work with V-Ray at the same time. One could be using the UI license to work with materials and setting, while the other is rendering. That is why after couple minutes without using the UI everything get grayout (the UI license is free to be use for the other user). However, you should be able to unlock the license very quick when you start using the UI again. So, if you have a permanent lock, this is a bug. In V-Ray 3.0 we are going to have a different approach.

                    Comment


                    • #11
                      By permanent lock you mean the dongle? That's what I have, so I guess it's a bug?
                      So if I just work by myself, the solution you gave me earlier is then the way to go?
                      BTW any hints of when v3 will be ready ?

                      Comment


                      • #12
                        Originally posted by fpedrogo View Post
                        If you lock at your dongle license, you will found two licenses.
                        Where is the dongle license?
                        I see a license_vrlservice.rtf under program files /Chaos group/VRLservice/c64/docs but is just a generic license document about the dongle I don't see reference to the two licenses ....

                        Comment


                        • #13
                          By permanent lock you mean the dongle? That's what I have, so I guess it's a bug?
                          I meant if Rhino get lock and you are not able to unlock the V-Ray UI. Then ys, it is a bug
                          So if I just work by myself, the solution you gave me earlier is then the way to go?
                          Yes.
                          BTW any hints of when v3 will be ready ?
                          Unfortunately, we don't have a date yet. What I could tell you is that we already have a lot of features.

                          Comment


                          • #14
                            You have to open the internet browser and type: localhost:30304
                            then click on: Get status of the server

                            Comment


                            • #15
                              Looking forward to Vray 3 ... I hope dag and drop materials is finally there
                              Thanks again Fernando

                              Comment

                              Working...
                              X