Announcement

Collapse
No announcement yet.

The maximum of resolution is in VRayVFB?

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

  • The maximum of resolution is in VRayVFB?

    My system is a 16GB memory at 64bitMax.
    When VRayVFB is turned ON and the rendering of the simple scene (no GI, no object, no element),

    16000 x 11184 can do a rendering.
    16000 x11185 cannot do a rendering. VRayVFB freezes.

    This is the same behavior at VRayVFB on VRay3dsMax, VRayMaya, and VRayRhino.

    What is this difference?
    Simple insufficient memory? (But it does not seem to have used up all memories.)
    or limit of VRayVFB?

    OakCorp Japan - Yuji Yamauchi
    oakcorp.net
    v-ray.jp

  • #2
    It's reccomended to render to vrimg when doing huge renders and convert to .exr later - I think if you set the max frame buffer to 1x1, then override the resolution in the VFB (saving to vrimg) and disable the frame buffer (so it writes the image directly to disk) there is no limit.

    Comment


    • #3
      Originally posted by flat View Post
      16000 x 11184 can do a rendering.
      16000 x11185 cannot do a rendering. VRayVFB freezes.
      What happens if you do 16000 X 11186? (just for the sake of interest, because 11186 is dividable by 2)

      Some codecs dont like if you use un-even numbers. This has nothing to do with vray, but maybe in some way related to memory or some other internal calculations?
      Kind Regards,
      Morne

      Comment


      • #4
        Originally posted by cubiclegangster View Post
        It's reccomended to render to vrimg when doing huge renders and convert to .exr later - I think if you set the max frame buffer to 1x1, then override the resolution in the VFB (saving to vrimg) and disable the frame buffer (so it writes the image directly to disk) there is no limit.
        +1 for this. I've rendered images over 30'000 x 30'000 straight to vrimg files no problem.
        MDI Digital
        moonjam

        Comment


        • #5
          yes agreed, but 16000 wide should be fine for VFB, especialy since it will just be black because in this case there is nothing in the scene
          Kind Regards,
          Morne

          Comment


          • #6
            Should it? that's 180 million pixels...

            Comment


            • #7
              I see no reason why this will be an issue with an empty scene and 16GB ram. But Vlado should confirm...
              Kind Regards,
              Morne

              Comment


              • #8
                Hello,

                It is tested and reproduced here :
                16000x11184 - was rendered fine
                16000x11185 - crash

                We have added this issue to our to do list.
                For rendering bigger resolution it is better to use "Render to V-ray raw image file" (vrimg) with Generate Preview ON and Render to memory frame buffer OFF.
                Svetlozar Draganov | Senior Manager 3D Support | contact us
                Chaos & Enscape & Cylindo are now one!

                Comment


                • #9
                  Currently we assume that one render element in the VFB (be it RGB, or alpha, or something else) can take up to 2^31 bytes in RAM (2147483648 bytes). 16000x11185 x 12 bytes per pixel gives 2147520000 bytes, which is above that limit (whereas 16000x11184 is 2147328000, which is below). As Svetlozar pointed out, we will look into it, but for the moment, you can simply render directly to a .vrimg file.

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

                  Comment


                  • #10
                    The question whether it would freeze if 15000x10000 is exceeded from my customer (the architecture advertisement is created) was received.

                    16000x11185 was taken as a result of my checking the limits of a crash and working resolution.
                    Of course, advised to export by .vrimg image to my customer.

                    VFB (be it RGB, or alpha, or something else) can take up to 2^31 bytes in RAM (2147483648 bytes).
                    Thank you, the reason was understood.
                    Improvement is hoped although a priority is low.

                    OakCorp Japan - Yuji Yamauchi
                    oakcorp.net
                    v-ray.jp

                    Comment


                    • #11
                      Hi,

                      here at Vray for Rhino the limit is 15400x.. and the RAM usage of Rhino+Vray is 2.4GB only (only RGB channel used). At 15500 the render doesn't start. From my users view the current limit of 2.4GB is quite low and I hope it can be higher in the future. Why is it so low yet?

                      Using vrimg slow down the workflow. Extracting the image is slow, also I used the frame buffer curve control (great tool!!) often and it doesn't work for vrimg or?

                      Regards,
                      Micha
                      www.simulacrum.de - visualization for designer and architects

                      Comment


                      • #12
                        Hi,

                        any news? Any chance to increase the tight RAM limit of 2GB to an higher value?

                        Regards,
                        Micha
                        Last edited by Micha_cg; 17-07-2012, 02:11 AM.
                        www.simulacrum.de - visualization for designer and architects

                        Comment


                        • #13
                          writing tiled only takes one conversion (load and save in nuke as scanline), and is hardly a show-stopper, rather THE feature to render multiple channels without wasting ram on the FB allocation.
                          Lele
                          Trouble Stirrer in RnD @ Chaos
                          ----------------------
                          emanuele.lecchi@chaos.com

                          Disclaimer:
                          The views and opinions expressed here are my own and do not represent those of Chaos Group, unless otherwise stated.

                          Comment


                          • #14
                            Originally posted by Micha_cg View Post
                            any news? Any chance to increase the tight RAM limit of 2GB to an higher value?
                            We are working on this and I hope it will make it into the nightly builds soon.

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

                            Comment


                            • #15
                              Great, if it could be available for the VfR nightly builds too, please post a short note here if it is available.

                              http://www.chaosgroup.com/forums/vbu...put-resolution
                              www.simulacrum.de - visualization for designer and architects

                              Comment

                              Working...
                              X