Announcement

Collapse
No announcement yet.

Proxies not rendering on Windows 10 Machine

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

  • Proxies not rendering on Windows 10 Machine

    We have recently installed win 10 on a few new workstation and are have problems when they render network jobs. It seems that Vray proxies are not rendering, but it is not on all frames. For instance - we are rendering a train station arrival hall animation and the first couple of frames that the win 10 machines render include the proxies, and then at some point the proxies stop rendering. All other computers render the proxies fine and the win10 computers also render the proxies fine when local rendering - just not when rendering a network job.

    Our existing environment is Win7 64 - Max 2016 - Vray 3.50.04
    The workstations that have problems rendering proxies are Win10 - Max 2016 - Vray 3.50.04

    Anyone experienced anything similar?

  • #2
    Do you get any errors in the logs ? Are they physically missing from the shot or they render black? Which render manager do you use?
    Zdravko Keremidchiev | chaos.com
    Chaos Support Representative | contact us

    Comment


    • #3
      Hi Zdravko,

      We are using RP manager to send the jobs and backburner. They are actually missing - not rendering black. I didn't check the Vray message window while they were rendering but I can do that tonight. The files also saved out fine - everything else was the same just no proxies were visible.

      Comment


      • #4
        Hi Zdravko, I sent the file in question again last night to the WIN10 machines and found that it rendered the first frame fine, and the second frame the proxies were not rendered. The strange thing is that I was watching the Vray message window while it was loading / rendering and it reported successful loading of the proxies. Just to note - all proxies didn't render and they are located in separate xrefs.

        Comment


        • #5
          Hi Zdravko,

          I have done some more troubleshooting on this issue - it seems that a simple scene with proxies works fine. Even if the proxies are in an xrefed file. When the scenes are more complex we are still having this issue of proxies not loading. This seems like it is something with our environment as no one else is reporting this issue. Can you make any suggestions on how to troubleshoot this further?
          Is it the case that upon rendering vray loads the proxy directly from the network path into RAM? It doesn't cache it locally?

          Any ideas would be appreciated.

          Comment


          • #6
            I've seen something similar to this recently.

            I found collapsing objects helped. once I dropped the total amount of different objects, the issue wasn't as bad. but it still happened.

            I'm running a mix of win7 and win10.

            I hadn't really thought about that. but i think it was only the win10 pc's that issues.

            Comment


            • #7
              We found the problem and as I suspected it was not a Vray issue.

              We are using windows server with Group Policies to map network drives to the workstations. It turns out that when using group policies, by default every 90 minutes or so windows refreshes the group policy - in our case that means remapping the network drives. While on Win7 this hasn't been a major issue, under windows 10 it cases a temporary network outage, which in turn i think has been causes some crashes, and I am certain has also caused problems when rendering. I am guessing that while vray is loading proxies over the network we get the dropout and then it fails loading proxies but continues with the render.

              The solution is to edit the group policy settings on the win server and tell windows not to run the policy every 90 minutes. Actually we turned it off so that it only runs on logon. There are other solutions online so if anyone is having a similar problem search for - Win 10 group policy mapped network drive issues or check out this spiceworks link : https://community.spiceworks.com/top...-drives?page=1.

              Our Win 10 machines are now running more stable and are rendering as expected without any assets missing.

              chris - are you using group policies? If so perhaps try modify them like we did. I think it has actually made our whole environment more stable.

              Comment


              • #8
                I will have to look into the server settings.

                though I was running UNC naming. so I'm not sure this was the issue.

                This only seemed to be an issue with animation and not stills. I may have just been overloading server/switch.

                Comment


                • #9
                  I've been troubleshooting some Backburner problems lately that started with Creators Update on W10. I'm seeing a lot of event viewer logs being sent to me with errors about refusing IP assignments, duplicate server and computer names on the network, and DNS issues. Google shows some problems with other applications as well. I haven't nailed down what is happening yet, but I wonder if the problem machines all have the Creator's Update. For some people it doesn't cause much of a problem, and for some they can't render a full job. I hadn't thought to ask about UNC pathing, that might actually be the difference between the two.
                  Last edited by Deflaminis; 20-07-2017, 09:29 AM.

                  Comment


                  • #10
                    Originally posted by Deflaminis View Post
                    I've been troubleshooting some Backburner problems lately that started with Creators Update on W10. I'm seeing a lot of event viewer logs being sent to me with errors about refusing IP assignments, duplicate server and computer namess on the network, and DNS issues. Google shows some problems with other applications as well. I haven't nailed down what is happening yet, but I wonder if the problem machines all have the Creator's Update. For some people it doesn't cause much of a problem, and for some they can't render a full job. I hadn't thought to ask about UNC pathing, that might actually be the difference between the two.
                    We know for sure that the Creators Update can stop the VRLService which is needed in order for the V-Ray Online license server to be available and running. If you just simply re-install the V-Ray license server, it will fix if any V-Ray licensing issues appear. Regarding the Backburner issues, can you please provide us with more details and are you able to render with V--Ray without using Backburner? Is it possible to send us some screenshots if any errors appear? How many machines are you using and on how many on them issues appear?
                    Also could you please contact your local IT Administrator in order to help you out with the issues mentioned regarding "errors about refusing IP assignments, duplicate server and computer namess on the network, and DNS issues"
                    Stefan Isakov

                    Technical Support Team Lead
                    Contact Support

                    Chaos

                    Comment


                    • #11
                      Personally, I have no issues and the IT department at Autodesk is on top of things so I've never had any networking problems or issues with group policy configuration. However, here are two threads with strange issues. I don't do a lot of network diagnostics, so it's a bit tricky for me to solve this. I've escalated it to Autodesk QA but no results yet. I just noticed behavior similar to what was being described in this thread, thought it might make sense to share some info. I don't believe this is a VRay or Max/BB problem, but a Windows problem. However, I am not totally sure.

                      https://forums.autodesk.com/t5/3ds-m.../false#M140428
                      https://forums.autodesk.com/t5/3ds-m...e/td-p/7058575

                      Comment

                      Working...
                      X