AWS Thinkbox Discussion Forums

Slave Log does not show progress of Arnold Render

Hello,

We are rendering with Arnold through Deadline. Slaves pick up our jobs and render them successfully, but we are noticing some missing information in the slave log. Specifically there is a big jump in where we normally see the renders progress.

Here is what we see in the slave log through Deadline:

0: STDOUT: 00:00:05 415MB | starting 24 bucket workers of size 64x64 ... 0: STDOUT: 00:01:45 499MB | bucket workers done in 1:40.25 0: STDOUT: 00:01:45 499MB | render done

We have set the Verbosity level in Arnold to 5, which should show results similar to our local renders:

00:00:05 617MB | starting 24 bucket workers of size 64x64 ... 00:00:05 650MB | 0% done - 9 rays/pixel 00:00:06 653MB | 5% done - 9 rays/pixel 00:00:06 656MB | 10% done - 13 rays/pixel 00:00:06 656MB | 15% done - 9 rays/pixel 00:00:06 657MB | 20% done - 9 rays/pixel 00:00:06 660MB | 25% done - 11 rays/pixel 00:00:06 660MB | 30% done - 9 rays/pixel 00:00:06 662MB | 35% done - 12 rays/pixel 00:00:06 663MB | 40% done - 38 rays/pixel 00:00:06 663MB | 45% done - 43 rays/pixel 00:00:06 663MB | 50% done - 31 rays/pixel 00:00:06 663MB | 55% done - 18 rays/pixel 00:00:06 663MB | 60% done - 11 rays/pixel 00:00:06 664MB | 65% done - 19 rays/pixel 00:00:06 664MB | 70% done - 11 rays/pixel 00:00:06 664MB | 75% done - 14 rays/pixel 00:00:06 664MB | 80% done - 20 rays/pixel 00:00:06 662MB | 85% done - 14 rays/pixel 00:00:06 653MB | 90% done - 10 rays/pixel 00:00:06 643MB | 95% done - 16 rays/pixel 00:00:06 642MB | 100% done - 43 rays/pixel 00:00:06 642MB | bucket workers done in 0:00.97 00:00:06 642MB | render done

Now, our Task Progress bars in Deadline appear to be working correctly, so we believe our Arnold setup is correct because Deadline is getting that information. Is there a possibility we have something setup incorrectly, or that Deadline is not grabbing the proper information from Arnold to populate the slave log? This happens in single frame and chunked jobs too.

Thanks!

Privacy | Site terms | Cookie preferences