Network render issue

Post your tutorials and help questions in this forum
Locked
Fabian-Eshloraque
Posts: 74
Joined: Sun Nov 17, 2013 3:29 pm

Network render issue

Post by Fabian-Eshloraque »

Hi Guys,

I'm having a problem when rendering on the farm.

Here are the specs:

1. Lightwave 11.6.1
2. Kray 2.5.9
3. LW Instances in scene
4. BNR (Paul from butterflynetrender is also checking this error)
5. Scene has a GI cache

Error:

1. Slave renders a frame, no problem
2. Slave starts on second, is stuck at 100% forever
3. No render log are produced by LWSN.exe for the frame its stuck

Any thoughts on it?

Fabian
Fabian-Eshloraque
Posts: 74
Joined: Sun Nov 17, 2013 3:29 pm

Re: Network render issue

Post by Fabian-Eshloraque »

And local rendering a sequence no issue's...
Fabian-Eshloraque
Posts: 74
Joined: Sun Nov 17, 2013 3:29 pm

Re: Network render issue

Post by Fabian-Eshloraque »

So did some debugging all day for this. It seems to happen when the renderslave starts to calculate the prerendering. Which means that an old bug is back. (see previous threats about instancing and rendering second frame hangs)

Attached the renderlog.
Attachments
kraylog.txt
(123.64 KiB) Downloaded 183 times
User avatar
Janusz Biela
Posts: 3265
Joined: Mon Mar 13, 2006 10:39 am
Location: Finland
Contact:

Re: Network render issue

Post by Janusz Biela »

Fabian-Eshloraque wrote:So did some debugging all day for this. It seems to happen when the renderslave starts to calculate the prerendering. Which means that an old bug is back. (see previous threats about instancing and rendering second frame hangs)

Attached the renderlog.
I will send mail to G. with this.
Fabian-Eshloraque
Posts: 74
Joined: Sun Nov 17, 2013 3:29 pm

Re: Network render issue

Post by Fabian-Eshloraque »

Thank you.
Fabian-Eshloraque
Posts: 74
Joined: Sun Nov 17, 2013 3:29 pm

Re: Network render issue

Post by Fabian-Eshloraque »

Hey Janusz,

I found a workaround for the bug:

1. Bake the gi cache (bake only, framestep, etc...)
2. Render the frames on the farm with cache irridiance OFF.

So it loads the cache, even with cache off. Difference is 10% more rendertime. (my rendertime is average of 12min on the farm, 8 on workstations, so kinda happy with that, lightwave native renders are around 1.5u)

Grtz,

Fabian
User avatar
Janusz Biela
Posts: 3265
Joined: Mon Mar 13, 2006 10:39 am
Location: Finland
Contact:

Re: Network render issue

Post by Janusz Biela »

Fabian-Eshloraque wrote:Hey Janusz,

I found a workaround for the bug:

1. Bake the gi cache (bake only, framestep, etc...)
2. Render the frames on the farm with cache irridiance OFF.

So it loads the cache, even with cache off. Difference is 10% more rendertime. (my rendertime is average of 12min on the farm, 8 on workstations, so kinda happy with that, lightwave native renders are around 1.5u)

Grtz,

Fabian
Yes that's strange. Anyway I will test soon uploader for FarageFarm (betatest), I just got new version. So I will test this system with load baked GI by network render.
Fabian-Eshloraque
Posts: 74
Joined: Sun Nov 17, 2013 3:29 pm

Re: Network render issue

Post by Fabian-Eshloraque »

Hi Janusz,

With cache irridiance off, it happens random to nodes/workstations in the renderfarm after second render. Anybody else had this problem?
User avatar
Janusz Biela
Posts: 3265
Joined: Mon Mar 13, 2006 10:39 am
Location: Finland
Contact:

Re: Network render issue

Post by Janusz Biela »

I am not sure where is problem. I do not have here render farm here. But I am beta tester of GrarageFarm client software and I will try test K2.x soon on theirs network again after half year brake (I got new client for LW).
Of course GarageFarm has it own system and if my test will pass there (it seems work there without problems - they say nothing about Kray problems) then problem will be on BNR side.
Meanwhile with G. we testing K3...
Fabian-Eshloraque
Posts: 74
Joined: Sun Nov 17, 2013 3:29 pm

Re: Network render issue

Post by Fabian-Eshloraque »

I changed to lw 11.6.3 and I dont have the problem anymore. Still doing some testing, but seems to be lw 11.6.1.
Locked