Announcement

Collapse
No announcement yet.

(Done) [HOU-1898] Vray submit to Deadline - one vrscene per frame ?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • (Done) [HOU-1898] Vray submit to Deadline - one vrscene per frame ?

    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?
    Last edited by Gosho.Genchev; 21-05-2020, 06:31 AM.

  • #2
    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?
    V-Ray For Houdini | V-Ray Hydra Delegate | VRayScene
    andrei.izrantcev@chaos.com
    Support Request

    Comment


    • #3
      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 [Info] * Deadline version: v10.1.5.1 Release (abec767df)
      VFH [Info] * V-Ray Deadline ROP: "/obj/ropnet1/vrayDeadline" [a4ff375]
      VFH [Info] * ROP: "/obj/ropnet1/vray"
      VFH [Error] * Submission failed!

      Comment


      • #4
        > and every frame is submitted seperate as a job (which tooks long). so , no that didnt work.

        This is how it's implemented...
        V-Ray For Houdini | V-Ray Hydra Delegate | VRayScene
        andrei.izrantcev@chaos.com
        Support Request

        Comment


        • #5
          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) .

          Comment


          • #6
            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.
            V-Ray For Houdini | V-Ray Hydra Delegate | VRayScene
            andrei.izrantcev@chaos.com
            Support Request

            Comment


            • #7
              we do. we exporting vrscenes per frame: and in deadline gui we submit one job.
              the controlbox: "Seperate Input vrscene Files per Frame" do the magic
              Attached Files

              Comment


              • #8
                Ok, I'll check deadline plugin sources, may be I've missed that control.
                V-Ray For Houdini | V-Ray Hydra Delegate | VRayScene
                andrei.izrantcev@chaos.com
                Support Request

                Comment


                • #9
                  great, thanks a lot!

                  Comment


                  • #10
                    Hey suedlich_t ,

                    the change you've requested will be in tomorrow's nightly builds.

                    Hope that helps!
                    gosho.genchev@chaosgroup.com

                    Comment


                    • #11
                      Thanks a lot, works now, and $F4 also fixed.
                      Now if you could fix the $OS thing: https://forums.chaosgroup.com/forum/...be-fixed/page3
                      and our wish : https://forums.chaosgroup.com/forum/...erent-versions
                      we would be very glad about, and can use the submitter smoothly.

                      Comment


                      • #12
                        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

                        Comment


                        • #13
                          Hey suedlich_t you are referencing the "Frames Per Job" default value right? It should be fixed in the next nightly build.

                          Comment

                          Working...
                          X