Itoo Software Forum

Author Topic: Starter Library fails with distributed rendering  (Read 159 times)

Jerny11

  • Newbie
  • *
  • Posts: 10
Starter Library fails with distributed rendering
« on: October 03, 2018, 08:39:07 PM »
Hi all,
I have no problem rendering any of the libraries I have on the server.
When using DR with vray spawner the starter library trees disappear on all slave buckets (my computer buckets are fine).
Seems like there must be a strait forward solution I am not seeing.
Any ideas?

Thanks!

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1088
    • iToo
Re: Starter Library fails with distributed rendering
« Reply #1 on: October 04, 2018, 09:04:37 AM »
Have You installed library items in render slave PCs ?
As an alternative You can relink library assets to be used from network instead of installing to each PC. Here is guide to do this.
Rokas
iToo Software

Michal Karmazín

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1553
Re: Starter Library fails with distributed rendering
« Reply #2 on: October 04, 2018, 09:06:00 AM »
Hi,

I would suggest you follow our Distributed Rendering issues (applicable for network rendering with backburner too) post to identify where the problem might be in your case. Basically, there are two common causes for similar issues: the plug-in is not properly installed on all render nodes, or there are missing paths to used assets.

Hope that helps.

Best regards,

Jerny11

  • Newbie
  • *
  • Posts: 10
Re: Starter Library fails with distributed rendering
« Reply #3 on: October 08, 2018, 07:13:58 PM »
Thanks guys, Rokas we will try the common path on the server.
Good to know!

Jerny11

  • Newbie
  • *
  • Posts: 10
Re: Starter Library fails with distributed rendering
« Reply #4 on: October 09, 2018, 11:14:47 PM »
Okay, I have got it working off a network directory! Thanks
When I update through the update manager will it install the items locally or to this network location?
If it gets updated locally do I have to copy each item to the server separately?
Thanks again

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1088
    • iToo
Re: Starter Library fails with distributed rendering
« Reply #5 on: October 10, 2018, 08:09:49 AM »
If You used registry settings to change library location- then it will download updates to that location in the future.
Rokas
iToo Software

Jerny11

  • Newbie
  • *
  • Posts: 10
Re: Starter Library fails with distributed rendering
« Reply #6 on: October 10, 2018, 03:40:20 PM »
Thanks Rokas,
Just to make sure I have it straight:

I created 2 different folders one for the library ("B") and one for the downloads ("A") so the Library wouldn't be cluttered with random downloaded files.

If I download to folder "A" on the server (designated through installation or update manager)
It will install, to folder ("B") library, if I changed the path to it in the registry settings.

Does this sound right?



Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1088
    • iToo
Re: Starter Library fails with distributed rendering
« Reply #7 on: October 10, 2018, 03:42:40 PM »
sounds right.
Rokas
iToo Software

Jerny11

  • Newbie
  • *
  • Posts: 10
Re: Starter Library fails with distributed rendering
« Reply #8 on: October 10, 2018, 04:02:13 PM »
Great thanks for the help!

Jerny11

  • Newbie
  • *
  • Posts: 10
Re: Starter Library fails with distributed rendering
« Reply #9 on: October 10, 2018, 06:12:41 PM »
Wait, just noticed in doing these changes all my personal library that is on the server is no longer showing through my Library browser.
Have I lost all these hours of work or is there a way to retrieve them?

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1088
    • iToo
Re: Starter Library fails with distributed rendering
« Reply #10 on: October 10, 2018, 07:27:40 PM »
Your created library should still be in Your hard drive.

Look for index.xml file where You stored Your library.


Once You find it. Add Parent folder to Library Browser:


Doing these steps should restore Your library.
Rokas
iToo Software

Jerny11

  • Newbie
  • *
  • Posts: 10
Re: Starter Library fails with distributed rendering
« Reply #11 on: October 10, 2018, 09:26:54 PM »
Great, thanks sooo much!!
Worked like a charm

Curious, could I have changed the starter Library this way when I first had the problem?
Not as efficient on the render slaves I guess (having to open max and such).

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1088
    • iToo
Re: Starter Library fails with distributed rendering
« Reply #12 on: October 11, 2018, 08:02:36 AM »
Basically slaves need to see shared assets (they need to have path pointing not on Your "D:\" drive but to shared network address i.e. "\\192.168.1.1". They still can be in Your "D:\" drive but sharing settings and paths matter here)
I understand that this is difficult to understand so illustration:
I have some maps for models used in the scene and want to render that in distributed rendering.


As You see they are pointing to D:\... drive and that path is invalid for all other rendering nodes in my networked PCs.

Though they are in the shared folder and can be accessed in alternative paths:
and mapped drive "L:\"

These 3 paths are all valid for my local workstation, but only 2nd paths is valid in my entire network. But since I have mapped L:\ drive in all of my networked PCs pointing to my Library folder

The last path is what I am using for my assets: "L:\Models\Vizpeople\BirchTrees\textures"

Now it is important to make sure that materials maps used point to either "\\192.168....." or "L:\" path so it can be rendered correctly in all DR nodes:


Same applies for XRef objects used in the scene.
This is just one of few ways how to configure network shares for distributed rendering.
Hope this is clear to understand and helps in Your situation.

Note:
Or You need to check transfer missing assets.
Rokas
iToo Software