Announcement

Collapse
No announcement yet.

VR frame buffer not saving

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

  • VR frame buffer not saving

    I need suggestions to solve this issue, specs are the following:

    viz 2005
    vr 14921
    dual xeon 3.2
    2gb
    image 4400x1920 px
    9:30 hrs rendertime
    some g-buffer / render elements active
    vr frame buffer
    render through backburner
    I launched it yesterday and today I can only see the end of my render, than vr frame buffer closed itself without any warning in the vrlogfile. I searched the path where the images were supposed to be but the folder was empty!!
    I searched throught the forum but because my deadline is in a couple of days I've no time to test, I need suggestions for the most reliable solution; vrimg, dynamic memory ,3gb switch (I made some tests and it seems unstable on my machine)

    thanx in advance

    a.
    Alessandro

  • #2
    Does the render node have access and rights to the save path?
    Eric Boer
    Dev

    Comment


    • #3
      You can use the .vrimg file option with the "render to memory" option off.

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

      Comment


      • #4
        thanx guys for your answers,

        using vrimg option solved my problem!!!

        Now I'm thinking if there is a method to evaluate, more or less, the amount of ram the every scene requires in order to prevent this kind of issue? ...in other words, which are the limits? 4000 px is a critical point?
        or, in any case, is it always better using vrimg file?

        a.
        Alessandro

        Comment


        • #5
          Originally posted by zeronove
          Now I'm thinking if there is a method to evaluate, more or less, the amount of ram the every scene requires in order to prevent this kind of issue? ...in other words, which are the limits? 4000 px is a critical point?
          Well, the best way is to actually render the scene and see how much RAM it takes. For large images though, the .vrimg file is the way to go. Hopefully in the bright 64-bit future ahead, there will be a lot less of these issues.

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

          Comment

          Working...
          X