Re: Frame buffer 0 invalid

[Christian Götzinger <cg(at)pension-goetzinger.de>]

Thank you for the advice! I have only 2 GB in my new workstation - about 
to upgrade to 4. However, I had task manager open the entire time, and 
right before the rendering finished I had still almost 1 GB of physical 
memory available! So I don't see how it could have run out :-/

To James: I did try to open the 1K file with imf_display, but it only 
displays a black image. In fact, I just tried something: I re-started 
the entire render and tried to open the image in imf_display while it 
was rendering (I usually do this anyway) - and it caused the render to 
stop immediately - without throwing an error, it just stopped. And 
imf_display also displayed a black image.

What I have done now is this: I have taken out a heavy object (4 million 
real triangles) and I'm rendering the scene again (I adjusted my 
settings this time around because rendering time was way too high 
anyway) - I have imf_display open and it's correctly displaying the 
progress, so I HOPE that it'll work. I will then render the 4 million 
triangle object separately.
You may say that I should have done this in the first place - but for 
one thing, XSI 5 is supposed to handle this kind of data, and for the 
other thing, my RAM did not run low. So I saw no need to split up the scene.

Cheers,
Chris

Thomas Helzle schrieb:
> How much Ram do you have installed?
> 3000 pixels isn't much but if ram is filled with other stuff from your heavy scene, it is possible you run out of continuous memory.
> I had similar problems (but with much lager images) and got the following advice from Mathieu Leclaire:
>
> ################################
>
> Well, I'm not sure which technique you use to render your limited area but I
> believe if you play with the image resolution, the focal length and the
> optical center shift, you can render regions of the image and then you could
> comp them back together using Photoshop or which ever software you can use
> to attach the pieces back together. If your not sure how to set your
> parameters, here's what you do:
>
> lets say you want to split you 12000x7500 render into 4 regions, you set it
> up that way:
> -set you resolution to half the value: 6000x3750.
> -in your camera's projection plane, set the focal length to it's value *2
> -set the X and Y Optical Center Shift to
> 	-1/2 * X Film Aperture,  1/2 * Y Film Aperture ...for the up left corner
> 	 1/2 * X Film Aperture,  1/2 * Y Film Aperture ...for the up right corner
> 	-1/2 * X Film Aperture, -1/2 * Y Film Aperture ...for the bottom left
> corner
> 	 1/2 * X Film Aperture, -1/2 * Y Film Aperture ...for the bottom right
> corner
>
> render each section at half your resolution, comp them back together after
> to get your 12000x7500 final image.
>
> If still too big, you can split it in 9 regions using the following instead:
> divide X and Y resolution by 3, multiply focal length by 3 and multiply your
> film apertures by -1, 0 and 1 to get the Optical center shift...
> Or split it in 12 regions, dividing and multiplying resolution and focal
> length by 4 and using -3/2, -1/2, 1/2, 3/2 for your optical shifts...
> Or split it in 25 regions, dividing and multiplying resolution and focal
> length by 5 and using -2, -1, 0, 1, 2 for your optical shifts...
> I think you can figure out the pattern from there.
>
> I hope this can help.
>
> ##################################
>
> It worked perfectly for me - may be a more secure way of rendering such a heavy scene like yours anyway.
>
> I still think it is pure horror that XSI/MR realizes it's problems only after the rendering and then throws everything into the garbage instead of simply writing the framebuffer(s) to disk, offering to recover it later with some tool then...
> Stupid little bugger ;-)
>
> Good luck!
>
> Thomas Helzle
> www.screeendream.de
>
>
> On Tue, 18 Jul 2006 16:35:39 +0200, Christian Götzinger <cg(at)pension-goetzinger.de> wrote:
>
>   
> > Hey guys,
> >
> > I have this scene that I need rendered asap. It's a very big scene and
> > I'm happy that it rendered properly. Well, it rendered properly, and
> > when it was time to write the output file to disk, Mental Ray chose not to:
> > Error 051003: frame buffer 0 invalid, cannot create file
> >
> > So, after 27 hours of rendering I'm sitting here without a file and have
> > no clue what went wrong. I had rendered out a small preview (800 pixels
> > wide) of the very same scene just a few days ago. The only thing that's
> > changed since then are a couple of material settings, higher render
> > settings and a higher output resolution (3000 pixels wide).
> >
> > I need this darn scene rendered, what can I do? I mean what on earth did
> > Mental Ray do with all the data it calculated over the last day? Threw
> > it away?
> >
> > Cheers,
> > Chris
> >
> >     


---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi