Announcement

Collapse
No announcement yet.

[VFBCore::SetRegion] Error writing render region to raw image file.

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

  • [VFBCore::SetRegion] Error writing render region to raw image file.

    I'm trying to render an animation but this keeps on popping up with Maya 2011x64, Win7x64 and V-Ray SP1 from june 20th:

    [2011/Jul/29|14:31:34] V-Ray error: [VFBCore::SetRegion] Error writing render region to raw image file.
    Error: [VFBCore::SetRegion] Error writing render region to raw image file.
    [2011/Jul/29|14:31:35] V-Ray error: Cannot write output image file "xxx/images/cam19_60007.exr"
    Error: Cannot write output image file "xxx/images/cam19_60007.exr"
    It worked for about 6 frames into an animation then decided to stop. However if I look on the server the image in fact has actually successfully rendered but mayaBatch.exe stops with:

    [2011/Jul/29|14:31:35] V-Ray: Render interrupted

    What is this and is there a way to fix this?

    Edit: I noticed this referred to "render region" but I'm sure this is disabled and have never used it in this scene.
    Maya 2020/2022
    Win 10x64
    Vray 5

  • #2
    check to see if vray frame buffer has render region button pressed in your scene.
    Dmitry Vinnik
    Silhouette Images Inc.
    ShowReel:
    https://www.youtube.com/watch?v=qxSJlvSwAhA
    https://www.linkedin.com/in/dmitry-v...-identity-name

    Comment


    • #3
      Unforuntately that is not the case, it is V-Ray being unable to write to exr for some reason or another. Using a different file format works fine.
      Maya 2020/2022
      Win 10x64
      Vray 5

      Comment


      • #4
        Are you writing to a network location? It's a known issue of the OpenEXR library. Storing the images locally or rendering to a .vrimg file will solve the problem.

        @Dmitry - the region rendering issue is long fixed now.

        Best regards,
        Vlado
        I only act like I know everything, Rogers.

        Comment


        • #5
          Originally posted by vlado View Post
          Are you writing to a network location? It's a known issue of the OpenEXR library. Storing the images locally or rendering to a .vrimg file will solve the problem.
          Aha, perfect will note this one down. Thank you Vlado.
          Maya 2020/2022
          Win 10x64
          Vray 5

          Comment


          • #6
            Originally posted by vlado
            Are you writing to a network location? It's a known issue of the OpenEXR library.
            Under what circumstances is this an issue? So far I have had no problems with rendering exr to network folders, but I'd like to be prepared if there are going to be problems.

            thanks
            David

            Comment


            • #7
              Its pretty random, seemed to work then all of a sudden got the error message. I htink it might be wise to write to vrimg in future,
              Maya 2020/2022
              Win 10x64
              Vray 5

              Comment


              • #8
                Originally posted by djx View Post
                Under what circumstances is this an issue? So far I have had no problems with rendering exr to network folders, but I'd like to be prepared if there are going to be problems.
                I think it only happens if the image takes a really long time to render (several hours).

                Best regards,
                Vlado
                I only act like I know everything, Rogers.

                Comment


                • #9
                  Hi Vlado, it was happening to me with DR and image render times of 1-2 minutes @720P.
                  Maya 2020/2022
                  Win 10x64
                  Vray 5

                  Comment


                  • #10
                    Originally posted by snivlem View Post
                    Hi Vlado, it was happening to me with DR and image render times of 1-2 minutes @720P.
                    Well, one more reason to use .vrimg then I hope this is fixed for the upcoming OpenEXR 2.0 library...

                    Best regards,
                    Vlado
                    I only act like I know everything, Rogers.

                    Comment

                    Working...
                    X