Output Filename Incremental

Deadline
1

Hello,

I suppose I’m doing this wrong but when I try to setup a new job with VRaySubmission using a .vrscene file sequence I’m not sure what to set as Output File name to get the deadline to make a file sequence. I have tried some different settings like adding wildcards ie filename_####.exr but the output file name will be exactly as I wrote instead of replacing the #### with a serial number. Therefor an animation will just render out one image, or more correctly every slave will overwrite the same file.

I have tried to find sequential naming of files in the documentation but with no luck.
Please help!

cheers!
//Peter

2

Hello Peter,

From our documentation: VRay File: The VRay file (*.vrscene) to be rendered. If you are submitting a sequence of vrscene files (one file per frame), you only need to select one vrscene file from the sequence.

Does this help?

3

Hi,

Thank you for your response. But it doe not help me with my issue. I have no problem select the vrscene sequence as you describe. The problem is the output filename. I cannot manage to render a sequence with incremental output filenames. All the slaves render but they write to the same filename resulting when all frames are rendered in only one file ie filename_.exr, not the expected filename_0001.exr, filename_0002.exr, filename_0003.exr…

How do I tell deadline to increment every output filename for each frame?

Cheers!
//Peter

4

Hello Peter,

As far as I understand, this should already be done. Could you email support@thinkboxsoftware.com with your scene file so we can try to reproduce? Otherwise a few job reports showing it writing out the same file would be helpful. Thanks.

5

I have mailed you just now.

6

Hello,

Thanks for the email, we will take a look and try to test this asap, and reply via the ticket system. I will update the forum post when we have some more concrete answers for anyone searching.

7

Hello,

How are things going on this issue? Do you need anymore feedback from me?

8

Hello Peter,

So I have been able to replicate what you are seeing, but not been able to figure out how to get it to work. I am going to see if we can fix this in code instead of thinking around the problem, but that would likely put a fix in 7.1 or 7.2.