Mirko Jankovic

Well I've got Rocky Linux 9.5 at the moments that solved problem I guess.. It have both Wayland and X11 integrated so. will live for a bit more. But still would be great to have Wayland support, Blender got it for couple years now...

ronald_a
On your rop, you need to have the „all frames at once“ checker checked (i am not in front of houdini, so this is most certainly call something else).

Sometimes I cannot use this as it won't update animated parts. At one example had some cashed simulated sand, it wasn't updating frame to frame

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?

It is especially problematic when using configure layer to setup frame ranges and use those for render frame range in rop as well as updating timeline to that frame range with multiple renderrops in scene.