Hello,

I need to render a picture, bmp format, 8,000px by 17,000px
Whatever the settings I use, it always crashes with a “Error while creating bitmap” without additional informations.

Max is supposed to render 32,768*32,768 px pictures so I don’t have explanations.
I thought that bucket rendering could solve the problem...but not.

My graphic card is a Nvidia Quadro FX 4600 and I have 3,25GB of RAM. Is there an issue with memory allocation from max itself?

Thanx

have you tried rendering to strips through BackBurner?  That will usually do the trick.  Otherwise, render out separate regions on your computer then stitch them together in PhotoShop or something.

What do you need an image that size for?  Depending on how it will be used, you can often times get away with less resolution because it won’t be viewed up close.

AFAIK, the maximum image size you can render to is dicatated by the amount of RAM in your machine.  When exactly does the error occur, during rendering or when it tries to save the image?  Have you tried a different file format?

Hi Chris

1- I never tried this strips rendering in Backburner. I only knew the bucket rendering feature for Mental Ray. Will try today.

2- The error occurs by pushing the render button. Just after come this popup alert message “Error creating bitmap”. The crash happens whatever the choosen output format.

3- The purpose of this rendering is advertise printing, 3m long poster.

PS: Another problem when I use bucket rendering on my renderfarm is that for larger pictures, it renders only black buckets with some white pixels on it. Everything is working well if I reduce the size to a standard one.

Thanx

This is very cool. I’m surprised its so complicated to render large pictures though.
Why not have strip render in max render dialog instead of using backburner as you only need one server and its function , as above to make large printable images, will never be necessary in a network render environment. And call it something intuitive!!

I have never run into this, but I usually get other rendering errors of the type, it is usually caused by not enough memory. But it could be something different

This is a known issue - here is the AD KB article on it - basically suggests rendering regions.

click on the link

Daf