Announcement

Collapse
No announcement yet.

Distributed Render with Phoenix 3.0.2 looks different on local vs remote machines

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

  • Distributed Render with Phoenix 3.0.2 looks different on local vs remote machines

    I installed the latest update on all three machines and re-rendered my scene with DR enabled on all.

    I was about to post images but Max has now frozen completely.

    EDIT: OK after killing the process it's working again.

    So here is the image with all three machines DR rendering. This model has a falloff map on him, no bitmap materials at all. The output cache and input cache are the same UNC path \\......\hgdtt####.aur

    Click image for larger version

Name:	phoenix-all.jpg
Views:	1
Size:	230.5 KB
ID:	886707

    The darker, spottier frames are from my local buckets and the smoother ones are from the remote machines.

    If I only enable the local host in DR, or disable DR altogether, I get this:

    Click image for larger version

Name:	phoenix-nodr.jpg
Views:	1
Size:	217.4 KB
ID:	886708

    And finally with only remote DR, disabling local host, it comes out like this (which is what I expected in the first place):

    Click image for larger version

Name:	phoenix-remote.jpg
Views:	1
Size:	228.2 KB
ID:	886709

    I haven't changed V-Ray, only updated Phoenix so I don't know what's to blame.
    Last edited by elyptic; 16-01-2017, 12:23 PM.

  • #2
    Click image for larger version

Name:	phoenix-all2.jpg
Views:	1
Size:	224.6 KB
ID:	866199To add to the confusion, each time I render without any changes I get something new.

    Comment


    • #3
      I would check the installs on the slaves. Many times I get vray/phoenix not installing correctly... I normally run the install twice on the render farm
      Adam Trowers

      Comment


      • #4
        I could try that but the DR servers are actually the ones doing it properly, though I suppose I could reinstall the local one again. Will try later today.

        Comment


        • #5
          Also,could you share the V-Ray version you are using? If you are on 3.5, could you check if disabling Adaptive lights would fix it? Are you rendering in Point mode of the Particle Shader?
          Svetlin Nikolov, Ex Phoenix team lead

          Comment


          • #6
            I am using latest production versions of both, and point mode of the particle shader. I've given up on this and went back to a fluid sim which is giving me a whole different set of problems, will likely post about it if I can't work it out by the end of the night.

            Comment


            • #7
              The solution to this problem was re-installing PhoenixFD 3.00.2 on my local machine, making sure to stop the VRaySpawner / VRayRTSpawner services while installing, and making those processes were using my personal user account instead of the system's. As it turns out, one of the shader dlls was not firing at all on my local machine, hence the difference in renders. Now I'm getting all buckets properly.

              Comment


              • #8
                Thanks for the heads up!
                Svetlin Nikolov, Ex Phoenix team lead

                Comment

                Working...
                X