Blender 4.0.2

#1 · 14. Februar 2024, 16:32

Hey,

i have installed blender 3.6 and after that, Blender 4.0 integration.

Even after I removed the 3.6 integration, Prism sends the command to start Blender3.6 via the State Manager to deadline.

Furthermore, the command for the output file does not seem to be entirely correct.

It is: -o "......\Blender_test_Concept_v0003_beauty.exr" -s 1 -e 1 -a but should be: -o "......\Blender_test_Concept_v0003_beauty_####.exr" So that the file dont look like: "Blender_test_Concept_v0004_beauty.exr0001.exr"

#2 · 14. Februar 2024, 17:03

Hey,

The Blender executable used for rendering is not defined by Prism, but by your Deadline Blender Plugin settings. The Blender Deadline plugin doesn't have any version management like the Houdini plugin. It just uses a list a paths to your Blender executables and uses the first one it finds. To use different Blender versions for different jobs you would need to modify the Blender Deadline plugin.
That looks like you have set the framerange set to "Single Frame" in the State Manager. In that case Prism tries to not use any framepadding. That works fine in local renders, but you're right that this causes wrong filenames when rendering with Deadline. This is because the Blender Deadline plugin enforces the framepadding by specifying a start and end frame in the render command.
I don't think the Blender Deadline plugin will be updated anytime soon to support single frame rendering without framenumbers, so in the next Prism update Prism will submit Deadline Blender jobs with framepadding also for Single Frame jobs. For multi frame jobs everything should already be correct in the current version.

#3 · 15. Februar 2024, 10:10

Thanks,

And yes, you're right, version 4 wasn't set correctly in Deadline.

And yes, when I render a sequence, the frame padding is correct.