[zoppo]

Hi JD,

I think I found a bug:
Animate something, export as animation. Render time is set to e.g. 20
When I start one of the generated files as single render in the network monitor everything is fine, max render time is 20 minutes.
But when I start it as Batch Render the render time changes to hours, in this case 20 hours.

Greetings
marc

[JDHill]

I confirm that, but it's not something that the plugin can change. You can override several of the settings, including stop time, in the batch job dialog, if you un-check the 'use scene settings' box. Also, in this scenario, I would think one might prefer using an animation job instead of a batch one.

[zoppo]

The plugin could do one thing - allow numbers like 0.5
Frankly I did not try the animation job, don't know why. But I will.

Is this a general problem / nw manager bug? Does this happen too if I export the scenes one by one instead of using "export animation"?
I'm no longer in the office, so I can't try right now.

[JDHill]

The resolution of that parameter is one minute, so the plugin can't do what you ask. Personally, that's fine with me, as I don't see where a person would want to set the stop time to less than a minute, aside from trying to work around an issue like this.

And I checked with all four network job types; it appears to be only the Batch type that's reading or using the stop time value found in the MXS incorrectly.

[zoppo]

I guess you are right about the .5 thing, it would only be useful for this workaround.
Could you please report this NWManager bug?