So here’s an issue I’ve run into with no explanation so far: Houdini, Solaris, and Karma. I set up frame ranges for two ROPs:
ROP1: 1-100
ROP2: 101-200
If I submit both and the timeline is set to ROP2’s range (101-200) at the time of submission, Deadline will mark all frames as completed correctly, but ALL frames are rendered and saved as frame.101.exr.
ROP2 renders normally from Deadline. It seems like it doesn’t want to render frames before the lowest frame number in the timeline at the moment of Houdini save, if that makes sense? ROP2 renders fine, and the sequence is correct.
So right now, if I have multiple ROPs with different frame ranges, after sending them all to Deadline, I have to set the timeline to capture all those frames, i.e., from the lowest frame in ROP1 to the last frame in the latest ROP.
Any ideas? Has anyone else run into this?
This makes sense. The frame range corresponds to the timeline. You would have to render them with different frame ranges.
Perhaps it could be made to set the scene range before starting the render (in hrender_dl.py).
It does not make sense if I have multiple shots for an episode for example. And each ROP is 1 shot. Each sh have it’s own frame range. Using configure layer node node sets frame range for each sh/rop and can then use Stage frame range drives pay range to automatically frae to frame range for each chot I work on. Same for rendering in ROP using configure layer start end frame to see for render frame range as well.
But as said after submitting all shots I have to add extra stage layer and set frame range 1 to maximum frame range possible to encompass all frames and then save scene before rendering on deadline. Anoying 
I get it, but the scene is submitted as is.
One option is to override the submitter/scheduler.