Announcement

Collapse
No announcement yet.

Openexr saved as transparant

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

  • Openexr saved as transparant

    Hi,
    I've got this problem quite often and in different scenes.

    I save as openexr through the renderdialog --> Frame buffer --> render to Vray raw image --> .exr
    After render it saves the .exr and it looks like it is saved with all layers (114MB)
    But if i open in photsohop or any other programm its all transparent..

    I also have a problem with BB which starts over and over again after finishing the job. I'm not sure the problems are related.
    This makes it very unreliable to render a batch through backburner. So i'm stuck with rendering on my workstation with DR and have to check if the image is saved correctly. If not; i do a region and save under another name till it saves correctly.

    I use 3ds Max 2013 V-ray 2.40.03

    Any Clues?
    Last edited by Roest; 13-06-2013, 08:15 AM.
    http://3dstudioprins.nl/

  • #2
    The issue with EXR is that it saves with applied alpha or it opens with it. So it takes alpha and applies it to image giving u transparent result. I cant remember if you can change it in MAX or not but if its not Max issue but photoshop then you need pro EXR or CS6 to tell it otherwise.

    Not sure with BB

    Thanks, bye.
    CGI - Freelancer - Available for work

    www.dariuszmakowski.com - come and look

    Comment


    • #3
      I have pro EXR. The problem is it saves everything as transparent (not only alpha)
      If i save the rendered image again it just shows correctly in photoshop with alpha as transparent.
      Last edited by Roest; 13-06-2013, 08:16 AM.
      http://3dstudioprins.nl/

      Comment


      • #4
        No one had this problem before?
        http://3dstudioprins.nl/

        Comment


        • #5
          Hi,

          Can you post an example EXR file to check it in our environment?
          Most probably the problem is in Photoshop and it's plugins.

          About the problem with Backburner, do you have tasks that require more than 10 hours rendering? If yes, try to increase the "Time out" parameters.
          Tashko Zashev | chaos.com
          Chaos Support Representative | contact us

          Comment


          • #6
            You can check this thread for more solutions:
            http://www.chaosgroup.com/forums/vbu...Time-Out-Error

            It's a discussion about the same Backburner issue. Hope this helps for your case too.
            Tashko Zashev | chaos.com
            Chaos Support Representative | contact us

            Comment


            • #7
              Hi Tashko, i sended you a private message with an example of an opexr file.

              About Backburner; It has nothing todo with the 600min rendering limit. Its with small jobs and bigger jobs. I will try today if it only occurs with openexr or also any other type of file.
              I will lookup the discussion anyway
              Thanks in advance!
              http://3dstudioprins.nl/

              Comment


              • #8
                Probably not much use to you, but Photoshop CS6 now gives you the option to open EXRs as transparent or with alpha channel.
                Check out my models on 3dOcean

                Comment


                • #9
                  Thanks for sending the file.
                  Just as a side note, it's better to use our support mail to send files or detail about issues that are V-Ray related.

                  However, it seems that the file is not readable. The possible reasons are that it was not downloaded properly (114mb) or was not properly saved.
                  Are you able to open this file in any software without errors?
                  Do you see only black image/layers when the file is opened in Photoshop?
                  Could you try to open the file with the native 3ds Max image file viewer (rendering menu \ View image file ). If it fails, save new low resolution EXR file without render elements and use the file viewer again.
                  Tashko Zashev | chaos.com
                  Chaos Support Representative | contact us

                  Comment


                  • #10
                    Thanks for the quick reply!
                    See attachement, that is what i see if i open in photoshop CS6.
                    edit* see attachment 2 for the 3ds max narrative viewer.

                    If i Open in Nuke i got this error: Error reading pixel data from image file. Unexpeted data block y coordinate

                    So probably it is not saved correctly. But why?
                    The image size is still the same as the correctly saved file.

                    Side note: I always use DR and save to network storage.
                    Attached Files
                    Last edited by Roest; 19-06-2013, 05:12 AM.
                    http://3dstudioprins.nl/

                    Comment


                    • #11
                      Yes, the same result with your file here as well.
                      Something fails when writing to file in your environment. Does it happen only with EXR file format?
                      Try to save locally and let me know if the file is unreadable again.
                      Tashko Zashev | chaos.com
                      Chaos Support Representative | contact us

                      Comment


                      • #12
                        This could take a while, because it don't happen every time. And if a render failed to save, the next time it saves correct.
                        So i have to monitor for a while

                        I'm planning to switch to 3ds max 2014, maybe a fresh install would help.
                        http://3dstudioprins.nl/

                        Comment


                        • #13
                          After switching to 3ds max 2014 i still got problem with backburner & transparant openexr..

                          I did rendered a 1000 frames animation saved as openexr without any problems though (i was really happy thinking everything is fixed )
                          But with bigger files and using DR, saving as openexr, backburner is unstable as always.

                          * I think i fixed the maxadapter issues/errors with the IPv6 turned off.
                          * The Error writing render region to raw image file (see attachment) is hopefully fixed with; "untick Render to memory frame buffer!"

                          * But now i still got the transparant openexr as output!! (today three times!)

                          Its just one of those weeks i got all kind of different problems, spending hours & hours on forums to try to fix shit instead of working.......

                          Now i'm back again rendering on my workstation with DR
                          It really drives me nuts.
                          Attached Files
                          Last edited by Jeroen Prins; 01-08-2013, 08:50 AM. Reason: attachment

                          Comment


                          • #14
                            This is actually solved in the latest nightly builds (provided that "Use memory frame buffer" is ON); you could try these that if you want.

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

                            Comment


                            • #15
                              I would be glad to try Vlado.

                              In order to try to solve the transparent exr's & BB, what tests can be done to pinpoint the problem?
                              - BB, save locally to png, exr.
                              - BB, save locally to png, exr with DR
                              - ...

                              I have a few hours today to do some tests. Because i rendered the animation without problems i think the problem occur when using DR & exr.
                              Any thoughts?

                              Comment

                              Working...
                              X