Itoo Software Forum

Author Topic: Distributed rendering issues  (Read 1983 times)

Thomas Hellmuth

  • Newbie
  • *
  • Posts: 5
Distributed rendering issues
« on: January 13, 2014, 07:45:16 PM »
Hello,

i got big a problem,


First table sorry if that problem was already solved but I haven’t found anything about that. Also sorry if my English isn’t that good.
My problem is the following.
Everything is working fine with my machine. The renderings are okay if I only have a box (sphere or whatever)  or even when I’m going to use Forest pro. If I’m going to include some render slaves and use distributed rendering without forest pro the slaves are working fine. As soon as I’m going to use the forest pro the main machine is rendering the whole scene alone and the slaves are doing nothing. In the small white box I’m able to see that the slaves are detected and the scene is loaded but no buckets will show up.
Can somebody help me?

Cheers, Thomas

yuv

  • iToo Software
  • Sr. Member
  • *****
  • Posts: 312
  • iToo Software - CEO
    • Itoo Software
Re: Distributed rendering issues
« Reply #1 on: January 13, 2014, 08:05:44 PM »

Normally this problem is caused by a mismatch of plugin versions. Could you check what version of Forest Pack Pro is installed in the render nodes ?
Daniel Quintero
Itoo Software
www.itoosoft.com
daniel@itoosoft.com

Thomas Hellmuth

  • Newbie
  • *
  • Posts: 5
Re: Distributed rendering issues
« Reply #2 on: January 13, 2014, 08:13:42 PM »
it is Forest Pack Pro 4.1.5

Thomas Hellmuth

  • Newbie
  • *
  • Posts: 5
Re: Distributed rendering issues
« Reply #3 on: January 13, 2014, 08:22:47 PM »
okay it works with the forest pro trees but not with the laubwerk trees

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3315
    • iToo Software
Re: Distributed rendering issues
« Reply #4 on: January 14, 2014, 09:45:06 AM »
Is the Laubwerk software installed in the slave nodes ?
What render engine do you use, Mental Ray or VRay ?
Carlos Quintero
iToo Software

Thomas Hellmuth

  • Newbie
  • *
  • Posts: 5
Re: Distributed rendering issues
« Reply #5 on: January 14, 2014, 10:12:52 AM »
laubwerk Plantskit 1 and 2 is installed and iam using vray for renderging

Laubwerk

  • Newbie
  • *
  • Posts: 9
    • Laubwerk Website
Re: Distributed rendering issues
« Reply #6 on: January 14, 2014, 01:07:32 PM »
Hi TR14174,

we've been made aware of a few people having issues such as this and are currently investigating. We are having problems reproducing the problem, it seems to consistently happen for a few customers and not at all for others. It doesn't happen on any of the test setups that we prepared, so any information that we can get about your particular configuration will help us nailing this down. Therefore it would be awesome, if you could contact us directly at support@laubwerk.com and provide us with configuration details (Windows version, 3ds Max version, V-Ray version, Laubwerk Plugin version) of at least the workstation and one client that isn't working. An (as simple as possible) test scene that definitely exhibits this problem would also be excellent. Even when that scene runs smoothly here, we definitely know it fails on your side and we can work on coming up with a configuration that lets us reproduce the problem.

BTW: This only happens with V-Ray DR, so if you need to render an animation you can temporariliy resort to using backburner only. This will work.

Sorry for the inconvenience!

Best
Timm

Laubwerk

  • Newbie
  • *
  • Posts: 9
    • Laubwerk Website
Re: Distributed rendering issues
« Reply #7 on: January 15, 2014, 10:12:41 PM »
Just so everybody knows: We've been able to find and fix the problem. The fix will be incorporated in our upcoming 1.0.8 update of Laubwerk Plants Kits. If anybody runs into this issue before the update is due and is in a hurry, please contact us directly at support@laubwerk.com with the 3ds Max version you're using and we will provide you with a patch.

Best
Timm Dapper

Thomas Hellmuth

  • Newbie
  • *
  • Posts: 5
Re: Distributed rendering issues
« Reply #8 on: January 16, 2014, 10:47:25 AM »
Problem solved.

Thanks Laubwerk