Announcement

Collapse
No announcement yet.

Hqueue issues

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

  • #31
    >I'm not sure how that could be related to VFH then...

    I think you are right. I will soldier on. Thanks for all the help so far guys. Really appreciate it.

    Comment


    • #32
      To be fair, none of us are HQueue experts. I'd love to help but I think a question on the SideFx forums would be more beneficial.

      Please do tell us if you find a straight-forward solution. I've been keeping my files on a shared location when testing this as it's not related to V-Ray in particular and have no idea how to go about resolving this.

      Best regards!
      gosho.genchev@chaosgroup.com

      Comment


      • #33
        I will indeed. Thanks for the help again !!

        Comment


        • #34
          If I send a job to HQueue with MANTRA it is totally fine about $HIP file root references for textures etc. If I have $JOB references it forces me to turn them into $HIP references.
          Fine it works !

          If I send a job to HQueue with VRAY it automatically sets it up as $JOB on export with no way of sending the job with $HIP references. This would be fine if $JOB was amended in the copied scene file, but it RETAINS it's local machine reference so none of the textures or HDRi's render.

          I am trying to figure out why this is the case. I will update if there is any breakthrough.
          Last edited by Jim Meston; 15-05-2020, 06:16 AM.

          Comment


          • #35
            OH MY GOD

            I have got it working !!!!!

            I figured that the Vray ROP is referencing (not $HIP) and must be forcing $JOB on the export.


            In the Vray ROP node the default save location is this.... ${HIP}/render/${HIPNAME}.${AOV}.$F4.exr

            I think with ${HIP} the curly brackets are screwing up the output.

            Changing it to $HIP everything renders and distributes perfectly.

            Might be something to change if it doesn't affect anything else!!

            Thanks again guys, you really saved my bacon.

            ​​​​​​​Jim







            Last edited by Jim Meston; 15-05-2020, 06:50 AM.

            Comment


            • #36
              Oh god ... now I remember I added that part to the script in the documentation for this reason.
              If you hit any issues, please update the Houdini python files as described in the docs section.

              Best regards!
              gosho.genchev@chaosgroup.com

              Comment


              • #37
                I already am running with the amended python file.... should that have fixed it?

                Also... do I only need to set the fixed Hqrop.py on the machine that I send to HQueue from ? (not on all the client machines)

                Comment


                • #38
                  Yes, the change should only be needed on the machine used to submit from.

                  OK, I will check in a day or two - hopefully there's something that can be done about this so {} are also supported.

                  You should be safe with $HIP though, I hope

                  Best regards!
                  gosho.genchev@chaosgroup.com

                  Comment


                  • #39
                    Deleted by user due to bad or outdated info.
                    Last edited by Jim Meston; 24-08-2020, 06:27 AM.

                    Comment


                    • #40
                      Just checking as I am about to do a farm software upgrade, do we still need to amend the hqrop.py for rendering via Hqueue?

                      Comment


                      • #41
                        Nothing has changed in regards to HQueue so I'm afraid the answer is yes.

                        All the best!
                        gosho.genchev@chaosgroup.com

                        Comment

                        Working...
                        X