PROBLEM: Memory Allocation Failure

[dmarques1177]

I have been working with this one scene for a while now, and rendered several different test images.
It's fairly simple. a packshot being light directly by 5 rect. lights, and a HDR image.

Normally it takes about 2 hrs to render each frame at my highest render settings, and about 5-10 mins in my preview settings.


Today I can't render. It keeps giving me this memory Allocation failure, the only difference I made to the scene is smooth out the geometry (#3 shortcut) and I can see how it would make the scene heavier but this alone crashing my render is absurd... the only other time I had this problem I just batch rendered a frame instead of rendering within maya and it worked, this workaround is not effective now.

BTW it crashes even when I set my render settings very low ...

[vlado]

Why would it be absurd, subdivision may create enormous amounts of geometry, and if you are using a 32-bit version of Maya, the 1.5 GB memory limit might indeed be filled pretty quickly. Anyways, if you go to the "Default displacement and subdivision" rollout in the "Settings" tab in the Render globals, you can decrease the "max subdivs" parameter, or increase the "edge length" parameter. Both will cause less geometry to be generated for subdivision surfaces, which will help to reduce memory usage.

Best regards,
Vlado

[dmarques1177]

Thanks a lot for your quick reply Vlado.

Well what I think is absurd is that I have rendered much more complex scenes with a lot more geometry than this with no problem... I will try messing with the subdivisions/edge length to see if I can render.


Thanks,

DM

[dmarques1177]

This is the error I am getting now:

Error: Exception [module=1] : Rendering region (384,0)-(448,64) //
// Error: There was a fatal error rendering the scene. //

is this a known error ?

[vlado]

It's probably the same thing, but in different words. If you still have problems, it would be best to get us the scene to vraymaya@chaosgroup.com and we'll check it out.

Best regards,
Vlado

[airstyle]

Somewhat left of field, but possibly related: we had this error pop up when using tiled EXR's and turning texturing filtering off. All we had to do is turn filtering back to default (quadratic) and voila it would render again.