Announcement

Collapse
No announcement yet.

Render passes look like static - Maybe a backburner or UAC error

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

  • Render passes look like static - Maybe a backburner or UAC error

    Hello all, my render passes are coming out garbled on the farm occasionally. Here is an example:


    We're not sure what's causing it, and I suspect it isn't vray but I can't be sure. Posting here to see if anyone has seen anything like this. We've had issues rendering out .tif, .tga, and now .png as passes. (elements)

    The beauty render comes out fine and looking good, just no passes. In Photoshop when we open this we see "Bitmap" instead of any RGB channels. Odd.

    Thanks for your time and feedback.
    AJ
    Click image for larger version

Name:	Shot_C2_Lighting_09__VRayReflection0008.png
Views:	1
Size:	36.9 KB
ID:	874109

    EDIT: The server machines are using W7 64 Bit with 12 GB RAM. intel procs.
    Last edited by Deflaminis; 05-04-2012, 01:33 PM.

  • #2
    I solved this problem. It's a max bug, again not sure if related to vray or not but here's how it came up.

    I loaded a preset that had render elements setup.

    Somehow it got corrupted in that it would load the setup, but the IOBitmap (pager?) module would "forget" the settings for the pngs. Meaning all the bit depth settings and alpha channel had nothing selected. Any renders from this would have the elements all jacked up.

    I removed the elements and re-added them and now it seems to work just fine. I haven't had a chance to test it with MR yet, but if it's a Vray issue here's the cause, steps to reproduce, and solution.
    `
    You can just go to elements, select one of them, and hit the "..." button. Then click in the emptiness of the frame and hit "Setup" and you'll see that no settings are selected. Odd. This causes it to freak when it's writing the images.

    Hope that's helpful. I can send the file if you want... stripped of everything but the elements.

    Comment


    • #3
      This was reported some time ago, but there isn't much we can do about it. As always, rendering to a .vrimg file and then extracting the elements with vrimg2exr is probably the most robust way to do this.

      Best regards,
      Vlado
      Last edited by vlado; 06-04-2012, 01:56 PM.
      I only act like I know everything, Rogers.

      Comment


      • #4
        I'll need to find the time to get our compositing department updated on the vrimg workflow in the long run it seems. Thanks Vlado.

        Comment

        Working...
        X