Hello,
actually using: vray_adv_43003_houdini17.5.460_3819bc8_7071
we manual exporting one vrscene per frame by using ${F4] in the filename.
when using the vray to deadline node, using “export local/render farm” - the node suggested to use ${batch} instead. But then wo got only one vrscene. X666_002_deadlineTest_vray4_A_v001_rah_Main.0000-0005.vrscene
using ${F4} - submission failed.
How we shoud export?
There is a frames per job control - did it work for you? It’ll substitute appropriate variable automatically (F4 or FBATCH).
> submission failed.
With some error?
frames per job set to “1” will seperate the vrscenes, but also the frames to render, and every frame is submitted seperate as a job (which tooks long). so , no that didnt work.
if i didnt fix the $batch suggestion i got the error:
VFH * Deadline version: v10.1.5.1 Release (abec767df)
VFH * V-Ray Deadline ROP: “/obj/ropnet1/vrayDeadline”
VFH * ROP: “/obj/ropnet1/vray”
VFH * Submission failed!
> and every frame is submitted seperate as a job (which tooks long). so , no that didnt work.
This is how it’s implemented…
hmmm. okay, but that isnt useable at all. if u want requeue task instead of resubmit as many jobs as frames are failed.
the smart way would be : to export seperate vrscenes, but submitting a job with a framerange (tasks) .
Job accepts a single vrscene file path. Separate files means different input files. Single jobs can’t work with multiple files or at least I’m not aware of this.
So, “submitting a job with a framerange” will work only on a single vrscene file.
Ok, I’ll check deadline plugin sources, may be I’ve missed that control.
great, thanks a lot!
Hey @suedlich_t ,
the change you’ve requested will be in tomorrow’s nightly builds.
Hope that helps!
Thanks a lot, works now, and $F4 also fixed.
Now if you could fix the $OS thing: (No Change Required, Closed) [HOU-1693] [HOU-1673] Batch rendering workflow needs to be fixed - V-Ray for Houdini :: Issues - Chaos Forum
and our wish : vray submit to deadline - different versions - V-Ray for Houdini :: General - Chaos Forum
we would be very glad about, and can use the submitter smoothly.
there is a logical failure in calculating the framerange. You are calculating SeqEnd - SeqStart. 1001-1025 is then only 24frames instead of 25. it should be calculated: SeqEnd - SeqStart +1
Hey @suedlich_t you are referencing the “Frames Per Job” default value right? It should be fixed in the next nightly build.
