Announcement

Collapse
No announcement yet.

Problems rendering large

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

  • Problems rendering large

    Just did a search, found billions of results.

    Quick question: I am having problems rendering above 4000x2000. I need to render this spherical camera at minimum 5000x2500, but it crashes before it even loads anything up in Max.

    I can render the 4000x2000 image just fine, but when I bump it higher it crashes at around 800mb of memory. My bucket size is 32x32 and I have even tried rendering with the VRIMG format and the VFB. Any ideas?

    Thanks,
    Colin
    Colin Senner

  • #2
    Switch to dynamic memory or try rendering via backburner - are there any huge textures you could reduce or heavy objects that could be made into vray proxies?

    Comment


    • #3
      Good suggestions, but it doesn't seem to be memory related, seeing as it's memory consumption doesn't get very high before it crashes.

      Dynamic memory is an option I haven't tried. I'll try that now.

      Thanks Jo,
      -Colin
      Colin Senner

      Comment


      • #4
        switching to Dynamic Memory did not help. Also I have been rendering with BB so that will not reduce it either.

        It renders fine at 4000x2000, so it's not material related I don't think. and the darn thing crashes almost immediately after starting.

        -Colin
        Colin Senner

        Comment


        • #5
          Just to make sure... when you rendered to the vrimg file, you unchecked the "Render to Memory frame buffer" box right? Otherwise, there's no memory saving.
          www.dpict3d.com - "That's a very nice rendering, Dave. I think you've improved a great deal." - HAL9000... At least I have one fan.

          Comment


          • #6
            ah...no didn't try that. Thanks and worth mentioning, I'll try when I get to the office tomorrow. Thanks.
            Colin Senner

            Comment


            • #7
              To further elaborate...
              Originally posted by vlado
              Basically, you are running out of RAM. One way to reduce the memory usage for the render elements is to write the image to a .vrimg file and then use the vrimg2exr converter to extract the channels.

              (*) Make sure you are using the V-Ray VFB;
              (*) In the Common tab of the Render scene dialog set the resolution to something like 320x240;
              (*) In the V-Ray VFB settings, turn OFF the "Get resolution from Max" option for the VFB, and specify the actual resolution that you need;
              (*) Turn off the "use memory frame buffer" option;
              (*) Turn on the "write raw image file" option and specify a .vrimg file in the field below it.
              (*) Turn on the "generate preview" option.
              (*) After the rendering is complete, use the vrimg2exr tool to extract the render elements as .exr files. You can find the vrimg2exr tool in the Start menu > Programs > Chaos Group > V-Ray for 3dsmax > Tools. There is also a GUI for it posted in the off-topic section of the forum, I think.

              Alternatively, you can simply render on a 64-bit machine with 64-bit 3dsmax and V-Ray.

              Best regards,
              Vlado
              www.dpict3d.com - "That's a very nice rendering, Dave. I think you've improved a great deal." - HAL9000... At least I have one fan.

              Comment


              • #8
                i would suggest rendering through backburner, with precalc Irrmap/LC (if you're using one).
                Harry G

                Comment


                • #9
                  as I have already alluded to, this problem does not seem a memory problem. I switched to VFB with Render to Memory etc unchecked and that does not solve the problem.

                  no dice any other suggestions? Litterally the only thing I'm doing is changing the resolution from 4000x2000 (which renders just fine, and quickly) to 5000x2500 and it crashes almost immediately upon loading.

                  Thanks,
                  -Colin
                  Colin Senner

                  Comment


                  • #10
                    If you are using the Hilbert sequence type, switch to another one and see if you still have this.

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

                    Comment


                    • #11
                      actually I was vlado, switching and checking now...
                      Colin Senner

                      Comment


                      • #12
                        Problem solved! Wow, that was obscure...I love Hilbert, guess I'll stop liking it now

                        Thanks a ton to everyone who helped me troubleshoot this,
                        Colin
                        Colin Senner

                        Comment


                        • #13
                          Hilbert.....I love his little dog that runs the company
                          Eric Camper
                          Studio 3D
                          www.dbfinc.com/studio3d

                          Comment


                          • #14
                            It is already corrected for the newer builds...

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

                            Comment

                            Working...
                            X