Announcement

Collapse
No announcement yet.

V-Ray Next Update 2 DR broken

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

  • V-Ray Next Update 2 DR broken

    So Ive been testing 3ds max 2020 and had found it to be as stable as expected and running ok until I've deployed it across my render farm and of course something has to crap out...

    When trying to use DR on a scene with 4 of my render slaves it will only render with two slaves at a time and the other two sit idle with the message window saying "Released because there is no pending work" and this is all right at the start with barely 10% of the render complete. I then tried a test where I saved the file as a 2018 version and opened and rendered that and it worked as expected with all 4 render slaves taking part in the render...

    I did email support (ticket-136-430-097 but thought I would drop a question here too, to see if others are having the same or similar problems.

    Current versions on all machines - Win 10 | 3dsmax 2020.1 | V-Ray 42001 - Update 2.1 (4.20.01.00001) | Phoenix 3.14.00 Build:20190427 | Forest 621

    -dave
    Cheers,
    -dave
    ■ ASUS ROG STRIX X399-E - 1950X ■ ASUS ROG STRIX X399-E - 2990WX ■ ASUS PRIME X399 - 2990WX ■ GIGABYTE AORUS X399 - 2990WX ■ ASUS Maximus Extreme XI with i9-9900k ■

  • #2
    Hello,

    Originally posted by Syclone1 View Post
    I then tried a test where I saved the file as a 2018 version and opened and rendered that and it worked as expected with all 4 render slaves taking part in the render...
    Is it possible that for some reason 2 of the slaves started V-Ray for 3ds Max 2018 spawner instead of the one for 2020? That would explain all of them rendering the 2018 scene.

    If that is not the case - can you run a render of the problem scene and then attach the v-ray logs from your workstation and one of the problem slaves? (vraylog.txtand VRSpawner.log).

    Best regards,
    Yavor

    Yavor Rubenov
    V-Ray for 3ds Max developer

    Comment


    • #3
      All of the slaves were running exclusively the 2020 spawner as I currently have to manually start and stop the services on each of the DR slaves.

      I did provide the scene, where exactly are the log files? Ill fire up a render now and grab logs from everything. I did provide the scene too in the original email to support.
      Cheers,
      -dave
      ■ ASUS ROG STRIX X399-E - 1950X ■ ASUS ROG STRIX X399-E - 2990WX ■ ASUS PRIME X399 - 2990WX ■ GIGABYTE AORUS X399 - 2990WX ■ ASUS Maximus Extreme XI with i9-9900k ■

      Comment


      • #4
        well that figures, I have been trying to get my 5th render slave online and finally did so I re-opened the scene I was running last night and added all 5 slaves (excluding the host) and its rendering fine now... Of course lol. **Bangs head on desk**

        Ill see how the day goes and if I can find the logs and still have a problem Ill reply to the post and or support... Thanks for the fast response this morning Yavor, its always appreciated

        Cheers,
        -dave
        Cheers,
        -dave
        ■ ASUS ROG STRIX X399-E - 1950X ■ ASUS ROG STRIX X399-E - 2990WX ■ ASUS PRIME X399 - 2990WX ■ GIGABYTE AORUS X399 - 2990WX ■ ASUS Maximus Extreme XI with i9-9900k ■

        Comment


        • #5
          Glad to hear that it is working now but if you see a problem again - send the logs. They should be located in the temp folder on the machines - you can open Windows Explorer and type %temp% in the address bar - that will get you to the right place. The V-Ray log is called vraylog.txt and it should be present on both the workstation and the slave machines. The spawner log should be in the temp folder of the render slaves and is called VRSpawner.log

          Yavor Rubenov
          V-Ray for 3ds Max developer

          Comment

          Working...
          X