Announcement

Collapse
No announcement yet.

Vray camera is broken when rendering through Backburner (VrayRT)

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

  • Vray camera is broken when rendering through Backburner (VrayRT)

    Hi,

    I'm using VrayRT 3.00.07 and Max 2015 sp2.

    When you render in Max with Vray-Camera, everything is fine.
    Click image for larger version

Name:	rendered in max.jpg
Views:	1
Size:	276.9 KB
ID:	880599

    When you submit the scene to Backburner, the vrayCamera renders as zoomed in or out. And there's no way I can match them.
    Click image for larger version

Name:	rendered with backburner.jpg
Views:	1
Size:	220.4 KB
ID:	880598

    If I use the normal Max Camera, it renders fine both in Max and Backburner.
    But the Max Camera is useless with Vray as there are no exposure controls.

    This is definitely a bug.
    In the past 3 weeks I have discovered several bugs... so if I am to buy Vray(i'm on the trial version now), do i have to buy it with those bugs ? (rethorical question)
    Thank you.

    Regards,
    Peter Istrate.
    CGI studio: www.moxels.com

    i7-4930K @ 3,4GHz watercooled
    Asus Rampage V Extreme Black Edition Intel X79
    64 GB DDR3 Corsair Vengeance Jet Black 1866 MHz Quad Channel
    8 * GTX Titan X
    960GB SSD Crucial M500 SATA-3
    nVidia drivers: always latest
    Windows 10 up to date

  • #2
    Originally posted by peteristrate View Post
    Hi,

    I'm using VrayRT 3.00.07 and Max 2015 sp2.

    When you render in Max with Vray-Camera, everything is fine.
    [ATTACH=CONFIG]20622[/ATTACH]

    When you submit the scene to Backburner, the vrayCamera renders as zoomed in or out. And there's no way I can match them.
    [ATTACH=CONFIG]20621[/ATTACH]

    If I use the normal Max Camera, it renders fine both in Max and Backburner.
    But the Max Camera is useless with Vray as there are no exposure controls.

    This is definitely a bug.
    In the past 3 weeks I have discovered several bugs... so if I am to buy Vray(i'm on the trial version now), do i have to buy it with those bugs ? (rethorical question)
    Thank you.

    Regards,
    Peter Istrate.
    Doest standard max camera works fine?
    CGI - Freelancer - Available for work

    www.dariuszmakowski.com - come and look

    Comment


    • #3
      Hi Dariusz,

      Yes, the standard Max camera works fine. I've stated that already, read again
      CGI studio: www.moxels.com

      i7-4930K @ 3,4GHz watercooled
      Asus Rampage V Extreme Black Edition Intel X79
      64 GB DDR3 Corsair Vengeance Jet Black 1866 MHz Quad Channel
      8 * GTX Titan X
      960GB SSD Crucial M500 SATA-3
      nVidia drivers: always latest
      Windows 10 up to date

      Comment


      • #4
        Aw sory, blindness has me... Humh that's strange in this case
        CGI - Freelancer - Available for work

        www.dariuszmakowski.com - come and look

        Comment


        • #5
          Hi Peter,

          Yes, there is a bug. The case is already logged to our system and we will fix it.

          Click image for larger version

Name:	2014-08-25 11_31_12.jpg
Views:	1
Size:	232.2 KB
ID:	854038

          Thank you for sharing your experience.
          Last edited by tashko.zashev; 25-08-2014, 01:37 AM.
          Tashko Zashev | chaos.com
          Chaos Support Representative | contact us

          Comment


          • #6
            Cool.
            For now I have worked it around with Batch rendering because I have several cameras in one scene(out of several other scenes), but when you have multiple scenes, Backburner is needed.
            Looking forward to see it fixed in the next build.
            Thanks.
            CGI studio: www.moxels.com

            i7-4930K @ 3,4GHz watercooled
            Asus Rampage V Extreme Black Edition Intel X79
            64 GB DDR3 Corsair Vengeance Jet Black 1866 MHz Quad Channel
            8 * GTX Titan X
            960GB SSD Crucial M500 SATA-3
            nVidia drivers: always latest
            Windows 10 up to date

            Comment


            • #7
              Thanks for your update Peter.
              Our developers are working on the fix right now, so we will notify you on any update.
              Tashko Zashev | chaos.com
              Chaos Support Representative | contact us

              Comment


              • #8
                I have also noticed that if I render through Batch renderer(not Backburner) and I try to save the renders as .hdr, it saves the image as black.
                If I save the image manually, using the VFB save button, it saves ok, but if it's saved through Batch rendering, it saves black.

                Regards,
                Peter Istrate.
                CGI studio: www.moxels.com

                i7-4930K @ 3,4GHz watercooled
                Asus Rampage V Extreme Black Edition Intel X79
                64 GB DDR3 Corsair Vengeance Jet Black 1866 MHz Quad Channel
                8 * GTX Titan X
                960GB SSD Crucial M500 SATA-3
                nVidia drivers: always latest
                Windows 10 up to date

                Comment


                • #9
                  Is that only for HDR files? What about OpenEXR?

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

                  Comment


                  • #10
                    The OpenEXR is fine.
                    The .hdr is not.
                    I haven't tried other file formats. I think you can replicate this with a very simple scene - just try to render and save with Batch rendering.

                    Regards,
                    Peter Istrate.
                    CGI studio: www.moxels.com

                    i7-4930K @ 3,4GHz watercooled
                    Asus Rampage V Extreme Black Edition Intel X79
                    64 GB DDR3 Corsair Vengeance Jet Black 1866 MHz Quad Channel
                    8 * GTX Titan X
                    960GB SSD Crucial M500 SATA-3
                    nVidia drivers: always latest
                    Windows 10 up to date

                    Comment


                    • #11
                      Hi Peter,

                      I can replicate this issue only if I use the native 3DS max save option.
                      Saving from Render settings > V-Ray frame buffer > Separate render channels to HDR file works fine in my test. Could you use this as a workaround?
                      Tashko Zashev | chaos.com
                      Chaos Support Representative | contact us

                      Comment


                      • #12
                        When you save to HDR, 3ds Max puts up a dialog box asking if you want to use non-clamped (realpixel) color channel, or use standard RGB channel. Which option did you select? The first one will not work.

                        The RT engine also has an option to generate a floating-point image buffer, which you might need to enable.

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

                        Comment


                        • #13
                          @Vlado:
                          The floating point buffer option("Use 32 bit frame buffer"?) for the frame buffer is checked.
                          For HDR, i use the non-clamped (realpixel) color channel because I need the whole 32 bit range of the image to alter it in compositing. The standard RGB channel is just an 8bit image if i'm not mistaken.

                          @Tashko:
                          If I use the save "separate render channels" then all my batched renders will have the same path that was set in "separate render channels".
                          Saving from Render settings > V-Ray frame buffer > Separate render channels to HDR file works fine, indeed but then I can't have different multiple saving paths as Batch rendering allows you to so that's why i need to save through Batch rendering(which uses the standard max saving option).

                          I could create a different "Scene State" for each of my renders so in that case, each camera will have it's own scene state with its own render settings(including "Separate render channels") and then I can assign the corresponding render state in Batch rendering, but this is not feasible at all.
                          CGI studio: www.moxels.com

                          i7-4930K @ 3,4GHz watercooled
                          Asus Rampage V Extreme Black Edition Intel X79
                          64 GB DDR3 Corsair Vengeance Jet Black 1866 MHz Quad Channel
                          8 * GTX Titan X
                          960GB SSD Crucial M500 SATA-3
                          nVidia drivers: always latest
                          Windows 10 up to date

                          Comment


                          • #14
                            Originally posted by peteristrate View Post
                            For HDR, i use the non-clamped (realpixel) color channel because I need the whole 32 bit range of the image to alter it in compositing. The standard RGB channel is just an 8bit image if i'm not mistaken.
                            The realpixel channel option will not work. Use the other one - it works just fine and will produce proper HDR data.

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

                            Comment


                            • #15
                              I was rendering today with Batch rendering as a workaround for Backburner and I have noticed the cropping(or zoom factor) occurs with Batch rendering as well this time. I had 2 batch render entries(2 cameras): the first one rendered correctly, the second one rendered cropped/zoomed.
                              But it worked fine for other scenes before.
                              That is very strange.
                              CGI studio: www.moxels.com

                              i7-4930K @ 3,4GHz watercooled
                              Asus Rampage V Extreme Black Edition Intel X79
                              64 GB DDR3 Corsair Vengeance Jet Black 1866 MHz Quad Channel
                              8 * GTX Titan X
                              960GB SSD Crucial M500 SATA-3
                              nVidia drivers: always latest
                              Windows 10 up to date

                              Comment

                              Working...
                              X