When rendering with Movie Render Queue, a single-frame range doesn’t seem to work. We need to render more frames than we have to, to have a specific frame range. For example, rendering 1001–1001 it doesn’t work. Instead, we have to render 1001–1002, which produces two frames.
This becomes a bigger issue on a render farm. We split renders into 5-frame chunks, for example, but because every job needs an extra frame, about 20% of the frames are rendered twice by different machines. This increases render time and rendering costs unnecessarily.
Do you know of any workaround or planned improvement that could help us with this workflow?
Note: This may be related to an old issue where the last frame was not always written when the render finished, although we haven’t confirmed whether that’s still the case in UE 5.7.
Thanks for your help in advance and wishing you all a lovely day!
If you have the render set to 1001-1002 it should not be rendering frame 1002. Only frame 1001? Is this not the case? If so, could you provide more information about your render settings, such as which renderer you are using and the sampling method?
That said, yes its confusing. It was originally written that way, and we have not changed it since, as that would potentially break a lot of people’s existing configs. There has been some discussion about doing it for UE6.
Our team realized that this was actually an issue with our custom tool, Render Manager, which doesn’t currently allow rendering a single frame or a custom frame range. We ran a few more tests and confirmed that Unreal does support this functionality, so we’ll fix it in our tool instead. Sorry for the confusion.
Yes, totally understandable. We’re really looking forward to seeing what’s being cooked up for UE6!
We’re really looking forward to seeing what’s being cooked up for UE6!