Announcement

Collapse
No announcement yet.

Hilbert in RC2 craches

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

  • Hilbert in RC2 craches

    In RC2, when rendering high resolution images (4000px) using Hilbert and a small bucket size (16 or so) Max crashes.
    Guido.

  • #2
    Do a search for vrimg
    Eric Boer
    Dev

    Comment


    • #3
      tnx Rerender.
      I know about the vrimg and memory related crashes, which by the way there's a lot of'em. I just wanted Vlado to know about this Hilbert thing. It appears to be a bug much more than a memory issue (or a combination of both).
      No matter what scene I am working on, when rendering at 4000px with hilbert and a backet of 16, it crashes.
      Guido.

      Comment


      • #4
        yeah thats interesting. Hilbert was supposed to be more memory efficient then other bucker rendering types?
        ____________________________________

        "Sometimes life leaves a hundred dollar bill on your dresser, and you don't realize until later that it's because it fu**ed you."

        Comment


        • #5
          Originally posted by percydaman
          yeah thats interesting. Hilbert was supposed to be more memory efficient then other bucker rendering types?
          Actually, the default "triangulation" mode is the most memory efficient one.

          There is a bug in the Hilbert sequence that will cause it to crash for high resolution images (it is generated recursively and a stack overflow occurs). It is a known issue and will eventually be fixed. Other sequence types do not have this problem. So it would be best to avoid the Hilbert sequence for the time being.

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

          Comment


          • #6
            oops, i was mistaking the hilbert for the default.
            ____________________________________

            "Sometimes life leaves a hundred dollar bill on your dresser, and you don't realize until later that it's because it fu**ed you."

            Comment

            Working...
            X