Announcement

Collapse
No announcement yet.

DR issues

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

  • DR issues

    Hi all,

    A funny thing happened yesterday! For no apparent reason all buckets rendered with the node at our office failed to render textures. I figured it was just a glitch so I rebooted the node and my machine and now DR just won't work! I can perform network renders through backburner and everything is fine but through DR all I get is 'render host not responding'! I can resolve the servers and vraydummy is active on both my PC and the node. All textures are available via the shared terastation.....I just can't get DR to work with the node.

    Any ideas?
    Is it penry....the mild mannered janitor?

  • #2
    After some messing around with the vraydummy and vrlservice I managed to get DR working but now the render node is not reading any of the textures in the scene! Vray/max/render node etc have all been working fine up till yesterday!

    HELP!!!
    Is it penry....the mild mannered janitor?

    Comment


    • #3
      SORTED!! UNC path issues. For some reason all my texture paths were eminating from our terrastation with the file path X: and not \\rendervault which apparently makes a huge difference with DR! Those two little backslashes make all the difference!
      Is it penry....the mild mannered janitor?

      Comment


      • #4
        Thanks for posting your solutions. I have recently been through some DR issues, too. Like yourself, I had issues with 'Start as a Service'. What a headache! In my research, I found that we should be able to have our models refer to an X: drive without having issues. Are you certain that the UNC was the issue, and not something else? Thanks again!

        Comment

        Working...
        X